Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by calweycn

  1. That doesn't help. Even if I'm not doing anything processor intensive, other programs will become slow to respond. And this is with multiple drives, not copying to the same drive. There's no way to limit the speed unless it gives you the option. I guess I just won't use this feature, since it takes away my computer's functionality. I have 1.5 GB of RAM and lots of free memory. If the program wants 100% of my hard drive time, that's too much.
  2. I don't see why it would take much time and effort. ImgBurn can read ISO files already. All it needs to do is look at the file sizes, like it does anyway, and create a new image structure. You can mount the image with D-Tools and use the root directory as your source in Build Mode. That will achieve the same result I'm talking about. But it'd be better if ImgBurn supported it directly. If you can read images, most of the work has been done.
  3. Can you add an option to limit the write speed for creating an ISO in Build Mode? It is very processor and drive intensive to have it running at full speed with no restriction. The computer can become extremely unresponsive due to this stress, reducing the ability to multi-task. I'd like to be able to limit the speed it writes the ISO.
  4. http://forum.doom9.org/showthread.php?t=110426 http://forum.videohelp.com/viewtopic.php?t=225001 Here are some articles for further reading on seamless layer break DVDs. This will support some of my stats above. In my experience, dual layer DVDs play fine even with ECC block/VOBU boundary LB selection. LUK has acknowledged this too. http://forum.imgburn.com/index.php?showtopic=1337 The Official DVD-Video Specification forbids seamless layer breaks and layer breaks within cells. However, players are largely able to tolerate such issues. I have never liked the LB delay in DVDs, so I started looking for ways to get rid of it. Through tests, I found the pause results from cell flags at the LB and cell commands before the LB. Use PGC Edit to change the flags to seamless and remove any command before the LB => seamless playback. When you burn a Dual Layer size ISO made with Shrink, you will probably end up with a NAV Pack layer break, unless you're lucky enough to have a cell on an ECC boundary. In my experience, it will play fine in most machines. Computer drives will not have any trouble with NAV Pack layer breaks. But you must also address the cell flags and commands if you want seamless playback. All Superbit DVDs use seamless layer breaks. A lot of Criterions do too - Naked, Solaris, Fear and Loathing, Bad Timing, Man Who Fell To Earth, Naked Lunch, Videodrome, etc. Seamless LB is the better way to go, but NAV Pack layer breaks are compatible in a large majority of the world's players.
  5. I've been burning DL made with PGC Edit and Shrink without any playback troubles. I calculated the exact position of the layer break and tested it in a Samsung and Daewoo. Both played past the layer break with no pause at all. (...) They should play in all computers also. I have read that at least 67% of players will handle a layer break that is NOT on a cell. I always use seamless layer break, because the layer break pause is too annoying. In regard to that, I've read that 95-99% of players will handle a cell layer break that is flagged as seamless. Proof: Many Criterion DVDs and ALL Superbits use seamless layer breaks. I have never heard of any people having problems playing them back. On the contrary, people note they don't have the typical annoying LB pause.
  6. I have checked the IFOs on burned discs with AnyDVD on and off. They are fine. AnyDVD just changes a few bits on-the-fly. It doesn't change what the drive writes. It doesn't change the VOBs. If the disc plays and everything is verified except one IFO/BUP, there is very LITTLE reason to worry. Only one IFO/BUP would be read differently with AnyDVD on. It would be a billion-to-one for all the data to be right except some bits in the IFO/BUP file. AnyDVD isn't doing anything I don't know about. I have tested ImgBurn's verify mode with AnyDVD on and off. I know what it's doing.
  7. ImgBurn will show you which files verified correctly and which didn't. At least, that's how the last version worked. So you will see that only these IFO/BUP files would fail verification. And actually just the main IFO/BUP, I think, for "non css" DVDs. You can disable AnyDVD and those IFO's will verify perfectly, just as most of the files do even with it running. It's a question of whether I want to waste the time disabling and re-enabling AnyDVD, and losing my place in whatever DVD I'm watching. I feel that 35-40 seconds of my life is not worth that, when I can still verify all the other data with AnyDVD on. If the disc plays and all of the other files verify, that's enough for me.
  8. Nobody said that it would cause problem with the layer break. They said it would cause the disc to fail verification. Actually, it's just a few IFO/BUP files that have a few bits changed. I have never worried about this. I tested it copying the IFOs from the DVD with AnyDVD on, then copying again with it off. AnyDVD doesn't change the VOBs on the DVD at all. It has no effect on normal Data DVDs, either. It just changes a few bits in the IFO/BUPs. People blow this way out of proportion, IMO. Very little is modified by AnyDVD. They will still be the same in terms of image, sound, and functionality. EDIT: BUF to BUP
  9. I leave it running, because it takes about 10 seconds to disable and 30 seconds to re-enable. AnyDVD is only modifying a few bits in the IFOs on-the-fly. It does not change the data that is written to the disc. The VOBs will verify with AnyDVD running. I see no reason to disable it, waste 35 sec or more, and lose my place in whatever DVD I happen to be watching. Disabling AnyDVD for verifying seems paranoid. All of the data can be verified, except a few bits in one the main IFO/BUP file. At least, that is what I noticed in the last version of ImgBurn (1300). AnyDVD is nothing to worry about, unless you are paranoid about a few bits of the IFO/BUP files.
  10. Lightning UK is a woman? I don't know personally, so I just say LUK.
  11. Would it be possible to treat an image like files, so that it could be padded or have a new layer break set, for instance? It seems this should work, in theory. Just read files from the image, and build a new disk from that. This would give us more flexibility for images, to either burn them as they are or pad the files and change layer break settings on-the-fly. Can this be done?
  12. That's not the only issue. The all-or-nothingness of it was the main issue. A person might want to check for updates regularly, but they don't need to always have the latest. Give the ad hominems a rest. Being able to burn files and create ISOs makes it a de facto ripper. I've posted on this issue numerous times. Nero and others do not have the same functionality as ImgBurn, so they aren't good comparisons. What you should say is that ImgBurn won't circumvent copy protection. Nor will Nero and Roxio and others. It can rip unprotected discs or "drives" if you know what I mean. (And I think you do.)
  13. Sure, the price will go lower. But DL will always cost more than SL. There is a limit to how long prices can go. I think less than $2 is pretty reasonable. I am seeing Verbatim +R DL for $1.75 at Worst Buy, which is less than Amazon or NewEgg. Even when BluRay drives become affordable, the discs will cost like $20-30 a piece. They won't kill the DVD market any time soon.
  14. Nothing prevents you from doing this. Just open Build Mode, set the DVD drive as your Folder source, and output to an ISO file. It should also work for you to burn the files directly to DVD, bypassing your hard drive. Of course, ImgBurn is not capable of circumventing any copy protections. You are on your own there. Nothing stops you from creating an ISO or burning one DVD to another. All of that should be very straightforward.
  15. You should also be able to take your "non css dvd" and burn it directly to another disc, bypassing the hard drive entirely. At least, I know of no reason why that would not be possible. ImgBurn is a versatile tool. LUK's last response was somewhat facetious IMO. He is too modest. Just experiment with the software and you will find it is able to do a lot of interesting things that save you time and hassle. Great work, LUK!
  16. The software has lots of features that might be viewed as pointless by you. That hasn't stopped you from adding them. Choice makes a better program. What seems pointless is all-or-nothing with no middle ground.
  17. No, it's not. The logs can still be subpoenaed or intercepted by other parties, given the current legal climate. So I might prefer to check less often for that reason. Plus, the software has never been updated daily for the general user base. Try 2-4 months between each major upgrade. Maybe you want to get updates without your IP on a log somewhere as aperson using the program every day. Maybe you don't want to upgrade to each new version immediately (early adopter), but you would like like to know about the upgrades eventually (without checking manually). There are many reasons to allow it and no strong reason not to. Accusing those who value privacy of paranoia is a bit silly. I'm not accusing you of collecting IP addresses. I am worried that someone else might collect them. Given the legal situation of this software, where it is not allowed to discuss existing features (like on-the-fly burning), it makes me think that you have something to hide.
  18. Because I want to know about the updates eventually, but I don't have to know about them immediately unless I'm experiencing problems. I also check free-codecs almost daily for any new software. ImgBurn hasn't been updated for 2-4 months, except for beta testers. Isn't it overkill to have millions of people checking for updates every day? Why not allow more realistic intervals like weekly, bi-weekly, monthly, and bi-monthly? It's not that hard to put a little menu or check box there. Why do you care what reason someone has for checking less often? Why waste a lot of bandwidth and server time for nothing?
  19. I started buying them at $7 and I will buy more as they go below $2. I never compress my DVDs any more. If they are too big to fit single layer for the movie itself, I use a dual layer. Always. I have not been satisfied with the quality obtained by compression - even slight. Over-burning is also handy. A lot of movies are just 30-150 MB over single layer size. They can easily be over-burned. I've burned up to 4600 MB with ImgBurn, BenQ 1640, and MCC or TY discs. Why are people so upset about $2? It's not that big a deal to me. I am not rich, either. $2 is nothing to me. I'll burn 50 dual layer DVDs and won't even flinch. The price is low enough now. It will probably NEVER get as low as single layer media.
  20. Apple/Linux/Unix may not be dominant in the front office, but they are dominant in servers and the back office. I can never trust NTFS. I have continued to lose files at a rate of ~1%, long after initially noticing the pattern. They are files I have just set in a folder and not accessed with any program (except defrag). When I go back later, some of them are garbage. This happens across partitions and drives, but only with NTFS. Never had it happen with data on FAT32. I go to play a video or song and find it's corrupt. Not just a few errors, but the whole file is garbage data. I've checked for viruses routinely, and even did a clean install of the whole OS. Nothing has stoppd these problems from occurring. Perhaps most people don't notice a 1% loss of their data, but to me it's unacceptable. Whether the problem is caused by NTFS is a moot point. The problem has only been observed by me with NTFS.
  21. We're getting off-topic, but I've tested the disks thoroughly with chkdsk, Partition Magic, and other software. There were never any bad sectors found. I seriously doubt that it was a hardware problem. All the files with corruption were on NTFS drives. Most people wouldn't even notice if 1% of their files were lost, because they don't check them. I run defrag regularly (PD7). There have never been any bad sectorsfound on the drives. There have never been any power failures, as I have used battery back-ups for years. Businesses also make errors from time to time. Probably at a rate of at least 1%. Also, the files that are corrupted might never be checked again. Many files in Windows are never used. Shrink DOES work with 2 GB file splitting on FAT32, but not Auto (which uses 3.99 GB splitting). It will work with any size file splitting for NTFS. It's not a big deal for me to use 2 GB splitting in ImgBurn Build Mode. I just wondered if this was a universal problem. Since at least one person has said they don't have this problem, it may be something caused by how my computer or software is configured.
  22. I'm using SPTI. File splitting was at Auto, but it didn't work for me. Shrink can't open the MDS, unless I use 2 GB splitting. Auto uses 3.99 GB splitting on FAT32. If it works for you, then there must be something wrong with my configuration - either in DVD Shrink or ImgBurn. I don't know what it could be.
  23. Worst Buy has Verbatim DVD+R DL 20-pack for $34.99 this week. Personally, I started buying when the prices hit $6.99 a piece. Now they're under $1.75. It'll be great when they get to $1, but $1.75 - $2.00 is a great price. Is $2.00 that big a deal? EDIT: price mis-typed
  24. Perhaps not, but there are certain others who take an interest in his software. I just don't want the program phoning home every day. I request or suggest that we be given more choices. Every load, daily, weekly, or monthly seems like a good starting place. Over a month would be excessive. There are others reasons one might want to check less often, besides privacy concerns. The software isn't even updated daily for the general public. There has been a 2-4 month interval between each major upgrade. Why not allow a weekly and monthly check? Maybe bi-weekly and bi-monthly.
  25. I didn't imagine losing 1% of my songs and photos, due to random file corruption on hard drives and partitions. Most of them were irreplaceable. FAT32 drives have never lost data. That's enough to make me wary of using NTFS. They might not notice if 1% of their files were randomly turned into garbage. I do not want to take that chance. 60 files out of 6,000 - lost. Not exactly what inspires confidence in users. No bad sectors on the drives. I've had battery back-up since day one, so there were no sudden power outages, either. EDIT: Many businesses use Apple, Linux, or Unix. They avoid Microsoft.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.