dbminter

By it's down to what the drive does means what it says on the tin. A disc can have a write descriptor of 16x but only write to 8x depending on the drive. The drive also has to have in its firmware the write strategy to support that maximum speed. If it doesn't, it will only write at the maximum speed the firmware dictates. Plus, many BD-R are rated at 6x but a lot of drives will write at 12x or even 16x for them. The drive basically does what it's told and does its best to interpret the instructions it's given. The drive sometimes doesn't always do what it's told. And you'll get random misbehavior, too. A disc may be rated 16x, ImgBurn says it will write at 16x, but the drive only writes at 8x for whatever reason. Some drives even have in their instruction set to do this. LG's, for instance, will write 6x BD-R Verbatim media at 12x, but if there's drive read threshold encountered, many times when the LG resumes writing, it's capped at 6x. The LG I got rid of was doing this. 16x DVD-R were said by ImgBurn to write at 16x, but were only writing at 8x.

As for the 2nd thing you're talking about, I don't know. As for the volume label, you can set that manually before you press the create/burn button. Then you won't be prompted to do so. You might be able to turn off these checks with these options in the Settings. I don't know, but you can always try. Tools --> Settings --> Build --> Page 3 tab --> Prompts --> Check the two boxes that say Don't.

Ah, now I see why you were trying to load an audio CD image in a game emulator. That's why I was thinking it was failing in RetroArch. Because it probably doesn't support audio CD images. Whoever made RetroArch probably didn't code in support for audio CD images, thinking there would never be a reason for them in the software. They were probably not aware of something like Monster Hunter being able to do that. Even though the old PS ROM supported playing audio CD's, it probably wasn't supported for playing back in RetroArch because Windows can natively play CD's on its own. So, the function was considered redundant. I admit, a lot of the time, I just thought this was human error. That you were trying to load audio CD's in a game emulator. But, there was actually a reason why you wanted to do that.

I could whip up a single track, really small audio CD with ImgBurn, but I'd have to burn it to a CD-RW and image that, since none of the virtual CD writers I tested ever worked. Which means my image files will be in CCD/IMG format, the only way I can test them with VirtualClone Drive. Which means you'd have to install VirtualClone Drive. And if you're going to do that, you might as well, before I do anything, read this disc to a new CCD/IMG format and test it in VCD yourself. To enable CCD/IMG creation, go into Tools --> Settings --> Read and check the CCD box under Image Layout File Format.

ImgBurn is fine for most disc reading, but certain instances and combinations of certain drives and discs aren't the best. For instance, some PS1 games can't be read in on certain hardware because they apparently have gaps in the audio tracks. Mega Man 8 is one of them that won't read in my Pioneer in ImgBurn but will in Alcohol 120%. I use Alcohol 120% for those cases where ImgBurn won't read a PS1 game disc. Other than that, I've never had a problem with other disc image formats. You sure it's an audio CD and maybe not a mixed mode CD, combining an audio track with a data track? Generally, those aren't a problem, but if it's a game disc instead, that might be a problem. You're doing it right, but there could be a wide variety of issues at play here. Your drive may be the issue. The disc may not be authored correctly or is some weird form of disc. Just to be sure you didn't get a bad read, try reading it again to a new set of BIN/CUE and attempt to mount again. Since I'm only familiar with VirtualClone Drive and Alcohol 120% as virtual drives, I couldn't say why WinCDEmu doesn't like that image set. You can't use BIN/CUE with VirtualClone Drive (Well, VCD will mount BIN files, but they don't play as audio CD's in VLC. I tested that out.) so you'd have to enable CCD creation in ImgBurn and read to a new image file set to mount it in VCD. I believe Alcohol 120% creates its own image file format, but it may support BIN/CUE already existent.

Never heard of WinCDEmu, so I couldn't say. As far as I know, ISO isn't for audio CD's or any CD format. As for why it may be a corrupt image, well, the image is corrupt or it isn't recognized as a compatible image for WinCDEmu. And that could either be a bad read or simply a bad disc. Maybe it wasn't authored correctly. Could be a lot of factors and my having no familiarity with WinCDEmu, I can't say.

Ah, that's what I did! I set ImgBurn to create.CCD files because VirtualClone Drive didn't appear to support .CUE files when I tried it out. But, it did mount .CCD (CloneCD) files because I think the same software company that makes VirutalClone Drive makes CloneCD. Which may explain why my CUE file didn't play in VLC. VLC may very well support BIN/CUE, but I only had IMG/CUE. I turned off CCD creation so I'd get a BIN/CUE image file set of the same disc to test again. VLC simply does not support playing CUE files.

Well, I've no idea why VLC associates CUE with itself because it does not support playing audio CD's from CUE/IMG file sets. I tried it just now. VLC does not natively support playing CUE/IMG files. I made an image file on a CD that VLC will play from (I tested it.) and VLC did not play the CUE file ImgBurn created. I tested a 2nd image file I made years ago for testing purposes and the CUE does not play. Now, it may work with BIN/CUE but without being able to create BIN/CUE to test, I can't say. I mounted the CCD file ImgBurn created with the IMG/CUE in VirtualClone Drive and VLC will play a CCD mounted IMG/CCD/CDT/CUE file set created by ImgBurn. What I don't understand is why ImgBurn is creating a BIN/CUE set when, for me, it created a CUE/IMG set of a CD.

As far as I know, no software player will natively read in BIN/CUE of audio CD's and play them. Now, if you mounted the image with, say, VirtualClone Drive, VLC, if it supports playing audio CD's (I don't know.), would play the image file as a virtual drive, if the image file isn't corrupt.

There are two ways to do that. First, use ImgBurn to burn the CUE file's BIN file to a CD-R or CD-RW and see if that disc plays. The second is to installing an optical disc emulator software like VirtualClone Drive or Alchol 120%. Both are either freeware or have a free version. You can then mount the CUE/CCD file, depending on the software you choose, and see if the mounted image plays.

Are you sure RetroArch plays audio CD's? The only two hits I found for RetroArch aren't for playing audio CD's. One for a video game emulator and one for the API that runs the emulator. It sounds like RetroArch is only for playing game CD's.

What program is this? I'm not aware of any application that can read BIN/CUE files natively and play them. I know DVDShrink can read in ISO's of DVD Video movies to process. And I think Media Player Classic Home Cinema can play DVD Video ISO's natively. But, as I said, those aren't audio CD image files.

BIN doesn't work that way, as far as I know. BIN is for entire disc images. What you probably want to is to create a container file by Ripping the individual tracks in Windows Media Player. Or you could install VirtualClone Drive. It will mount .CCD files that ImgBurn, I think, creates along with BIN/CUE.

You might have luck installing the free version of Alcohol 120%. I thought it had some kind of capability to image such discs. Maybe that's only in the paid version. Maybe I'm completely wrong; who knows?

The write speed you get out of a burn is down to a few factors. So, even if you have Max set, you may not get the highest rated speed you expect every time. Every burn, it's really down to simply what the drive does. The slower you write any burn, the better likelihood it won't encounter issues. So, if you want to set each burn to just 2x, it is something to try. In fact, sometimes, troubleshooting advice is given to write at a slower rate to see if that helps solve the problem. Near as I can remember to what I was told about the TOC, the TOC is not written to the same place each time. That there is no set "logic" to where the TOC goes. About writing to the edge of the disc, I still believe it's down to a combination of the burner and the media. For instance, I've written several 24.9 GB images to Verbatim BD-R in my Pioneer BDR-209 and BDR-2209 without issue.

If the drive is making those kinds of noises, then the drive could be scratching up media. You may want to, if you can remember, do a thorough check on the bottom on a BD-R before burning it. That way if you get scratches on it after the burn, you know it's the drive doing it. The only thing I could see making a scratch like that is if there's some kind of imperfection or raised area in the tray. When the drive spins the disc, it would be scratching against the drive tray. The laser can't be making them and the internals of the drive only ever touch the hole in the center. So, it must be something in the tray indentation itself. Supposedly, BD media is "scratch proof." I mean, if you took a pair of scissors, yes, you could scratch the bottom surface. However, relative to DVD bottoms, they are "scratch proof." Which is why you should be checking the media before you burn it. You want to make sure the discs didn't come out of the factory with scratches throughout the entire spindle.

It's possible the disc may have been scratched out of the factory. The drive may not have done it. I encountered one back in January that failed to Verify. When I examined the BD-R in the light, I noticed it was cracked all the way down the radius. Must have come out of the factory that way. Why it didn't fail during burning, I can't explain.

Then, do it!

Ah, that's a shame. I remember 22 years ago, mIRC used to queue an entire log before writing it to disk after the chat window was closed. Unfortunately, the application would frequently crash when the log size reached a certain limit, losing the log. It eventually was changed to write each line of the chat window to the log on disc after it was sent. This prevented the loss of chat logs.

Ah, then might i again suggest that each line be written to the log on disk as it's generated in case someone does have to terminate the application? I suggested this because someone else posted a problem where they couldn't post a log because they had to terminate a locked up ImgBurn.

I spoke from over 10 years of experience with LG. The old joke is LG stands for Lucky Good in that it's Lucky Good if it works right. I've had multiple copies of the WH16NS40 and they all had the same problems. They will fail 9 times out of 10 to Verify writes to BD-R and RE DL. They only write BD-RE at 1x for 2x media. It will always write corrupt data to the 2nd layer of BD-RE DL when formatted as a giant floppy. When writing to BD-R and you experience a write rate drop, the maximum it will resume writing is 6x. When writing to Ritek 8x DVD+RW, it will complete Verify even if the data is corrupt when you try to access it. The first LG drive I had was a rebranded DVD burner from IOMega. I quickly got rid of it because it would 50/50 write DVD Video discs that played back with skips and pops in the video. I only used an LG drive at all because it was the only internal BD drive that was writing to 8x DVD+RW after Pioneer borked the 1.34 firmware. I wouldn't have used it otherwise, and when Pioneer fixed the problem with their 1.50 firmware, I quickly removed the LG (It had stopped writing to DVD-R, anyway.) and replaced it with a Pioneer 209. There was also someone else who reported problems with that LG drive writing to BD DL media. After they replaced the LG with a Pioneer 2209, the problem went away. So, my experience with LG has left me with a bad taste in my mouth about their WH16NS40 BD drive. Much prefer Pioneer's 209 and 2209 BD drives. As for DVDInfo Pro, something is causing the drive to return the disc is smaller than it should be. That would be either the drive, the disc, or DVDInfo Pro, or a combination of those things.

Every time ImgBurn generates a line in the log, does it write the log to the disc each time? Or does it queue the entire log until the operation is completed and then the log file is written to disc? If it writes the log only after an operation is completed, might I suggest that ImgBurn write to the log file each time it generates an output message? That way, if an operation fails due to a command that never completes, the log can still be viewable.

So, you have successfully burned these Ritek BD-R before? Just that you burned less than 99% of the total available disc space? It seems you're using an LG BD burner. I'd still say that LG drive probably doesn't like Ritek BD media very well. LG's, I know, are absolutely useless for writing BD DL media, so it wouldn't surprise me if it can't write 100% of the available space on a disc. Particularly a Ritek one. As I said, before I laid the entire blame on the Ritek's, I'd try some Verbatim's and see if you can write to the edge of those. It may just be that Ritek discs are pretty bad and that quality Verbatim media might solve the issue. Or the LG drive may just be pretty rotten and can't write to the very edge of any BD-R media.

Probably the drive doesn't like the Ritek BD-R you're using. Ritek is a 2nd tier optical disc manufacturer. Have you used these discs with any frequency before and they worked out okay? I'd recommend trying Verbatim BD-R and see if that can be written to to the edge. I know the Pioneer 209 and 2209 will write Verbatim BD-R at almost to the edge, just a shade under 25 GB.

What are the contents of this disc? If it's not a bootable disc, i.e. just a disc of some contents that aren't made in any fancy way, you could try just creating a new ISO in ImgBurn Build mode. See if that ISO mounts. Of course, this doesn't solve why Windows won't mount that ISO. But, you could spend the rest of your life trying to debug a Windows issue and get nowhere. It's the nature of the Windows beast. When something goes wrong with an internal Windows function, too often than not, the only solution is to restore Windows from an image where it worked before/reinstall Windows. However, it's probably just a case of a weird ISO that isn't mounting correctly as you said another image does work. Probably something wrong/weird with the source disc that is creating a weird ISO.