Jump to content

Recommended Posts

Posted (edited)

Hi everybody!

 

I am new to this forum, so please excuse me in case of errors.

 

I recently created an image of an audio CD. It was an original CD, and I was trying to make a private, personal backup. Everything worked fine, ImgBurn created a .bin and a .cue file. If I try to mount the image with DAEMON Tools, I am told there is a syntax error. It took me quite a while to figure out that there was something wrong with the ISRC. By the way, here is the CUE file:

FILE "Gathering, The - How to measure a planet [Disc 1].bin" BINARY
 TRACK 01 AUDIO
   ISRC <cIG29802681
   INDEX 01 00:00:00
 TRACK 02 AUDIO
   ISRC <cIG29802682
   INDEX 00 05:04:12
   INDEX 01 05:04:55
 TRACK 03 AUDIO
   ISRC <cIG29802683
   INDEX 00 11:21:32
   INDEX 01 11:24:42
 TRACK 04 AUDIO
   ISRC <cIG29802684
   INDEX 00 17:44:12
   INDEX 01 17:46:55
 TRACK 05 AUDIO
   ISRC <cIG29802685
   INDEX 01 21:19:02
 TRACK 06 AUDIO
   ISRC <cIG29802686
   INDEX 01 27:20:65
 TRACK 07 AUDIO
   ISRC <cIG29802687
   INDEX 00 33:43:42
   INDEX 01 33:46:62
 TRACK 08 AUDIO
   ISRC <cIG29802688
   INDEX 00 38:47:40
   INDEX 01 38:47:62
 TRACK 09 AUDIO
   ISRC <cIG29802689
   INDEX 00 44:42:25
   INDEX 01 44:43:57

 

Obviously this ISRC is invalid. I see 3 possibilities what went wrong:

 

1) The ISRC on the original CD is wrong. Very unlikely, unless it is some funky kind of copyprotection. If so, the record company is a bunch of [insert very rude word here]!

 

2) My CD drive extracted the ISRC wrong. It is a Samsung DVD writer. Don't know the exact model ATM.

 

3) ImgBurn did something wrong.

 

In case 3 it would be a ImgBurn bug. I can't imagine that nobody ever encountered this. I have a few other images that showed the same problem, but many others that mount perfectly well. I will check if those have correct ISRCs or none at all.

In cases 1 and 2 there is obviously nothing that can be done. In this case it would be nice if I could deactivate ISRC readout by ImgBurn in order to create valid CUE files. Or is this illegal due to copyright issues?

It certainly is not nice to delete the ISRCs manually from every CUE sheet.

 

Someone got an idea what to do?

 

regards, Mike

 

 

Ah, sorry for not including a log. :&#39;( I don't have it with me ATM. But for the above problem it should not be necessary. :whistling:

Edited by mike42
Posted (edited)

LiteOn and Samsung drives are buggy like that, use a different drive.

Well, you will maybe understand that I won't go to the store and pick up a new drive, "just because of that issue" :ermm: . It's not that I desperately need the ISRCs read out correctly. I just want to mount the CUEs without having to correct them manually.

I have actually implemented code ready for 2.5.1.0 to work around the issue.

Does that workaround involve a better read out or does it just ignore/discard the faulty ISRC?

 

PS: And thanks for the quick reply!

Edited by mike42
Posted

It never hurts to have a few drives :)

 

You can get them for £20 here (latest models) so it's almost as cheap as buying a spindle of decent discs (cheaper in some cases).

 

2.5.1.0 contains an alternative method of reading it - where I do the work (reading all the subchannel data and extracting the ISRC that way) rather than just asking the drive to return the ISRC.

Posted

2.5.1.0 contains an alternative method of reading it - where I do the work (reading all the subchannel data and extracting the ISRC that way) rather than just asking the drive to return the ISRC.

Great! When do you plan to release 2.5.1.0? :w00t:

How about still including an option to omit the ISRC? Just in case some crapy drives still refuse to return valid information.

 

I can't understand, how a DVD drive can be cheesy like that. Don't those freaks test their hardware before selling it?

×
×
  • Create New...

Important Information

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