LIGHTNING UK!

Please put a new blank disc in the drive, go into Write mode and then copy + paste everything from the box on the right of the main window.

You're making a double layer disc / image. Pick a layer break position and click OK.

Verify when you burn and post the log please.

The link to the file in the first post works fine. You can always just use something like Audacity to reduce the volume and resave the file yourself too.

You aren't burning an Audio CD, so your player needs to support playing flac files from a data disc. Does it?

Maybe you just need to install Madflac? It's mentioned in the guide (last page/post)

It's a buffer used for when reading the files from the source location. The files have to be read and processed, building up the file system that then gets written to the disc in nice little disc sector sized chunks (via the I/O buffer I mentioned before). So it's an input buffer rather than an output buffer.

The speed it resumes at would be down to the drive. It's probably slowed itself down because it's realised your machine can't keep up at the original speed for whatever reason.

It's on Page 2 of the I/O tab in the Settings.

You burnt them as a data disc? as in, you have flac files on the disc or you made an audio cd? if you still have actual flac files on the disc, they’d have been written as-is. No data gets lost. if you burnt an audio cd, the directshow filters installed on your pc would have handled the conversion into the format required for an audio cd. Perhaps one of those misbehaved.

Drives are built around the mmc specs. That’s how you communicate with them. There might be a higher level call you can make that either uses cached data from the OS or issues the two calls in the background on your behalf, I’ve no idea about that though as I work with the actual mmc commands.

Something in your directshow filters list must be causing this. make a new cue with one of the problem files and right click it in the list so you can view the filters list. please let me know what it says.

I don't recall it having command line usage for that, no. ImgBurn follows the MMC specs and uses SCSI_PASS_THROUGH_DIRECT via DeviceIoControl. From the MMC specs, you'd probably want the 'GET CONFIGURATION' command and the 'DRIVE SERIAL NUMBER' feature.

The first error is the important one, not a thing that pops up after a retry. Your drive reported a ‘write error’ while trying to burn the disc. So, it didn’t like something about it. if there’s no better firmware you can use, there’s little you can do about it. if it’s a fluke failure, try another disc. If it keeps failing, you could try enabling the ‘perform opc before write’ option to see if it enables the drive to do a better job. Enabling defect management is also an option, but that slows down the burn and uses up disc space.

I’d always use Sao/dao. I do recall a few discs needing raw-dao 96 due to early copy protection efforts, and of course, ImgBurn doesn’t support that.