LIGHTNING UK!

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

Ok, so I added 1 folder to the little 'source' box. When I go the burn the disc, I'm presented with this messagebox. It's relatively clear to me as to what I'd do in your situation, but I realise you're not a native speaker of the English language. You'd need to click 'No' if you want the actual folder in the root of the disc.

Actually, that can happen if you're in standard input mode and only add 1 folder. It'll prompt you to ask if that folder represents what should be the root folder of the disc. What happens to that folder then depends on your answer. I don't mind if the op asks extra questions in their topic. I'd rather that than them hijack someone else's.

Also, what you've burnt there seems very small. Is that intentional?! You must have used less than 1% of the available disc space.

1. No 2. Yes, using the aptly named 'Restore Defaults' button within the settings. 3. No

The defaults work fine. There's very little to actually configure for burning discs. The drive and firmware control all the technical stuff. Software pretty much just sends the data.