LIGHTNING UK!

Load the program without a disc in the drive. Go into Read mode Put the disc in the drive and keep an eye on the status bar of the main window. If the drive goes through the motions of trying to initialise the disc and then just ends up saying medium not present, it means your drive can't read the disc (at all). This is not an ImgBurn issue. Another drive may have more luck reading the disc.

Already done.

It already uses the name of a (data) disc for exactly that. I expect the problem you’re having is that you’re taking an image of an audio cd, which don’t actually have names. For those discs, it would involve querying some sort of online database.

So you set it burning and then cancelled it once it had begun? If you were too late and the drive had already started burning, you're out of luck. Unless you happened to be using rewritable discs, a burnt disc stays burnt - that's the nature of burning optical discs. Don't blame the app for your own mistakes.

If it stops, it generally means there's some sort of communications issue between your computer and the drive. ImgBurn will have sent a command to it for processing and is simply waiting for a response. Does it have enough power? Try another USB cable / port perhaps. When it appears to be stuck, if you unplug the burner, your system should error out.

It isn't... the calculation is just a bit off. Drives usually ramp up to their chosen speed slowly throughout the burn. So if you pick 32x, it may start at 16x and then build up to 32x... which would only be reached at the very outer edges of the disc (i.e. when you've filled the disc up 100%).

What happens if you pick 24 or 32 as the write rate? Does it still max out at 14x? The 14x could actually be a cosmetic issue as I fixed an issue to do with CD read and write rates a million years ago. There hasn't been a new 'public' release since I fixed it.

If you get an actual error during the verify phase, it shouldn’t be ignored. If your drive just stops doing anything, it’s probably more of an issue with your setup than the burn / discs. Do you have the drive’s data usb cable plugged into a usb 3.0 port? I’m assuming it’s designed for usb 3.0. Most BD drives would be.

Yes, definitely use both usb plugs, otherwise it won’t have enough power to actually burn!

If the drive has just stopped doing anything, you’re probably out of luck. The I/O (commands and data) going to and from the drive must have got stuck. Pull the plug on the drive and the program will probably be able to display an error.

You must have that option being forced by something (a settings file maybe?) as it certainly remembers what I set it to after being closed / reopened.

Yes, besides being made for images using file splitting, it’s made for anything with a layer break and for anything under 1gb in size - as that’s the cut off point for daemon tools to emulate a cd rather than a dvd.

Try another usb port / cable etc.

I don’t recall them ever actually releasing rewritable dual/double layer dvd media. I guess they had their reasons for that, but I’m afraid I don’t know what they were.

It might be the 'Delete Incomplete Files' option on the Events tab in the settings.

It might be tied to the batch mode checkbox.

It won't *only* be making the mds file, the ISO will be there somewhere too. Make sure Explorer is configured to show file name extensions.

You're also burning at max speed. Try slowing it down to 3x or 4x.

The log only gets saved when you exit the program. If you haven't done that yet, copy and paste everything from the log window instead (use CTRL+A to select all of the it). Your posts are missing key info that we'd normally easily get from a complete log of a burn/verify operation.

When using file splitting, it would be making a layout file. As it then knows it's made one, it would load it. You're in a situation where no layout file has been made, but one exists... therefore you run into the situation where ImgBurn basically tells you off for loading the wrong file. I could perhaps silence the prompt when it knows no layout file has been created but one with the correct name (as per the built in checks) exists.

On quick examination of the code, if the program thinks it has made a layout file (CUE/DVD/MDS etc), it'll use that file when loading into the Write mode queue - so you should not be seeing the message you're seeing. Do you always output to the same folder / file name? Your issue may arise if using the same output folder and file name - whereby one build HAS made a layout file but a subsequent one hasn't (the files from the previous build still exist). Write mode checks for the existence of a CUE/DVD/MDS file with the same name as the file you've loaded and then displays the message you're seeing if it finds one.

I'm guessing you must have the 'Add to write queue when done' option selected within Build mode?

Your machine probably lost connection to the drive and the I/O request has basically got stuck. If you unplug the drive, the program may well eventually get an error back from the OS that it can show you. You are using the Y cable into 2 USB ports yeah? You need one to be USB 3.0 for the drive to achieve the speeds it's capable of, but it may also need that little bit of extra power USB 3 provides over usb 2.0

It isn't, which is why the program wouldn't choose ISO for an Audio CD.

It'll use ISO for single session / track (mode 1 track) discs. For other CDs, it'll default to BIN (with the accompanying CUE file). I don't recall ever adding a setting that tells it to always use BIN/CUE - even for basic discs where ISO is easier and usually preferable.