dbminter

The more data you burn to a disc, the larger the extended area of the burn ring. So, 250 MB will have a smaller area than 1 GB. However, if you're burning a double layer DVD Video, those employ what is known as padding. So, their ring areas may not necessarily be indicative of the actual size on the disc. For instance, I once burned a DVD VIdeo that was just a few MB larger than the size of a DVD-5. Yet, nearly the entire DVD+R DL burn area was used.

Well, the image file size should not be the same size as the 3 input files. The image file format is a container and therefore will be larger than its contents because of overhead, file system metadata, etc. So, when you burn an image size to a disc, there will be "more" burnt to it because it contains this various metadata overhead. I can't comment on the Write files/folders to disc option as I've only ever used it to test things other have reported problems with. But I would guess that it dispenses with the overhead metadata associated with a container file as no image file is written first. Plus, it depends on the data being written. For instance, a DVD Video should have theoretically different burn sizes because it uses a specific file system format type and associated metadata for DVD player playback compatibility.

DVD-RW doesn't just go read only and there's no way as far as I'm aware of to make a DVD-RW read only like you could with a floppy disk switch or the switch in a DVD-RAM cartridge. It's either read only DVD-R to start with or your drive is read only only. Or something is wrong somewhere. When you first open ImgBurn, copy and paste everything from the Log window. Next, in Write mode with the "DVD-RW" inserted into the drive, copy and paste everything from the right hand side pane of information.

This is most likely the reason: I 20:34:39 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) CMC makes the worst discs out there. I would try better quality discs first. Like TDK or Verbatim. If you're going to use Verbatim, however, make sure you have the RIGHT Verbatim. NOT the Life Series you find in stores; those will be CMC. Get the DataLife Plus (NOT Life Series.) or discs labeled as AZO, which you will only find in online stores, usually, like Amazon. Another possible culprit is the log indicates you're using a slim model drive. Slim models tend to be junk.

Are you talking about image files or files being written to an image file? If you're talking the former, that's already a feature in ImgBurn. ImgBurn will lock in image files it's currently burning to disc. The only exceptions are the .MDS, etc. metadata files. And, I think if you have file splitting on an image set, ImgBurn only locks the portion it's currently burning from, but I could be wrong about that.

There's a way to tell a USB device's USB version. Download USBTreeView.

If you burned many similar sized discs before and it worked, then the problem could be the drive itself. It may need replacing. You may also want to try a BD-R 50 other than Ritek. Like Verbatim's VERBAT-IM media.

I have some older MP3's back from 1997 when I first started ripping CD's with a piece of software called MusicMatch Jukebox that were like 160 KBPS back before I knew of the different quality settings. 160 was the default. Once I learned the "difference," I changed the default to 320.

For 2 decades, I stuck with 320 KBPS MP3 because that was good enough. But, with the abundance of free space available now on things like USB HDD's, I switched to FLAC. And iTunes, which I primarily use now for CD extraction, uses M4A, but I choose Lossless for the quality of the rips.

If you want ImgBurn to burn FLAC to Audio CD, you'll need to download and run something called madFLAC.

Yeah, it sounded like on your previous attempt you were trying to burn another data CD with the container files rather than the CUE file, which does the conversion of the container files to Audio CD format.

It shouldn't be asking you for Joliet or any file system if you're using .CUE to create an audio CD. After you save the .CUE, you load it in Write mode or double clicking on it may open the .CUE in Write mode for you. Then, you burn the .CUE file to CD. A screenshot showing these yellow triangles may help as I don't know what that exactly means in this case.

Well, it sounds like you didn't covert the MP3's to Audio CD format. Did you or did you just burn the MP3's to CD directly? If you did the latter, then unless your CD player natively supports playback of MP3's, the disc won't play. If you want to create an Audio CD, you will need to use Create CUE file under Tools and burn that to a CD.

Depends on how you define "auto play." If you mean just pop in the Blu-Ray and have the MKV's play automatically, no. If your Blu-Play supports native playback of MKV container files, you can just burn them to a disc and load them from it, but you have to do it manually. If you want the MKV to automatically play when you insert the disc, you have to convert it to a Blu-Ray Video Disc first. I don't know of any free options that do this, but there are several pieces of paid software out there.

That log doesn't help. Depends on what made the disc that isn't finalized. You could try right clicking on the drive with this disc in it and under Close choose Session. Then repeat for Disc. Don't know how well that would work, though.

Generally, no. When discs can't be read, that's it. Optical is a generally all or nothing situation. What you might have better luck with is not a utility to recover the data but a different drive to try reading the discs in with. Try someone else's drive and see if the discs still behave the same way. If they don't AND they have a different make and model of the drive you have, you know the discs are shot.

Depends on what you're trying to do. If you're just burning some MP4 files on a Blu-Ray for playing back on a PC or a BD player that plays container files like MP4, choose UDF. If you're trying to get MP4's to play like a DVD or a Blu-Ray Video disc, be aware that some BD players simply won't play them that way, particularly if you're trying to make a DVD. You need a video converter application to make a DVD/Blu-Ray Video disc. If you've got the proper VIDEO_TS or BD folders, just drag and drop those into a Build job and ImgBurn will make the necessary file system and other settings adjustments.

I was more concerned about batch processing. There could probably be switches or default behavior where ImgBurn might close itself.

It is possible to run 2 instances at once, but it sounds like you're burning a queue of discs or you're using batch processing. I've never done either of those before so I don't know what the behavior of the software would be in those instances.

It would be highly unlikely if you received an entire cake stack from the factory that has been partially written to. So, the most likely culprit at this point is your drive. I would, at this point, invest in trying a new drive. A USB one would be easiest to set up, but most USB drives are slim models, which tend to be trash. I'd be sure to get a different make and manufacturer than the drive you currently have. One other thing I'd try, though I doubt it would help. But, it would be easier and cheaper than the above solution if it works. In ImgBurn, open Tools --> Settings --> I/O --> Page 1. Under Interface, there are a series of options you can check. Try changing these and press OK. Once the Log window refreshes to show you have the new I/O setting enabled, see if these discs still list as not empty. Try each I/O setting if one doesn't work.

I forget precisely how to fix this, but I think it's somewhat along these lines. First, insert a blank DVD. I'd take a disc from the very bottom of the package, which has the highest likelihood of really being blank. Then, open the disc in File/Windows Explorer. There should be something on the screen about files waiting to be written to the disc and the option to open the folder where they're stored. When you open this folder, delete everything in it. Particularly desktop.ini or any .ini files. I think this will return to File/Windows Explorer that the disc should be treated as a blank disc. I also found these instructions. I've never done them so I can't vouch for their effectiveness: Open Run by pressing the Windows key + R simultaneously. Type shell:cd burning, and then press Enter to open the Temporary Burn Folder. Delete all the files in the Temporary Burn Folder folder. Restart the PC.

Unless some files were added for writing to the disc in File Explorer and were never written to. Windows allows you to write files to a recordable DVD even after you've added some to them. If those files never were written, they're "queued" for future writing. This might explain why every time you insert a new blank DVD-R it's showing files are to be written to them.

Well, it appears SOME data was written to it. In the first screenshot, just under 0.2 GB are on it.

Okay, that means your discs aren't blank or your drive thinks they're not blank. Most likely the latter. Try opening one of these discs in File/Windows Explorer. See if there are any contents on these discs already. In which case, I'd just invest in a 2nd USB burner drive and connect that. Then, try again. Preferably, don't use the same model drive. Although the metadata shows 154 MB is apparently on this DVD+R you inserted.

What happens when you try Read mode on one of these blank discs you put in your drive? What does ImgBurn say about the disc?