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 1889326 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1475
I cannot for the life of me figure out how to save a log in cue tools.  What on earth am I doing wrong?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1476
I cannot for the life of me figure out how to save a log in cue tools.  What on earth am I doing wrong?

I assume you mean 'verify' log. Make sure 'Write AccurateRip log' is ticked and 'In source folder' if you want the log written to the folder where the files are being verified otherwise it is written to the 'Output:' folder shown under 'CUE Paths'. You can also add '.log' to the 'Name format:' if you wish.

pic link snagged from another post for visual reference only. Settings may differ.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1477
There's some strange behavior when there are several logs in folder.

Example.

Folder content:
Arturo  sandoval  &  WDR  Big  Band - Mambo Nights.cue
Arturo  sandoval  &  WDR  Big  Band - Mambo Nights.log
...
Mambo Nights_English.log

The first log ist in Russian, the second one - its English translation.

I start verify and I don't see any warning or dialog.

Now I rename the 1st log into Mambo Nights.log.
When I start verify now a dialog window appears allowing me to select the preferred log.

Do I make something wrong?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1478
If CUETools finds a log file that has exactly the same filename as a cuesheet, it uses it.
If not, it tries to find a log file with matching TOC. If there's no such log file, or there's more than one, it asks a user.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1479
Quote
If CUETools finds a log file that has exactly the same filename as a cuesheet, it uses it.


This is what I supposed. Thank you!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1480
Please forgive poor English. CUETools writes:
"AR: database access error" what happened?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1481
AccurateRip site seems to be having some trouble. Try again later.
CUETools 2.1.6


CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1483
Also, this:
A small % of people are getting routing issues to the new server [hosting AccurateRip and other Illustrate services] and there are a bunch of people who cannot reach it. It is a top priority correct this issue.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1484
The recent AR server trouble gave me the idea that it would be nice if rips with "database access error" would be automatically sorted in a "database access error" category within the local DB.

Edit: Just as "disk not present in database" should also be sorted in a "disk not present in database" category, I think I already asked for that one but I recall you so that you can fix both in a row. So far it wasn't very important as "disk not present in database" was what was remaining after you manually sorted all the rest, but with the database having access trouble 50% of time, "database access error" & "disk not present in database" get mixed in what remains after you sorted all the rest manually according to the local DB. It's still not a big issue, but ... I mean CT is supposed to be here to ease my life afterall !

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1485
I tried out CUETools.  (On a mac under parallels desktop, by the way;  I don't think I had any issues with running it on a virtual machine with mac formatted hard drives.)

I am using it only to verify files previously ripped with various tools before the days of AR.  The feature of being able to manually enter the first track pregap is superbly useful.

I have several questions and minor complaints: 


1)  It is not clear to me whether I first need to ask CT to make a cue sheet.
2)  Although I have checked somewhere to get verbose log files,  the output from a verification differs from time to time. Sometimes it is just one line, and only one track is reported as having been checked, although the progress report during the verification shows all tracks being checked. 
3)  When I do one operation, the entry in the input box changes from the folder I chose to some file in the folder. 
4)  I am not sure whether you are reporting results to AR.  You should not, I think, because  I am checking files previously ripped possibly by possibly inferior ripping programs and sometimes I just guess the first track pregap.

Thanks for this very nice program.


CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1486
1) No, CT will use splitpoints between your files to create a virtual dummy TOC.
2) ?
3) That's recursive scanning I guess. It seems normal.
4) No, nothing is submitted to AR on verification. IIRC maybe something is submitted to CTDB but only if AR(2) [Not 100% sure here].

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1487
2)  Although I have checked somewhere to get verbose log files,  the output from a verification differs from time to time. Sometimes it is just one line, and only one track is reported as having been checked, although the progress report during the verification shows all tracks being checked.

It's probably showing a batch log because you selected a folder. Batch mode is meant to verify lots of files in one go, so it only prints one line per album. You can then find the album in Local DB to see the verbose log, or just make sure you select a cue sheet (or an audio file, if there is none), not the folder.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1488
So I guess the bottom line is that I should ask CT to make a cue sheet, and then choose the cue sheet as input for the verification step. Is that correct?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1489
2)  Although I have checked somewhere to get verbose log files,  the output from a verification differs from time to time. Sometimes it is just one line, and only one track is reported as having been checked, although the progress report during the verification shows all tracks being checked.

It's probably showing a batch log because you selected a folder. Batch mode is meant to verify lots of files in one go, so it only prints one line per album. You can then find the album in Local DB to see the verbose log, or just make sure you select a cue sheet (or an audio file, if there is none), not the folder.



How do I access/view  the local DB?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1490
Quote
How do I access/view the local DB?


CUE Paths (Main Window)/Input/Folder Browser (Bottom Left)

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1491
Hi.

I've got a feature request.

When being asked whether to submit CTDB data, there's a small tick box that wants me to remember my choise. Now the problem is that it doesn't remember its state.  Basically I want to be asked everytime without having to untick that option, so if I untick it, the next album I verify I want the dialog box to have this option unticked already, if you know what I mean...


CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1492
Hi.

I've got a feature request.

When being asked whether to submit CTDB data, there's a small tick box that wants me to remember my choise. Now the problem is that it doesn't remember its state.  Basically I want to be asked everytime without having to untick that option, so if I untick it, the next album I verify I want the dialog box to have this option unticked already, if you know what I mean...



Seconded. It is quite annoying having to uncheck this box every time.

I'm also having a problem with CUETools getting stuck on a pregap. If I test a cue without a pregap then add the pregap line to the cue, CUETools returns results for no pregap. Same thing in reverse. If I test with a pregap then without, the results are still for the pregap. I tried deleting the entry from the local DB and restarting CUETools. I finally deleted the local DB and it forgot the previous pregap.


korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1493
Hello,

Another neeb to Cuetools 2.1.2A.  A few simple questions and a question about a log <groan>.

First, between 2002 and 2005 I ripped about 3500 CDs using EAC, these were then encoded to APEs.  About 1200 of these were verified by ripping them on 2 different types of drives and then comparing the results.  Since late 2005 I have basically been listening to them.  For a couple of reasons, I have recently decided to transcode them to FLAC. Fortunately, I found Cuetools which allows me to do so much more.  Unfortunately I am getting many more "not accurate" results than I had expected.  Some I can explain (a leadout issue on an early drive) but others I can't.

One issue is I am in Australia and most modern music CDs sold here were also (in various combinations) remastered, mastered, rearranged, had tracks changed etc, and pressed often (in the 80s and early90s) from either track or whole disc based digital master tapes (Sony PCM16xx U-Matic).  This often results in accuraterip returning a low confidence for popular titles, 0 confidence for the most less popular tittles, or no database entry at all.

I really don't know much about accuraterip as it was in its infancy when I was ripping. I am currently muddling my way through Cuetools and the resultant log files, I suppose it will all eventually become clear.  Now to the questions:
1. is there a manual for Cuetools?
2. is there a guide to interpreting the logs?
3. is there a good explanation of how the accuraterip database verifies the tracks ( it is track based, isn't it????)
4. with various artists albums there appear to be 2 main types of cue sheet:

Code: [Select]
REM ACCURATERIPID 00304806-0287f028-15121c12
PERFORMER "Various"
TITLE "The Best Of The East Coast Blues And Roots Music Festival (CD 2)"
REM DATE 2000
REM GENRE "Blues"
FILE "Various Artists - The Best Of The East Coast Blues And Roots Music Festival (Disc 2 of 2).flac" WAVE
  TRACK 01 AUDIO
    TITLE "G Love & Special Sauce / Blues Music"
    PERFORMER "Various"
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    TITLE "Tony Joe White / The Delta Singer"
    PERFORMER "Various"
    INDEX 01 04:16:59
  TRACK 03 AUDIO
    TITLE "Charlie Musselwhite / The Big Boat"
    PERFORMER "Various"
    INDEX 01 08:51:42

and this

Code: [Select]
REM ACCURATERIPID 002391cc-0180ddea-b910f40e
CATALOG 093624686729
PERFORMER "Various Artists"
TITLE "City of Angels"
REM DATE 1998
REM DISCNUMBER 1
REM TOTALDISCS 1
FILE "Various Artists - City Of Angels Movie Soundtrack.flac" WAVE
  TRACK 01 AUDIO
    TITLE "If God Will Send His Angels"
    PERFORMER "U2"
    INDEX 00 00:00:00
    INDEX 01 00:00:32
  TRACK 02 AUDIO
    TITLE "Uninvited"
    PERFORMER "Alanis Morissette"
    INDEX 00 04:32:13
    INDEX 01 04:33:60
  TRACK 03 AUDIO
    TITLE "Red House"
    PERFORMER "Jimi Hendrix"
    INDEX 00 09:08:70
    INDEX 01 09:10:45
  TRACK 04 AUDIO
    TITLE "Feelin' Love"
    PERFORMER "Paula Cole"
    INDEX 01 13:01:02
  TRACK 05 AUDIO
    TITLE "Mama, You Got a Daughter"
    PERFORMER "John Lee Hooker"
    INDEX 01 18:38:45
  TRACK 06 AUDIO

Which of these is considered the most "acceptable" (if that has any meaning)?  I noticed that different  databases appear to favour different schemes.


Also, I do not know what to make of this log

Code: [Select]
[CUETools log; Date: 5/08/2011 12:34:44 AM; Version: 2.1.2a]
[CTDB TOCID: 6eSv.MMZM7l_9J3YkT4EeahUW.c-] disk not present in database.
[AccurateRip ID: 00304806-0287f028-15121c12] found.
Track  [ CRC    ] Status
 01    [38357a6a] (0/0) No match but offset
 02    [dd866980] (0/0) No match but offset
 03    [e7b3b15e] (0/0) No match but offset
 04    [90c75012] (0/0) No match but offset
 05    [50ddae6d] (0/0) No match but offset
 06    [01d603a5] (0/0) No match but offset
 07    [b90c18f9] (0/0) No match but offset
 08    [e43da2fe] (0/0) No match but offset
 09    [2bfa9f4a] (0/0) No match but offset
 10    [79be0aa4] (0/0) No match but offset
 11    [d95f2e46] (0/0) No match but offset
 12    [ba182d68] (0/0) No match but offset
 13    [0018ce84] (0/0) No match but offset
 14    [66431538] (0/0) No match but offset
 15    [fb6cc9a7] (0/0) No match but offset
 16    [45dd7b4a] (0/0) No match but offset
 17    [fbda9e6d] (0/0) No match but offset
 18    [b8fcc4de] (0/0) No match but offset

Track Peak [ CRC32  ] [W/O NULL]
 --  100.0 [5DA62C09] [1D6E8764]         
 01  98.4 [5AA0BC10] [74DD99F5]         
 02  99.9 [7BD092FD] [E5915363]         
 03  100.0 [51B7D756] [8ED611E2]         
 04  100.0 [4E771224] [0716E7D8]         
 05  89.0 [F889D9B9] [5D83586C]         
 06  99.8 [A9E24353] [2BE94567]         
 07  100.0 [B49874A7] [7AD02C4C]         
 08  94.4 [FB69F64C] [C518C405]         
 09  89.0 [0F7F529B] [52A79887]         
 10  100.0 [99AEBEC5] [0DEAC2A1]         
 11  93.9 [5208A259] [4512CAB0]         
 12  97.9 [644A77A5] [41256702]         
 13  78.4 [45E4DD4F] [26EAC24E]         
 14  100.0 [267C0718] [E40121FA]         
 15  100.0 [7CAB10AB] [3863F8DD]         
 16  98.4 [5FD54815] [DDDAA824]         
 17  99.9 [1866FB99] [0ACC4021]         
 18  99.9 [F40C451F] [FD15E293]         

While this disc was being verified the acurraterip symbol was in the status bar with a 0 beside it.

I could understand it if there were some tracks with 0/0 - but all tracks? Am I just being dense?

Thanks,
Bob

BTW. Sorry about the rambling.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1494
Hi fellas, another newbie here.  I've mostly been lurking but figured I'd speak up because I have similar questions to robbo1802 above.  (If one of you could point me to a Cuetools guide/manual it would be much appreciated.)

I'm using Cuetools to split up large flac files into individual tracks and I don't understand the logs.

For example:

Code: [Select]
[CUETools log; Date: 5/11/2011 6:56:30 PM; Version: 2.1.1]
[AccurateRip ID: 000c9374-00537836-79096b08] found.
Track  [ CRC    ] Status
 01    [054fb569] (0/9) No match
 02    [12b7456a] (0/9) No match
 03    [ef75c86a] (0/9) No match
 04    [354bf4f9] (0/8) No match
 05    [eaeed1cf] (0/9) No match
 06    [6877ed3b] (0/9) No match
 07    [9bd777da] (0/9) No match
 08    [e0b55d58] (0/9) No match
Offsetted by -1855:
 01    [ef4ad646] (2/9) Accurately ripped
 02    [ad689173] (2/9) Accurately ripped
 03    [da3a9fe5] (2/9) Accurately ripped
 04    [506a1091] (0/8) No match but offset
 05    [d3884347] (2/9) Accurately ripped
 06    [fc8126d0] (2/9) Accurately ripped
 07    [6eeb6008] (2/9) Accurately ripped
 08    [56d00b11] (2/9) Accurately ripped
Offsetted by 12:
 01    [64f41ac5] (7/9) Accurately ripped
 02    [4968ed2a] (7/9) Accurately ripped
 03    [2518e7ca] (7/9) Accurately ripped
 04    [d157e819] (0/8) No match but offset
 05    [6a99eb6f] (7/9) Accurately ripped
 06    [df060337] (7/9) Accurately ripped
 07    [f89e8e17] (7/9) Accurately ripped
 08    [3e5e201b] (7/9) Accurately ripped

Track Peak [ CRC32  ] [W/O NULL]
 --  99.7 [52994A3F] [30AABD7D]         
 01  99.5 [30E9376F] [C7F3061C]         
 02  99.5 [ADFEC796] [E5CE296A]         
 03  99.5 [49B24626] [C5BD0089]         
 04  99.5 [8E01E290] [5274FA92]         
 05  99.7 [7BB60CC9] [D1F48EBC]         
 06  99.5 [4790503A] [B4389095]         
 07  98.9 [6A24A9F1] [77A65087]         
 08  98.4 [4A700127] [53558F7F]         

Does this log mean that the current offset is incorrect, and I should adjust it to 12 (or choose "fix offset")?

Sorry for being such a noob.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1495
giant walking robot:
I haven't read robbo1802's post, but in your case, it's either:
- the offset was not fixed while ripping & it's not accurate
OR
- the pressing with your offset is not yet in database & it's maybe accurate.

Anyway "fixing" offset alone will not fix track 04, only repairing with CTDB can maybe do that if errors are detected.
By experience I would say that the rip is suspicious & that case 1 is more & more likely as time goes by.
Furthermore, even if your pressing suddenly appear in the AR database, it can very well happen that track 04 will still be not accurate.
It would mean that pressings with offset 0, -1855, 12 are nearly identical except for the offset.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1496
robbo1802:
1 & 2 - As sources of information there is this topic, the HA wiki entry & CT official website. (Sometimes Spoon's own AR forum which also helps for AR development & maintenance, but not on CT or logs). Yes learning about CT, AR & CTDB is painfull, but it worths the pain IMHO.
3 - Yes AR is track based, all information about how it works & why, is buried somewhere in this topic.
4 - CT doesn't really care about the cuesheet style. It cares about the TOC, the only thing that matter is that the splitpoints between tracks are at the same place. If the TOC (with some special info like pregap & extra info like datatrack length) is the same it will have the same ID & check against the same CRCs.

Finally rips with AR(0) are rips for which there was at some point an entry in AR which was withdrawn for some reason. Maybe purged virtual drives results or pending conflicting CRCs waiting for a confirmation.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1497
Hi sauvage78,

Thanks for that help.  I must admit I was hoping for a nice manual, trawling through monster threads is not my favourite pastime.


4 - CT doesn't really care about the cuesheet style. It cares about the TOC, the only thing that matter is that the splitpoints between tracks are at the same place. If the TOC (with some special info like pregap & extra info like datatrack length) is the same it will have the same ID & check against the same CRCs.


I wasn't concerned about the how the different cuesheet styles affect CTDB and AR (and as you have explained, they don't), I was more looking to see if one style was considered better than the other.  I would prefer to have all the 'various artist' cue sheets in a single style.

At the moment I am grinding through the task of transcoding all the apes and embedding the cue sheets in the FLAC files.  I am trying to understand all the various combinations of what CT does in the different directory modes and actions.  I am using batch to convert the files and it appears that in this mode CT will check against the AR DB but NOT the CTDB for verification - I find this a bit puzzling.

When I have finished transcoding I will have to do a study of the results to see how well I did with EAC.  Unfortunately, I think there may be more questions than answers, especially when it comes to compilations (both various artists and single artists) as these can be a patchwork of different tracks.

I will also have a look at further editing and addition to the tags on the files and I am wondering what apps are considered best for this.

Thanks again,
Bob

 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1498
1. is there a manual for Cuetools?
2. is there a guide to interpreting the logs?

CUETools wiki is open for everyone to contribute. I'm still hoping somebody will write guides there.

3. is there a good explanation of how the accuraterip database verifies the tracks ( it is track based, isn't it????)

It is track based and it's quite simple. It keeps checksums for tracks ripped by different people, and if your track checksum matches the one in database with high confidence level (confidence level is just the number of times such checksum was submitted), you can hope your rip is correct.

4. with various artists albums there appear to be 2 main types of cue sheet:

It's better of course when track author is stored in PERFORMER tag, because this way you can correctly tag your FLACs and you will be able for example to find all tracks by a certain artist in your collection.
The artist / title notation probably only exists because freedb database couldn't handle track artists any other way.

Also, I do not know what to make of this log
While this disc was being verified the acurraterip symbol was in the status bar with a 0 beside it.

There is no data for this CD in AR database. As sauvage78 pointed out, this CD probably was submitted to AR, but later deleted.

I'm using Cuetools to split up large flac files into individual tracks and I don't understand the logs.
Offsetted by 12:
03    [2518e7ca] (7/9) Accurately ripped
04    [d157e819] (0/8) No match but offset
Does this log mean that the current offset is incorrect, and I should adjust it to 12 (or choose "fix offset")?

I wouldn't adjust offset unless you want to create a bit-perfect copy of this CD on a CD-R.
Even if you are sure that offset is wrong (it could be just a different pressing) offset correction doesn't change the actual sound, so what's the point.
CD manufacturers don't worry about offsets, there are dozens of different versions for any popular CD which differ only in offset, because they were produced on different factories.
If CD manufacturers don't care about it, why should you?

This rip also seems to contain an error on track 4, but that has nothing to do with offsets.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1499
Is there any way to use CueTools to encode to Wavpack Hybrid (Lossy+Correction)?

I tried to set up a 'custom' encoder command line (wavpack.exe / -b320 -hx -m -c - %O) but nothing happens: the progress bar is stuck at 0% and the wavpack process has to be killed...