Am I the only one who has encountered a problem with the CUERipper 2.1.4 'Test & Copy' mode? I'm unable to use it. Whenever I have the box checked I get an Exception error: "Gap Detection Failed." It does this with every disc I have tried, using two different drives. CUERipper works perfectly fine if I do not check the 'Test & Copy' box. I can't think of any logical reason why choosing 'Test & Copy' would cause gap detection to fail, but it does.
I can confirm this error.
crc.Combine length cannot be negative Parameter name: len2
I then tried the 4 original cue files individually and they all worked fine.
Is there any workaround for this issue?
Using a combined cue file for multi CD set can save a lot of time with regards to file naming and tag data for each track.
CUETools is working correctly as it was designed to process a single redbook CD rip at a time, not compilations containing multiple discs. Not a CUETools issue. The input is not correct.
So it looks like there is a threshold of combined audio length for a single cue file in CUETools 2.1.4; when this threshold is exceeded, CUETools will result in a negative combined CRC and the exception will be thrown.
Is there any workaround for this issue? Using a combined cue file for multi CD set can save a lot of time with regards to file naming and tag data for each track.
But a single cue file containing multiple FILE commands is still a valid CUE sheet.
Honestly, I combined the CUE files because then the output file names (%tracknumber% %artist% - %title%) are numbered correctly, rather than 4 files starting with "01", 4 files starting with "02", and so on. This also applies to the track number tag as well; I want 1/72, 2/72, etc. in stead of 4 files with 1/18, and so on.
I read someone else having the same error in this thread but there was further explanation.
I tried search for term "slider" and was trying to pin it to this forum only but results were not helpful so ...can someone please explain to me for CUETools the slider function in the last column of the main window? or point me to a tutorial where it is explaned? The app fires up with it set to 5 (the range is 0 to .
you only need to know the TOC in order to calculate the CDDB1 DISCID, and the TOC is always present in newer EAC logs.
Is it possible to also write the DISCID to the cue sheet? I couldn't find an option for this. And if it's not, could it be added in a future version? Or is there maybe a reason for not including it? Since I can't quite imagine this has been forgotten.
It's also being calculated using the TOC of the files being processed as it is the 3rd part of the AccurateRipID: xxxxxxxx-xxxxxxxx-DISCIDEDIT: To see the TOC used when processing files you can turn on the Create TOC option which will create a text file with the same filename as the output CUE and the extention .TOC
However, for discs with CD-Extra content, the incorrect ID would be calculated, right?
It can't handle sheets pointing to BINARY files, it seems. And of course, it doesn't process data tracks themselves. So it's safer to use the TOC from the EAC log (provided that the CRCs match (?)), since it has the TOC straight from the original disc. It does so already when verifying, I think.
You can always download the latest source code from project's SVN repository at SourceForge.Instructions for svn access can be found here.