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 versions 1.9.5 through 2.1.6 (Read 1906769 times) previous topic - next topic
0 Members and 11 Guests are viewing this topic.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #350 –
I've been messing around with 2.0.1 and I like it.  What I would like to see is a 'Correct Filenames' option that will write a new file, appending the original file name.  So if I have a folder full of FLAC files, I would keep the existing WAV cue intact.  This may have already been requested.  Sorry if that is the case.

I also noticed that the "Verify AR + CRC" option only works with EAC v0.99 logs.  It would be nice for it to work with 0.95 logs also.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #351 –
Quote from: RolloTomasi on
I also noticed that the "Verify AR + CRC" option only works with EAC v0.99 logs.  It would be nice for it to work with 0.95 logs also.

My mistake.  Verifying CRCs against the log file does not work in BATCH mode.  While in batch mode, it only REPORTS the CRCs.  Both versions of EAC appear to be supported.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #352 –
WOW, how did I miss this thread since I first tried AR in CT? Seems all my accuraterip-dreams has come true

I have a problem (with 2.0) though: I input track-separated flac-files and want to encode offset-corrected albums (still as track-separated) to a specified dir (using custom format). However, it seem not to recognize the artist and album as it creates this dir for everything:
"Unknown Artist - Unknown Title"
Can't wait for a HD-AAC encoder :P

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #353 –
Quote from: atzaus on
I joined to ask what offset X, files accurately ripped means? Should my files be offset by 6 bits and then the will be accurately ripped? Is there an option to detect files as they are without offsetting them? Also can you add an option to generate a better formatted log for the folder so we can easily found out which folders are AR.

Your files are accurately ripped if they match at least one offset (pressing).
You might want to offset them by X samples before burning a CD-R, if you want an exact copy of an original CD.
If you burn with software which is not aware of drive offsets, you should offset your music by X + YourDriveWriteOffset.
What exactly would you call a better formatted log? Please, give an example.

Quote from: RolloTomasi on
Verifying CRCs against the log file does not work in BATCH mode.  While in batch mode, it only REPORTS the CRCs.

I'm still thinking if/how should the program be allowed to autolocate log files.
Currently in single mode when the program cannot find the .log file with same name as a .cue sheet, it asks a user to select a matching log file.
In batch mode it cannot ask a user. For now, try renaming your log files.

Thanks everyone for feedback, as usual i will try to fullfill most of the requests when i can.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #354 –
Quote from: odyssey on
I have a problem (with 2.0) though: I input track-separated flac-files and want to encode offset-corrected albums (still as track-separated) to a specified dir (using custom format). However, it seem not to recognize the artist and album as it creates this dir for everything:
"Unknown Artist - Unknown Title"


Make sure "Fill up missing CUE data from tags" option is turned on.
Try also enabling 'Freedb lookup'.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #355 –
Quote from: Gregory S. Chudov on
I'm still thinking if/how should the program be allowed to autolocate log files.
Currently in single mode when the program cannot find the .log file with same name as a .cue sheet, it asks a user to select a matching log file.
In batch mode it cannot ask a user. For now, try renaming your log files.

Hm, you could let it scan every file with the log extension for typical strings of EAC logs. That's how you can get the (list of all) log file(s) automatically without letting the user choose. This should work good enough for directories with only one .log file.

At the moment when there are more than one audio file and/or log files, CUE Tools prompts the user and he has to check the log by looking at it in the preview. While this works, too, it can be automated I think: CUETools should read all the CRCs of all the logs regardless, and compare them to the ones it will calculate later. That way at least a positive match can be confirmed, and the correct log can be linked to the correct audio file without the need of user interaction. Quite similar to how AR works actually. And if the CRCs do not match (for 2 CDs, there would be 4 CRCs, two from the logs and two calculated by CUETools), there can still be a prompt so that the user may choose which of the EAC logs is the correct one for each audio file.

In the end this should make the log selection prompt a much rarer sight.

Yet another trick would be to utilize the alphanumeric sort order of the log files, in case log and audio file basenames do not match. That should work in many cases for multi-CD albums at least. So the first audio file in the file list of the directory and the first log file probably are related to another, even if both logs come before both audio files or vice versa:

CDImage1.ape
CDImage2.ape
Unknown Title (CD1).log
Unknown Title (CD1).log

But this may fail, so it's not safe to to turn it on by default. Maybe it's a choice for batch processing if the user wants it to.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #356 –
Quote from: Gregory S. Chudov on
Currently in single mode when the program cannot find the .log file with same name as a .cue sheet, it asks a user to select a matching log file.
In batch mode it cannot ask a user. For now, try renaming your log files.


In regards to the names matching, I figured that out since I posted.  For the most part, there will only be one log per folder, and using the EAC defaults, the log file name does NOT match the cue file name.  I suggest letting batch mode use the existing non-matching log if only one log exists, and skipping the log check if more than one exists.  Better than nothing.

Case in point.  I tested an album in batch mode, log file name did not match the cue file name.  The rip was individual tracks, gaps appended.  The Cue gave me an AR match, but the files did not.  Rather, they reported "Disk not present in database."  However, when I tested the same files in single mode, and selected the LOG file, an AR match was reported.  Any idea what would cause this discrepancy in results?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #357 –
Some CDs have nonstandard pregap (pause before the first track), some have data tracks.
If this information is missing, CUETools cannot calculate the correct disc id.
This information can be found in a .cue sheet or an EAC .log file.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #358 –
The CD in question DOES have a non-standard [greater than 2 seconds] 1st track pregap.  Checking the same file with TripleFlac reports a match. 

But this DOES explain the discrepancy in results clearly.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #360 –
What is this screenshot intended to prove?
However it works fine on my German system.
audiophile // flac & wavpack, mostly // using too many audio players

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #361 –
that cutools couldn't give the files russian names.
 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #362 –
Turn off 'Remove special characters' option.
If you want it to support even more languages, turn off 'Force ANSI filenames' also.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #363 –
awesome program, just wanted to pop into the thread and say thanks for all the hard work.
finally decided to download and try CUETools.  so far i've just been using it this morning to Verify AR + CRC's.  from the looks of it, plenty of potential other uses as well.
v2.0.1 x64 is working great for me on Vista Ultimate x64.

thanks again.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #364 –
Quote from: Gregory S. Chudov on
Turn off 'Remove special characters' option.
If you want it to support even more languages, turn off 'Force ANSI filenames' also.
thanks ill try it

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #365 –
im unhappy with the l8est unstable/experimental versions browsing behavior. cuetools is now using its own browser instead of windows' that is actually very slow for people with huge harddrives and a lot on them. my comp is pretty fast too. also i dont get an option to choose between my local .cue vs freedb and musicbrainz anymore.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #366 –
Use of cuetools' own browser is optional. You can still drag'n'drop files directly to the input box. In the next version it will be possible to hide the browser altogether. Also i'm pretty surprised that it's slow for you, because for me it works even faster than windows vista's explorer, and i have a 1TB+ archive.

Also it's strange that freedb doesn't work for you. Are you sure 'Freedb lookup' option in the main window is set to 'Always'? Or maybe you selected a folder as input, thus activating batch mode?

I realize that constant changes to the program are confusing, but i want this program to be more friendly to new users. I promise i'll make sure it doesn't loose any of it's features in this attempt to simplify the ui.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #367 –
Hi there, just want to say thanks for the tool. Decided to convert all my Flac + cue images into separate files +cue (Gaps Appended). All working fine, converting back to single wav image with cue seems to be going all well.

Have a small request for v2 with the new gui, it's not possible to view hidden folders in the file tree. Why would anyone need that?
Well i run cuetools through Parallels on the Mac. My drive is partition into 3 parts, one for each OS and a large storage drive where all the music is kept. Unfortunately on the MAC the file system lists additional partitions within a hidden /Volume/ and this is not accessible to CueTools v2, v 1.9.x works fine.
Now i can understand that viewing hidden folders might actually impact on the File Tree view of v2, but if it doesn't and if it is not time consuming to enable then it would be appreciated.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #368 –
I have a request: When I fix offset only if 100% tracks are confidence 2, Cuetools fix the offset according to the lowest offset difference. Would it be possible to have an option in order to have it match the offset with the highest confidence level instead of the closer one ... this doesn't matter for quality indeed but it is better IMHO than fixing to the closer offset. Why ? Because when there is an accuraterip purge then the rip with the closer offset might be deleted if it is not popular & then you end up having fixed your offset against a rip that is not in the database anymore ... targetting the offset with the highest overall accurate result for all tracks would avoid such un-wanted behavior. Thks.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #369 –
Quote from: sauvage78 on
Because when there is an accuraterip purge then the rip with the closer offset might be deleted if it is not popular

Are AccurateRip submissions really deleted just because they're not popular?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #370 –
No accurate rip records are deleted due to popularity.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #371 –
Check out the new build.

Quote from: joyus on
Have a small request for v2 with the new gui, it's not possible to view hidden folders in the file tree.

Forgot to do it in 2.0.2, i hope i won't forget it next time.

Quote from: sauvage78 on
Would it be possible to have an option in order to have it match the offset with the highest confidence level instead of the closer one ...

Wierd request imho, but it was easy to add such an option, so i did it.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #372 –
I just want to say thank you again for the latest version, Gregory! It's truly awesome.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #373 –
Aw, a new version without intermediate builds on SVN... gonna translate some new stuff, brb.
audiophile // flac & wavpack, mostly // using too many audio players

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #374 –
Well as it seems nobody understund what I meant, maybe once again my english wasn't very good.

What I meant is that I like fixing the offset because it creates shorter logs (that has nothing to do with quality or safety), so before the recent virtual drive result purge I have fixed my offsets on my collection, just to get rid of some useless lines in my accuraterip logs but it happened that, due to the default system, I fixed my rips with offset/pressing that were close but with low confidence (say offset +1 confidence 2) instead of fixing my rips with a higher confidence but a bigger offset (say offset +1000 confidence 100). Now with the virtual drive purge the pressing with confidence 2 & offset +1  has disapeared ... so I have fixed my rips for nothing, if you have the option to match the offset with the higher confidence then you get rid of this annoyance ... or at least you highly reduce the probability. Not very usefull, but still nicer IMHO.

Thks for the new version I will try it right now