LIGHTNING UK!

Thank you. Well... you can't have a file of total length 02:00:13 and have something starting at 02:00:13... you're already at the end of the file. Looks like a bug in whatever made the cue/wav files. Easiest course of action here (assuming it's the same issue with all of the files) is just to remove all of the INDEX 00 entries.

Well, I can't see any 4 second tracks but there are lots of 0 second (and frame) index 00's, which I guess is also a no-no. Maybe next track pregaps at the end of the previous track aren't supported at all? Could you fire up the 'create cue file' feature in the tools menu and add the first wave file from that set please? If I know exactly how long it it, I'll know if there should be data after the end of track 1 / index 01's supposed end (which would then form index 00 of track 2).

Please don't do the above, it will mess things up. Once you've loaded the CUE in Write mode, click the 'Image Information' button and take a screenshot of what it says please. You may need to scroll the window and take a 2nd screenshot so I can see it all. Normally a drive will reject a cuesheet because a track is coming out as less than 4 seconds in length. So it could that be the program doesn't really like your CUE (pregaps for the next track at the end of individual track wav files are a bit complex) and a track length is being calculated incorrectly.

If your player compares folder names character by character, the 1 at the start of 100-199 would put them before 20-99. That’s why you need the leading zeros.

For whatever reason, the response to the ‘inquiry’ command is corrupt. That’s where the name of the drive comes from. Has it always done that on your system? Try turning the machine off and on again. Try removing the ide/ata controller from within device manager and rebooting. Have a look at which filter drivers are installed ( option on the tools menu), maybe you have one that’s messing with the actual response from the drive.

I don’t even know how that’s possible?! It’s not an issue I’ve seen before. I’d say to enable I/O debug mode by pressing F8 and then scan for devices again (tools menu). Once the drive has been found and the log window settles down, turn off I/O debug mode again and save + upload the log for me to look at please.

What have you been using? 01,02,03… 99? If you go over 2 digits, you’d probably need to use 001, 002 etc.

It’s my own code.

That’s a strange error to report. At this point, assuming the files are what you say they are, I’d have to say madflac didn’t install correctly.

If you've followed the Audio CD guide and created + burnt the CUE file, your tracks are absolutely in the order you put them in. There's no such thing as 'alphabetical' when it comes to CD-DA discs because there's no file system to begin with. This is the guide you should be following:

A quick Google later... https://www.cdrom2go.com/dvd-plus-r-dl-double-layer

The disc you burnt at 19:04 (according to your log) looks fine to me. As you've burnt it at max speed (48x), there's a chance the burn quality won't be quite as good as if you'd burnt it at something like 24x - meaning it might be harder to read and some drives may totally fail. It was totally readable in your burner though, so playback should be possible on your PC. If you want names to show up in a standalone player, you need to be looking at adding CD-TEXT to it. You can do that when you create the CUE file based on your MP3 files. ImgBurn can read the ID3 tags (if present) in MP3 files and create CD-TEXT info from them, you just need to instruct the program to do that. I think the Audio CD guide in the Guides forum does cover that, so please take a look at it.

Yes, as dbminter has said, the log of the MP3 -> Audio CD burn would be useful here please.

Goto Tools -> Settings -> Read -> Page 1. On there you should see the 'Read Errors' groupbox. Change 'Software Retries' to a lower number (1 or whatever) and then tick the 'Ignore Read Errors' box. Your drive will probably slow itself down if it hits a problem area on the disc.

You haven’t told me what you want it to do. The options can mostly be found in Tools -> Settings -> Read

What do you want to happen in such situations? There are several setting that can be adjusted to make the program / drive behave differently when it comes across bad sectors.

Ok, try going into Tools -> Settings -> Read -> Page 2 and change the value of Disc Layout Method -> Blu-ray to 1-3-2 or 3-1-2. It may then ignore the fact it has multiple tracks and just go by the TOC / Disc Capacity. Once you've made your first ISO, it'll probably be worth mounting it in a virtual drive and doing a file level comparison of everything on the disc to make sure it all works correctly. Once you've done that and are happy with the results, go ahead and process all of the discs using the autoloader.

No, build mode won't really work with the autoloader... not how you want/need it to anyway. Can you go into Read mode when one of those discs is in the drive and then copy + paste all of the disc info from the box on the right into a reply please?

I’d be blaming your source DVD Video structure / files here. As it burnt and verified successfully, this disc itself is fine. It’s perfectly possible to burn rubbish… but that isn’t ImgBurn’s fault, it burns what you give it.

Yes, they would be different for each game, but you specifically asked about a 733MB one. As mentioned in my previous reply, if the 'Time' comes out below 80mins, you're fine. The 640MB / 700MB mentioned on 74 / 80 minute CDs is for when you're burning 2048 bytes of data to the sector (what we call Mode 1 / 2048). The sector can actually hold 2352 bytes of CD-DA, which takes you the equivalent of over 800MB... which is obviously loads more than your 742MB or 733MB images.

That wasn't a trick question btw, the audio could be files within the data track or they could be CD-DA tracks in their own right. I just wanted to be clear which was the case with this specific game. What does the program actually say when you load the CUE file in Write mode and look at the 'Time' field in the 'Source' box? Ignore the size of the BIN file itself as CD-DA will throw that off (if you're purely going by the 700MB capacity). If it comes out under 80 minutes, you should be fine.

Is that a pure data image or does it have audio tracks?

ImgBurn isn't designed for what you're using it for and the style in which the drive burns doesn't support simply skipping and then later retrying the skipped files. There are real hdd backup tools for that job. An unreadable source file doesn't usually immediately cancel anything, you're normally offered a couple of options as to what it should do. If iTunes always causes a problem, just ensure it isn't running or whatever when you perform the backup. Once the drive starts burning, it expects to keep burning until it has completely finished what you've told it you'll be burning. You can't skip sectors on the disc because the file allocated to those sectors wasn't available at the time - all you could do is fill them with fake data - and the sectors can't then be overwritten (although technically, on a DVD+RW, they could be) if / when the file is readable. You also have the option of creating an ISO rather than burning on the fly, and then just burn the ISO. Once the ISO has been successfully built, you don't need to worry about individual files being locked by other apps.

ImgBurn only does the burning part... so where and what exactly is crashing? Is it DVD Flick or has that finished its job of encoding and fired up ImgBurn to do the burning part? The more info you can provide us with, the easier it is for us to help you. A screenshot of what you're seeing may help.

Can you post the log please?