Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,458
  • Joined

  • Last visited

Posts posted by LIGHTNING UK!

  1. 2 minutes ago, Ken852 said:

    Is there any advantage to using IMG/CCD over BIN/CUE?

    I have installed Daemon Tools Lite 10.14 and I was able to mount the BIN/CUE files and have it present as Audio CD in File Explorer and have it play some tunes off of it in VLC.

    I'm supposed to point Daemon Tools at the CUE file rather than the BIN file? By trying to mount the BIN file, I got the same error as I got previously using Virtual CloneDrive ("disc might be corrupt"). But selecting the CUE file instead made all the difference! I can tell now why I must keep the CUE files. Good lesson!

    Similarly, with IMG/CCD files I need to point at the CCD file rather than the IMG file? I had ImgBurn write a second set of files for me, this time selecting IMG for file destination. It made IMG/CUE files instead. Little did I know I have to enable the CCD box in settings. Thanks @dbmin

    It's past midnight here, I will do some more testing in evening tomorrow.

    Not where ImgBurn is concerned, no.

    BIN/CUE is what ImgBurn started off supporting for CD images. I added support for CCD purely so people had the option of using VirtualCloneDrive instead of DAEMON Tools.

    Yes, you should always point the tools at the info files (CUE/CCD/MDS etc) rather than the data files (BIN/IMG/MDF). Otherwise, you're just giving them a load of data without any info on how to interpret it.

  2. How do you figure it's 2352 bytes per sector? I'm just curious. I have seen mentions of 2048 bytes per sector for CD discs on various forums and other places. For the disc I used in my example the reported size is 434108416 bytes and number of sectors is 211967. That comes out to 2048 bytes per sector. I'm no expert, but that would seem fitting for an ISO file? I know nothing about sessions, tracks and indexes. So in regard to these details it may be more fitting to use BIN/CUE files.

     

    That’s just what CDDA is. Check the MMC specs for optical drives and the various types of sectors used for what can be stored on a CD.

     

    Please just take it from me that the program is telling the truth. Don’t attempt to read an audio disc to a single file that you’ve given the ‘iso’ extension to. It won’t work... in anything.

     

    Bin/cue is very common for anything CD related. Bin/cue can be mounted in lots of virtual drive programs (the main one is / was Daemon Tools).

     

    Virtual CloneDrive is by the same people that made CloneCD, hence why it supports CCD/IMG instead, rather than Bin/cue.

     

    A virtual drive program that can fully process a bin/cue combo and emulate an optical drive/disc with it will be usable in the same way as if you had the original disc in a real optical drive.

  3. An ISO is dumb. It's a basic 2048 bytes per sector (purely 'user data') dump of the disc. It knows nothing of sessions, tracks, indexes etc and is always assumed to be single session, single track.

    Audio discs are complex. 2352 bytes per sector and you have the option of multiple tracks and multiple index points. That's why BIN/CUE is used. The CUE file is required for all of the extra info about the disc and the BIN is a 2352 bytes per sector dump of the disc. Without the CUE, your BIN file is useless - do not delete it.

    ImgBurn can also create a CCD file - which is very similar in function to the CUE file. VirtualCloneDrive doesn't actually (fully) support BIN/CUE, which is why ImgBurn can make CCD/IMG - VCDs native format.

     

  4. Sorry, no. ImgBurn can't help you with this.

    You've basically made a multisession disc.

    ImgBurn can send the commands to close tracks, sessions, discs etc.... but they're only useful for when those commands didn't work the first time around. 

    Your disc has been left unfinalised and with a new session open (that you can add data to) on purpose. The only way to finalise it is to add more data to it (again, can't be done with ImgBurn) and then ensure it's closed/finalised - do not let the software make yet another new session.

    It might just be easier to make a new disc. Use ImgBurn in build mode, add your MP3 files and burn.

  5. The program reads the sectors in chunks. When the drive returns an error, it drops down to reading them 1 at a time so it can pick out the bad one.
    What’s happened here is that the drive errored out when reading the chunk, but then succeeded to read them all when doing it 1 by 1.

    I would the disc has the potential to be unreliable. Maybe do a stand-alone verify on it and see if the drive fails to read it again in those same locations.

  6. Yes, unless your drive is broken, you should have no problem writing to them (subject to normal disc quality issues).

    Do not attempt to erase or format them before use. Take one out of the packet, fire up ImgBurn and try to burn that image again.

  7. Please try the following...

    Tools -> Settings -> 'Read' tab -> Page 2 -> Disc Layout Method -> Change 'Blu-ray' to 3-1-2.

    Then try using Read mode to read the disc again.

    ImgBurn will be in control of read then and not the OS, meaning you can perform more retries / skip bad sectors etc.

    Post the log when you hit a problem spot, have retried a few times and are about to give up (if it comes to that).

     

  8. It's probably just down to the media you're using.

    Although you say they're Verbatim discs, I'm afraid they're the wrong ones.... perhaps the 'value' range? Yours use the CMC MID/dye rather than the MCC/MKM one. Look for the 'Azo' label on Verbatim media and avoid their value range.

    If you get the decent stuff and the drive still errors out, you'll have to invest in a new drive.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.