LIGHTNING UK!

It would be useful to see the disc info from the box on the right (in Write mode) when the NS40 does and doesn't error out as the program attempts that format with quick certification (FST 0x03). Of course if you've packaged it up now, that won't be possible Just something for me to remember to check next time I'm able to. EDIT (because you just posted): I figured the NS40 would always produce that line on a brand new and uncertified disc. As you say then, it must be down to the state the NS55 leaves the disc in - this is where the disc info would come in really handy! After ImgBurn has tried its workaround to do a full format with quick certification and it fails, it tries it again with no certification. Only after that does it do the full format with full certification like you've actually asked it to. I've actually swapped that round now too as it's pointless quick certifying if you're then going to full certify.

Ah there's actually something a bit funny going on here. The bit I was referring to in the log is this bit... When I first saw your log, I wasn't near my computer and the exact meaning behind the values of FST escaped me. I figured it meant 'Full Certification' and the program was then falling back to 'Quick' or 'No' certification. It turns outs that 0x03 actually means 'Quick Certification' and that's then made me think something isn't quite right there as it shouldn't be attempting to perform 'Quick Certification', it should be doing 'Full Certification'. So I fired up the development environment to see what's happening and notice there's a workaround in place for LG drives in the WH1x and BH1x ranges. The workaround makes the program perform a full format with quick certification before then doing another one with full certification. Without that, the full format with full certification didn't seem to 'take' and the disc probably came out looking as if it hadn't ever been formatted. From what I can tell, the workaround was added back in 2010 for the BH10 and maybe BH12 models, but was set up to be future proof and work with any in the '10' range - so it's also being applied to BH14 and BH16 models that came out later on. Since then of course, LG have taken to using a different chipset for the BH14 and BD16 drives and these don't need the workaround anyway I expect. I will now adjust my workaround so it only applies to the 10 and 12 models. All that is of course beside the point! Your BH16NS55 seems to be having trouble with the disc and is remapping loads of duff sectors into the 'spare area' - only there are too many and the spare area has been exhausted. Additional format attempts might help matters, as might formatting on the NS40 before trying again on the NS55. It's unfortunate that the NS55 can't handle the CMC discs like your NS40 can, but that doesn't necessarily mean there's anything wrong with it. It could be better than the NS40 on all other media The Pioneer 209 is a good alternative, so yeah, try giving one of those a go. Oh and I never meant to say your discs were fake, they just aren't what I call 'true' Verbatims

Have you exhausted the actual intel sata ports on the MB and that's why it's on the Asmedia ones to begin with? Always opt for the intel ones over 3rd party. Glad the driver update fixed your issue though

If you burn using ImgBurn in Build mode (and the option to verify is enabled), it'll recreate the 'virtual' image (built up from your files/folders) and so verification will still be at byte level and miscompares will be picked up. Doing it after the fact when you don't have an ISO to compare against will mean it just checks the sectors are readable.

Your ns40 doesn't support the same format as the ns55. The ns55 can do the 'full certification' and is detecting an issue that maybe your other drive can't? Btw, your verbatim discs have the wrong MID. Yours are CMC.

Oh sorry, I thought you were verifying it against a disc image file (ISO). Without one of those to compare against, it won't find any miscompares and will just be checking the disc is readable in its entirety.

ImgBurn compares sector by sector at byte level. If you've modified the image file after burning it, it should pick up on it and list it as a miscompare. Please post the log from where you verified the disc.

It doesn't look like madflac is being used at all. All I see is that gstreamer splitter filter and I'm not familiar with it.

I'm afraid that screenshot doesn't show me what the problem is... actually, it makes me think your system can decode FLAC files ok.

1. It could be the drive or it could be the discs. Without trying different ones of each, you'll never know. 2. As I've said before, I can't answer that. Where a drive reports it can burn a disc at various speeds, you have to burn one (some) at each supported speed and then check them using the 'Disc Quality' PIPO scan. Examine the results and work out which speed produces the best burns. If you're saying mdisc burns at a maximum speed of 4x, I very much doubt you'd be offered anything other than 4x. In which case, you have no option but to burn at 4x.

Assuming your drive doesn't normally have a problem reading double layer discs, you'd have to assume it did a bad job of burning the disc if it's then unreadable. You could try burning at the other speeds the drive claims to support on that MID (MKM-003-00) and/or enabling the 'Perform OPC Before Write' option to see if that helps. Beyond that, you could try cleaning the drive with a cleaning discs or look at replacing it. As for your BD player not playing it... well it could be that it just doesn't support AVCHD on DVD media, or at all. Some players may not like the booktype being changed to DVD-ROM, but your drive does that automatically so you're stuck. Even with the unreadable 2nd layer, I'd still expect the device to play a 'bit' of it before failing.

The one with a total of 688675 PI Errors is obviously your best one. The others are pretty much the same or worse than the scan you posted in post #13. If you refer back to that post (and my reply), you'll see that your error levels are still a lot higher than I'd personally expect and want.

1. You can fill it to the exact capacity of the disc without any problems. 2. No. The log is only saved when it's closed down. 3. No idea. There are file system descriptors at the end of the disc if udf is used. Maybe it was trying to read them.

If the LiteOn options don't work, you're probably out of luck. I have no experience of that specific model, so I don't know if there's any way around it. You might find something of use over at the MyCE forums.

This is nothing to do with ImgBurn, why's it in the ImgBurn support forum?! Maybe try DVDFlick?

Your drive can't burn BD discs, it can only read them. It'll burn DVDs though. You have what's known as a 'combo' drive.

What do you mean? It's labelled as 'file system', so that's what it is. Only if you're planning on reading the disc in a Windows 95 machine. Beyond that, udf is supported pretty much everywhere and will normally be read instead of the Joliet or iso9660 file systems.

Your post (#50) and my reply (#51) have already covered this too.

That's the beauty of the Internet. It'll tell you everything you want to read and everything you don't want to read.

Please refer to my answer in post 29.

No idea

1. We've already covered this. You won't find the best speed until you burn a few at each and test them. 2. There's only 1 in ImgBurn. Like I said, make sure the 'verify' checkbox is ticked. 3. I'd expect a disc that's better to begin with will last longer, yes. That's assuming everything else about them and the storage methods is identical. 4. The error levels are reported by the drive. A process on your pc shouldn't alter what is an internal function of the drive and the media in it.

1. Yes, verify is not limited to certain disc formats. I don't know about discspeed, that could be more of a firmware / chipset thing as the software issues vendor unique commands in order to get pipo levels. 2. I don't have any. 3. If verify passes, it's readable. 4. They shouldn't, no.

The drive will either error out during the 'write' operation or the verify one. Just make sure the verify box is checked so it does actually do that bit. Do the pipo tests with the normal software.

Correct