LIGHTNING UK!

The only thing that can make the drive error out like that is the drive itself. Only 3 things are involved in the burn quality (or lack of) and that's the drive, its firmware and the media you're using. No software can force it to write to something it doesn't want to, just like no software can make it not write to something it wants to. All ImgBurn is doing is feeding it with a stream of data. The DVD+ (plus) format does not support test write and even if it did, you'll only get write errors when the laser is actually 'ON' and writing. Switching to incremental works sometimes and fails others, all you can do is try it. What I have to make clear however is that you shouldn't *need* to do that if the driver/firmware/media combo were all playing nicely together. btw, you can get Verbatim DVD+R DL's for about

Verbatim media?

Read the audio guide in the Guides forum.

Personally, no. But then I don't use Ricoh DL discs, I use Verbatim. It can happen on any media the drive has problems with. Yes, in the 'Settings' on the 'Write' tab under 'Write Type'.

Just update the firmware anyway! Make sure you try burning at each of the 'supported' write speeds too - i.e. 2.4x and 4x.

If you've got a VIDEO_TS folder (complete with IFO/BUP/VOB files), just follow any one of the numerous DVD Video guides in the 'Guides' forum.

There's nothing to say that Nero can/is even looking for errors in these finalisation stages. Also, it uses the incremental write type and not dao. Sometimes one will work when the other doesn't - it all depends on how the drive is feeling that day. The content of the image has nothing to do with why it's failing. This is purely a drive/firmware/media combo issue.

That means the drive is probably still busy processing a command. ImgBurn isn't in control at this point, hence you can't quit. What you need to figure out is why your drive / machine is getting stuck like that. Is the firmware on the drive up-to-date? Are you using decent Verbatim/Taiyo Yuden media? Do you have the drive setup properly on the correct controller and with the correct/up-to-date drivers?

Fast Write wouldn't do anything as the error is being returned by the actual 'FORMAT UNIT' command, all be it delayed. Once the 'FORMAT UNIT' command has finished doing it's thing, ImgBurn then writes zeroes to every sector on the disc - that's where the 'fast write' bit comes in. To be 100% sure the drive is ok to burn to every sector I'd probably leave fast write off for the erase. That way, the drive's automatic write/verify process will point out any dodgy sectors. I've never used the LG media, it's still sealed up in the box with the manual etc. I only have verbatim BD-RE discs and a panasonic BD-RE DL one. Spare areas doesn't apply to DVD-RW, only DVD-RAM and BD-RE.

See now that's a totally different problem. Your drive is unable to read back that sector and is timing out - Samsung drives tend to do that after 10 seconds. If the drive can't read the disc (and it's a data one) then it's pretty useless. Another drive might have more luck though. If it was a DVD Video disc you might find standalone devices are more forgiving, but it's not! Where were your verbatim discs made? Look on the box / packaging / spindle / tub. btw, adding 4 bin/cue's in build mode (which basically just backs them up) doesn't mean you can verify against any one of them - that won't work, period. If you were trying to get a usable disc with the program somehow magically merging the 4 cd images into 1 bigger dvd image, you'll need to rethink things as it just doesn't work like that.

There's not really any problem here. The image file data sent to the drive has been corrected on-the-fly (by the drive) during burning and you can't really avoid that. (not with ImgBurn anyway as it doesn't support the 'RAW' writing mode) If the disc doesn't play then it might well be a protection issue and again, ImgBurn cannot help you with that... and nor can we.

I believe the spare areas are used for defects / sector remapping etc. I don't know much about it. The error isn't a good sign, what discs are you using? I've never had such an error when using my verbatim bd-re discs and we have the same drive. The drive seems to have a problem with formatting the sectors at the end of the disc (as it failed on 99%). Still, it looks as if the drive did then manage to write all zeroes to the sectors so it's not all bad.

An ISO isn't something you convert, it's something you burn *as is* to a disc, sector by sector. If you have an ISO, burn it in 'Write' mode. You can also mount the ISO in a virtual drive program like DAEMON Tools and then see what's on the disc (i.e. inside the ISO) by just browsing it in Explorer as you would do any other disc.

Maybe it's a size thing. The disc is pretty full there and you're only using the cheapo Ricoh discs. How many times have you tried burning it? Have you tried using a LB position that uses less padding (i.e. so the data going onto the disc is smaller) ?

Sorry, it won't happen.

This isn't really the place for that.

Ok well you can't do anything with 'project' (ppp) files, you need to export the project video etc to a proper movie format - be it an AVI, DVD Video (VIDEO_TS) files etc. I'm not familiar with the tool you're using so I can't help with that. It's probably best that you read the cyberlink help manual or something so you can figure out how to use it properly.

It helps to have the entire log from that burn+verify session.

You're verifying that 8GB disc against a 472MB image - is that on purpose? BIN/CUE files should be burnt to a CD, not a DVD and certainly not a double layer DVD! It's impossible to say that there's any problem when looking at the log above. Yes there are miscompare errors (normally from bad memory or filter drivers messing things up) but it looks like you might just as easily be verifying against the wrong image.

I should have mentioned to set the 'Speed' to 4x and put the 'Show PIE' and 'Show PIF' on 'Block'. In any case, it's not going to solve anything so don't worry too much... just make sure you use the settings above next time you need to scan. Your current ones aren't producing accurate graphs and they're much harder to read than they should be.

It'll burn as much is free. Look in the disc info panel on the right, it tells you everything you need to know about the sizes. BD media has 'preferred' sizes and max sizes. To use max you need to format it without spare areas (option in the settings).

It's pretty obviously that ImgBurn's current 'Build' mode is meant for burning from an existing hdd structure. If / when that changes, it'll do what you want it to. Personally I'd laugh at someone that's got a backup of something twice on a disc. If it's that important you'd have multiple copies on different discs, not the same one.

I'm not going to integrate anything. ImgBurn is designed to work with DirectShow and whatever filters are already installed (or can be installed).

You can't really tell from that. Maybe you can bring up properties (right click) on the source box. Some filters will offer a little info / about / configuration box. I guess the quick way to test is to see if you can uninstall dc bass source and then open the flac again. If it doesn't work then there's no chance it can be anything other than dc bass!

They both burnt and verified fine and both booktyped to DVD-ROM... so it's a bit weird that one works and the other one doesn't. Scan both discs via the PIPO function in DVDInfoPro (using the same drive - probably the liteon) and post those screenshots for us please.