LIGHTNING UK!

ImgBurn is more about burning than reading. You can use ImgBurn's CLI and some other app to control the unit for the read part, ImgBurn will only use the currently selected slot. For burning (from the Write Queue), ImgBurn will automatically burn individual images to media in different slots.

Don't worry about the errors, a lot of them are expected... but you only know that when you understand them - and that's my job really, not yours Worry about stuff you see (when debug mode is disabled), not stuff you don't see.

Sorry but I've seen it before where people have already come to their conclusions. Being blunt about it just saves us both time. ImgBurn defaults to using the SAO write type, Nero may be using Incremental. Your drive should write perfectly well using either one but sometimes they just don't. That's nothing to do with the software, it's a hardware thing. Select the other write type and continue on your merry way.

It's not the end of the world anyway, you can just tell it not to capture graph data. That is of course just a workaround and not a fix for what is obviously a bigger problem.

ImgBurn has to correct certain pointers when it burns to disc due to the layout and positioning of the files. The layout isn't the same when you look at the files as files... but then DVD players don't do that, they go by the pointers.

Whatever your time doing QA has taught you, software cannot introduce errors during the burn - well, not with the type of burning going on here anyway. If the drive makes a crappy burn, it's the drive/media/firmware at fault - end of story. It would (and do) say exactly the same thing if my program was the one that worked and something else didn't.

Read the FAQ, it tells you what to do when that happens.

If the ones on the liteon tab work, hit the advanced button and add your device identifier (SONY DVD+-RW DW-Q58A) to the liteon tab in there - that way the program will do it for you automatically each time you burn.

The whole point of it being there is to fix a problem.... so it's unlikely I'll make it optional.

You should post the full log so we have all the info to go on.

Nope. Do you have a slow PC or something? It must take 20 or 30 seconds to analyse the files prior to a burn... that's not a lot of time really!

I had someone try that OS build you're using and theirs didn't hang for ages in the way yours is. Maybe you could do a rebuild of that one - or better still don't use such a hacked up version!

Do any of your settings get saved when you close the program down? You're not using an .ini file for saving them are you.... just the standard method in the registry? Open up regedit and browse to HKEY_CURRENT_USER\Software\ImgBurn The Auto Write Speed entries should be right at the stop, all starting with 'AWS_'. What do you see? If in doubt, delete the 'ImgBurn' key (when the program is closed), open ImgBurn and then close it again. Now refresh regedit (press F5) and see what's been written to it and if the 'ImgBurn' branch has been recreated.

Maybe your drive is just playing silly buggers and not updating the info quickly enough after I've told it where the new LB should be. Eject the disc and reinsert it, then copy + paste the disc info from the panel on the right. If you have any other drives available anywhere, you could try it in those too. That way we'll see what other drives make of the LB position and if it really has/hasn't been moved. I'm sure I don't need to tell you that you should be using Verbatim DVD+R DL 2.4x (MKM-001-00 dye, Made in Singapore) discs for all your DL burns do I? It's mentioned in just about every DL related thread on this forum (and most others).

That's not verifying then, it's analysing! It needs to do that so it gets an accurate/exact size of the decoded PCM info - otherwise you end up with unwanted gaps between the songs or stuff gets cut off / lost. So basically, you're stuck with it.

Can you do a complete read of that disc still? If so, I guess the drive is ok with it. If in doubt, burn it again.

Please post the rest of the log. That said, everything I've said above this post still applies to you!

before write? Verify happens after the Write operation and is controlled by the 'Verify' checkbox in the 'Destination' groupbox on the main screen.

Change 'Folder Content Location' to 'Start' and try again. (Tools -> Settings -> Build -> DVD Video)

Yes, that's correct. You use ImgBurn for the actual burning part... but you only do that once you've got a proper set of file to burn.

Use tsmuxer to make the proper bd layout then. You're not inventing the wheel here, I'm sure there are guides for this on Google if you search. The Doom9.org forums must be full of the stuff.

Drag the BDMV folder to the 'Source' box in Build mode and then click 'Write'.

Why would you join the ImgBurn forum and post this kind of question in the ImgBurn Support section?! Surely you'd at least be using ImgBurn wouldn't you?

Hmm I guess I need to extend my 'Create CERTIFICATE Folder' option from a simple 'Yes / No' checkbox to an 'Ask / Yes / No' combobox. It doesn't even sound as if I can always leave it out when I know I'm burning directly to DVD media. I guess I could always include it when going direct to Blu-ray though, that should be safe enough.

It means your drive can't read (verify perhaps?) the disc.