calweycn

You said it! Wish we could download the newest beta, like some other programs allow. I didn't use Build Mode for a month, except on data, because of the 32k IFO padding issue. Turning off the feature wasn't an acceptable solution, so I didn't use Build Mode.

I didn't understand how a 700 MiB CD can hold 80 minutes of CDDA, when it should only hold 69:20 (assuming 2352 bytes per frame). I knew that DVD sectors were 2048 bytes. I didn't know that the lead in wasn't included, so that was nice to know. DVDs apparently have the same 150 sector lead-in. Now the numbers add up. Your use of modulo (remainder) made it more clear. Thanks.

That's what I calculated, but it should take 2352 bytes per frame to give CD quality audio. Unless it's compressed to 87% size... So, that's still a mystery, how they squeeze 2352 bytes into 2048. Plus, eight to fourteen modulation should increase the bit rate even more. http://en.wikipedia.org/wiki/Eight-to-Fourteen_Modulation

These figures still don't add up for me. A 700 MiB CD should only hold 69.3 minutes of music, not 80. Each minute takes up ~10.1 MiB. (2352 bytes per frame. 75 frames/sec. 60 sec/min.) The MSF is always more than it should be, according to these figures. WTF? See third paragraph here... http://www.beatjapan.org/mirror/www.be.com...er/Issue66.html

Thanks, LUK. I knew it had nothing to do with the actual DVD length, but I should have guessed it was based on CD. Do you know how many frames are in a second of CD audio? I think 75. How does your program convert bytes to MSF, or is it based on something else? Regards

DVD+R free time is 510:03:29 or 4,700,372,992 bytes. Does anyone know how to convert mm:ss:ff to bytes? EDIT: Just curious...

I really have to disagree with that statement. It might be true if users were paying for the program and customer service support. However, since this is freeware/donationware it is up to the programmer what his program will and will not do or display. And it's up to the users whether certain suggestions are good ideas or whether certain aspects of the program are good. They are entitled to their opinions, and LUK is entitled to his. Just because he gets the final word doesn't mean he is right and everyone else is wrong. He is right for himself. He is wrong if you disagree with him. There's nothing disrespectful about saying that. While we're on the topic of what no one is forced to do, no one is forcing LUKto develop the program all by himself. I'm sure there would be thousands of talented programmers willing to help if he would open-source the project. In fact, I'll go farther and state that certain "problems" which dominate thinking here would not exist if the previous incarnation of ImgBurn had been "open." That is not a complaint, merely a statement of fact/regret. I have no stake in this issue, since my burners all support full bit-setting on +R and +RW media. I have never had a compatibility problem. Nor am I in need of "justifying" anything or "whining" about anything. You seem to have a problem with anyone disagreeing to The Boss. So does blutach. It makes me sad to see this self-abnegation and denial of everyone else's views. The Boss can do what he wants. The fact that these threads get LOTS of interest (page views) should say something. But apparently, it doesn't. Alas.

Horseshit. That's about the most stupid and ridiculous statement I've had the misfortune of reading. Is Nero a ripper? What about UltraISO? MusicMatch Jukebox? Do any of these programs remove Macrovision? What about ARccoSS? Doh! The word "ripping" applies to copying discs, whether they are protected or not. People "ripped" CDs when they had no protection at all. Removing protection and "ripping" are two different things. ImgBurn can rip "non css dvds." It's a ripper, whether or not you want it to be. Words have meanings. You can't say it's not a ripper, when it can create ISOs and burn files. It doesn't defeat any copy protection, but it can and does RIP discs. I stand by what I said. Nothing you have said in any way refutes what I said. I think you're getting the point. Creating ISOs and burning files makes it ableto "rip" things. Ripping doesn't have anything to do with removing protection. They are separate issues. People tend to confuse them. Windows Explorer can't create ISOs or burn DVDs. So get a clue before you hurt yourself. You've given an analogy that doens't even hold up. I repeat. Nothing you have said in any way refutes what I said.

Thank you! Are you trying to get a rise out of me, Agent Jill? If so, your attempt failed. Good job making yourself look bad. Everyone can test whether my posts are full of @#$. So, don't bother adding any substance. That would be above you. Your vocabulary is more full of $#!@ than anything else, apparently... EDIT.

Yeah, well, then LUK can just disable over-burning, since it's such a bad idea. How can it damage the drive in Test Mode? Nero CD/DVD Speed doesn't lock up the drive when I use it to test a disc's over-burning capacity. I'll continue over-burning. I've never experienced any damage to the drive. If I do, then I won't cry too hard about paying $40 for another. And I'll remember not to burn that much data in the future. Re: the "dangers" of over-burning. I've read up on the subject and tested a lot of things to see what's safe. I only had trouble when I tried burning huge images, in Test Mode, just to see where it would fail. I don't see how I could damage the drive. I learned that MCC 004 fails at 4633.8 MB and YUDEN T02 fails at 4637.2 MB. I don't plan on burning that much. I would stay at or below 99% of that, just to be safe. I hate compression. I either over-burn or use a dual layer disc, if something is too over 4482-4489 MB.

Why can Nero CD/DVD Speed perform the same operation without hanging? I've left it running for an hour and ImgBurn wouldn't stop or close. It would respond to input, like opening menus, but the drive was locked, and nothing would make the program shut down. It does this even in Test Mode. Is there any way to recover from this, without a hard reboot?

I'm not having problems with the discs. They play fine. I tested the last chapters in a picky machine. They have played perfectly up to 4600 MB. The problem's when I test the over-burn capacity of a disc. It will lock up the program if you burn too far, even in Test Mode. It just hangs on finalizing the disc. There was no way to unlock, except a hard reboot (after closing programs and saving data). I always burn at 4x or less, esp for over-burning. I would never burn anything over 8x, because the quality isn't that good. I've tested over-burned discs in two players and the end plays fine. Most of my burns are under 4560 MB. Only a few have been over that. They play OK, so that doesn't worry me. I would like to know how to get the program to shut down properly if over-burning a DVD fails.

Whether it's a good idea or not is decided by the user base. The program warns you about other things, like when you try to burn a DVD video with the wrong settings. Why not warn you if the drive is not set for DVD-ROM book type? He doesn't have to do the work of fixing the settings, but just a warning in the log, or a pop-up telling you it's best to use the DVD-ROM book type. Afterall, LUK has frequently told people to use DVD-ROM book type when they were experiencing problems. If the program told them, it would save some time in answering support questions.

Last time I checked, Pioneer couldn't bit-set DVD+R or DVD+RW single layer. I don't see why DVD makers don't get with the program. All drives should do bit-setting all the time. Anything less is just lame. Why would someone make (or buy) a drive that can't do bit-setting (Pioneer), or that will forget to do it after every reboot (LG)? NEC and BenQ do not have this annoying behavior, so they will continue to get my business. Any drive that doesn't support full bit-setting with official firmware is less than worthless.

I appreciate being able to over-burn discs slightly (100 MB or so). But if you go too high, ImgBurn (and DVDD) will lock up and refuse to shut down. Even when using Test Mode, this happens. They can't be terminated even through the Task Manager. This should be fixed. We need to be able to force the program to stop when over-burning fails, not lock up itself and the drive. It would also be nice to have an option to test the discs for over-burn capacity. Nero's CD/DVD Speed isn't accurate. It's off by 25-36 MB (14-20%) in what it predicts the additional capacity. I've burned 4600 MB without problems. It'll go as far as 4633-4637 MB, based on my tests, but 4630 is probably the limit for safety. Good media is essential, e.g. MCC 004 or Yuden T02.

I have also noticed consistently higher error rates with ImgBurn (all versions) than DVDD. I'm using YUDEN-T02, MCC 004, RITEK G04, and MKM 001, burned by NEC 3540 and BenQ 1640. Newest firmware in each. I burn everything at 2-4x. Despite claims to the contrary, I've found there's a difference between the two programs. ImgBurn doesn't burn as well and discs are more likely to have skipping, freezing, or pixellation in picky machines. The errors are only a bit higher, like 1/3 to 1/2, but the playback is worse than the relative increase would indicate. I have seen everyone deny this repeatedly, but I have burned dozens of images with media from the same spindle and the pattern is undeniable. Nothing can be faulted in my media, drives, or burning methods. By the way, the reason I burn at 2-4x is because that minimizes the problems, but I still use DVDD for burning as much as possible. It's far better, IMO. ImgBurn would be great, if it weren't for all the bugs and inconsistencies. EDIT - shortened, corrected

Try hitting Escape while your computer is booting up. That should bring up a menu to select the boot device from. Choose the drive your Windows CD is in. Does that allow you to boot the CD? {EDIT}

I'm not asking for his expertise or hard work. That's his choice to give. I have no trouble understanding that he wrote it. That's irrelevant, tho you seem to use this justification every chance you get. I'm having trouble seeing where I have "ordered" him to do anything,or said I would "hold my breath and stamp my feet" if he didn't do it. Perhaps you can quote the relevant lines where I made such orders, threats, or ultimatums. If not, kindly omit such junk from your posts. You aren't fooling anybody. Have some decency. Your responses are as empty and distorted as they are insubstantial. That's what happens when you completely ignore what I say and go off on a rant about what you imagined about me. Go back and read what I said. I am not doing anything childish. You can choose not to read or respond to me if you don't like me. I'd *prefer* that to this drivel you keep posting and attributing to me. Why not just respond to what I say in a charitable and rational way,or else leave it alone? Making up lies doesn't improve your standing. Look at yourself and stop judging your neighbor. Show me where I have complained. Like everything else, you are just distorting what I said and changing the meanings of words. To complain means "To express feelings of pain, dissatisfaction, or resentment." Where have I expressed pain, dissatisfaction, or resentment? I made a suggestion. I asked for an explanation. I think what you mean is that you don't want anybody questioning LUK et al. It has nothing to do with complaining. Fine, the subject can be closed in your mind and LUK's. That's your choice. The answer was dismissive and trite. "With enough time & effort - I don't want to do it." You refuse to actually engage in civil or logical discussion. You attack anyone who goes against the grain here..You can believe what you want about me, but you clearly do not know anything about me. You don't even quote my messages. Just distort them with a lot of lies. Very unimpressive.

Then it is not something for this Forum. ImgBurn is clearly working as it should. No, it's not. LUK admitted that it was a problem and someone in another thread said that it would be fixed soon. It's a problem caused by ImgBurn's Build Mode messing up DL images created from hard drive files. The problem is caused by ImgBurn and introducing mastering errors. If the images are not mastered correctly, then that is your problem or concern.It doesn't matter what program reports it. That's completely irrelevant. Either the images/discs are mastered correctly or they're not. I have found they are not mastered correctly when I create images from files on disk. That reduces my faith in the program and I'm sure others react the same. I will not use the program for creating dual layer discs until this issue is fixed. I think that is a valid position to take, unless you show my concerns are unfounded. LUK specifically told me that this thread was on-topic. You are totally off-base, and off-topic. The software is buggy and I'm not going to apologize for saying that it is. It works great if you don't care about dual layer. I would prefer that my discs not have mastering errors reported. That's just me, though. I'm not "going on" about anything. I added some information and you attacked me in a totally off-topic and hostile manner. If I am off-base, why are my posts not deleted? Maybe your 12 year old has a problem thinking for himself. Maybe you're just using hyperbole to make your points.

Wrong again, Blutach. I don't understand where's the challenge in READING FILES from an ISO. Perhaps you can provide a superior explanation to "With enough time and effort, anything is possible." Are you up for that challenge, or will you just continue taking the easy way out by simply attacking people? My, aren't you helpful? Don't bother adding any substance to the discussion. Just attack me and walk away. Is that what it takes to get your kicks? Does it compensate for your life? I don't care what LUK does. I suggest something that seems useful and easy to implement. I get a dismissive answer. Then I'm told that what I don't understand is "the no bit." Do you understand how wrong your condescending characterizations are?

Do you really figure if you prod enough it will happen?... No, I figure that LUK will just refuse to do anything I suggest, because he has a personal problem. I think his claims that it would be difficult to do are false. It would be no more difficult than reading the files on an ISO, which ImgBurn already does. If I prod enough, he may begin to think outside of the box he seems to be operating from or at least admit the reason he doesn't want to implement such a trivial and useful feature. What about the answer that LUK gave me are you able to understand? Is it that difficult to READ FILES from an ISO? That's shocking. I wonder how on Earth programs like WinRAR and ISO Buster were able to reach this level of sophistication, when the author of a burning program sees it as a challenge. I understand that LUK doesn't want to do it for some reason. I think it would be as simple as plugging one piece of existing code into another. His answer didn't have enough substance for me to understand. EDIT

I'm not debating anything. I'm saying that the problem doesn't occur if I make an ISO from the disc with ImgBurn. I am trying to isolate what's causing the problem. LUK's theory doesn't explain why the problem happens one time and not another. $38 for life time upgrades is hardly overpriced. I haven't asked anything aboutAnyDVD. I provided information about how to reproduce a bug. AnyDVD doesn't report "incorrect mastering" when I use Imgburn to make an ISO directly. So, I think some other software might need to be considered. Asking AnyDVD would achieve nothing, since AnyDVD isn't producing the image. I only mention the programs to show how I produced the error. The error does not occur when I make an ISO with ImgBurn directly. It occurs when I use it on files generated by other programs. If ImgBurn produces DL images that aren't mastered correctly, then it produces DL images that aren't mastered correctly. Flinging invective does nothing but discredit yourself. Regards?!?

You could have stated your response without all the useless repetition of your initials. I've learned that AnyDVD doesn't complain if I make an ISO with ImgBurn directly. Why wouldn't the error happen there too? Maybe it's caused by an interaction with other programs. I use ..., Shrink, and PGC Edit for most of my back-ups. Thanks much. EDIT

The demand on the I/O system is more the problem, I think. Perhaps this isn't an issue if you have SATA. Not everyone has a cutting edge system. It makes sense to allow people to limit the speed for ISO write just as you can limit the speed in other modes. Why not force you to burn everything at max speed, if that's LUK's philosophy? We seem to be going back to the all-or-nothing logic, common in other threads here. If that's the only answer people can offer, you might as well not even bother responding. I think customization has value and yes the option to do things slower has value. Whether you agree with that is irrelevant. What would it hurt to have the option?

I don't have any problem browsing or editing documents or even watching a movie while it writes, but it not go over about 20x average and 60x max. Multi-tasking certain applications creates a lot of slow down.