Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: CUETools 2.1.4 bugged (Read 3391 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CUETools 2.1.4 bugged

I ripped a CD to tracks using Exact Audio Copy 1.0 Beta 3.

Three of the tracks were not accurately ripped. My drive did show C2 correction on these three tracks.

I loaded CUETools 2.1.4. I used the "repair" script and selected "wav" for the encode format. After verifying, it prompts me to "Select the Best Match." I get two options, one with no errors, and one with the reported errors from Exact Audio Copy. If I select the one with no errors, CUETools does nothing. If I select the one with errors, CUETools goes to "writing tracks," then reports that it has corrected the errors, and gives a clean AccurateRIP report.

HOWEVER, when I use CUETools to run a verify on the tracks that it just wrote, and said were corrected, it returns that the tracks STILL CONTAIN the errors. I checked the checksums on the written WAV files, and indeed they do match the original WAV files (the ones with the errors).

I tried the exact same steps using the previous version of CUETools - version 2.1.2a.

This version now works. When I verify the files CUETools says it copied and corrected, they return that they are now indeed accurately ripped. The checksums now differ. I also get a .accurip file in the output directory; I didn't get that before.

So it appears that version 2.1.4 is bugged! That's a pretty big bug IMHO.

(I made sure the local CUETools database in ...\user\Application Data\CUETools was deleted before running each of the above.)

CUETools 2.1.4 bugged

Reply #1
First, there's a [a href='index.php?showtopic=66233']development thread[/a] that the current developer of the program reads regularly. Problems should be reported there. This issue was already reported though by me.
Quote
If I select the one with no errors, CUETools does nothing.
That's because there's nothing to do.
Quote
If I select the one with errors, CUETools goes to "writing tracks," then reports that it has corrected the errors, and gives a clean AccurateRIP report.
This is a projected report (no verification is done during the repair script).
Quote
HOWEVER, when I use CUETools to run a verify on the tracks that it just wrote, and said were corrected, it returns that the tracks STILL CONTAIN the errors. I checked the checksums on the written WAV files, and indeed they do match the original WAV files (the ones with the errors).
This was a known issue which I reported [a href='index.php?act=findpost&pid=801200']here[/a]. The patched version was uploaded to the site with the same version number as stated [a href='index.php?act=findpost&pid=801938']here[/a].

Are you sure you were using the fixed 2.1.4? You would have needed to download it after Jul 12 2012. I just tested wav to wav repair and it worked as expected using the fixed version. Verification confirms changes were made.
korth


CUETools 2.1.4 bugged

Reply #3
Downloaded when? Recently? The patched version replaced the original at the same link Jul 12 2012 with no change in version number.

[EDIT] Just confirmed the link is the latest patched version. Two more discs repaired wav to wav as expected and differences verified.
korth

CUETools 2.1.4 bugged

Reply #4
Downloaded it today.

I tried it again and it still fails to actually repair the wavs. Version 2.1.2a works fine.

Not sure why 2.1.4 works for you and not for me.

CUETools 2.1.4 bugged

Reply #5
Very dumb question, but: you have not managed to change the target folder for the files, so that you are overwriting to somewhere else rather than ... ? (Yeah, I've done that.)

For the record, the version bump did the trick for me. I have repaired 20 rips with it.
Last two months' worth of foobar2000.org ad revenue has been donated to support war refugees from Ukraine: https://www.foobar2000.org/

CUETools 2.1.4 bugged

Reply #6
Don't know why either. I'll point the developer to this thread. Might take a day or two and he may not reply to this thread but he'll look into it. Could you post the CUETools log?
korth

CUETools 2.1.4 bugged

Reply #7
I should have just bumped the version for that bug fix to avoid so much confusion. Anyway, if you are entirely sure that a clean experiment (with freshly downloaded, freshly unpacked CUETools.exe modified 11 July 2012) produces wav files that are no different from the originals, then i will need more details (logs, source file format, etc).
CUETools 2.1.6

CUETools 2.1.4 bugged

Reply #8
Well, I redownloaded 2.1.4, deleted the user folder, ran through it again, and now it works.

It may be, that I may have unknowningly done or clicked something in the program that triggered the bug. Or, the download may have been the version from before 7/2012, somehow (we won't know now since I deleted the download). Or, most likely, it's just user error.

 

CUETools 2.1.4 bugged

Reply #9
Or, the download may have been the version from before 7/2012, somehow (we won't know now since I deleted the download)


Or you might not have? Downladed CUETools_2.1.4.rar and then re-downloaded, it being named CUETools_2.1.4(1).rar, then after downloaded the latter, you just went ahead and extracted the former? ;-)
Last two months' worth of foobar2000.org ad revenue has been donated to support war refugees from Ukraine: https://www.foobar2000.org/