A few thoughts:
In some case "disk not present in database." is repeated twice without real use.
Worst, it is confusing as the second time is repeated in the middle of CTDB information while it is an AR information. IMHO, this is not really clear. As no CRC is displayed because the rip is not in the AR database, "disk not present in database." is still displayed next to CTDB information without pointing out that it is not belonging to the CTDB informations. At first I was confused personnaly .
Exemple:
[Verification date: 06/05/2010 04:54:04]
[AccurateRip ID: 00100325-008d29b0-a809970c] disk not present in database.
CD-Extra data track length 02:37:15 - 02:38:14.
[CTDB TOCID: iV0EDyEDBUTK5m1qP1duC.QkPfY-] found.
[ CTDBID ] Status
[b90da38a] (39/39) , Accurately ripped
Disk not present in database.
Track Peak [ CRC32 ] [W/O NULL]
-- 97,8 [D7CE63F7] [D53620F4]
01 84,0 [B6E48353] [51481335]
02 90,8 [6AF45844] [79640A06]
03 97,8 [60FC355C] [9D941685]
04 87,6 [A97E2DBC] [B9DD6683]
05 89,3 [E491D56E] [62468787]
06 91,6 [B9CA1D1C] [1AA62050]
07 89,8 [454B37CA] [EFACBDA6]
08 95,0 [2948647D] [E0A78584]
09 87,6 [86E97FED] [9A1E4147]
10 88,5 [21754A50] [E2C6BFEC]
11 89,6 [7489D97C] [C619A96D]
Even if not perfect, it would have been clearer if
"Track [ CRC ] Status" would have split CTDB & AR informations zone.
Example:
[Verification date: 06/05/2010 04:54:04]
[AccurateRip ID: 00100325-008d29b0-a809970c] disk not present in database.
CD-Extra data track length 02:37:15 - 02:38:14.
[CTDB TOCID: iV0EDyEDBUTK5m1qP1duC.QkPfY-] found.
[ CTDBID ] Status
[b90da38a] (39/39) , Accurately ripped
Track [ CRC ] Status
Disk not present in database.
But IMHO the best way to deal with this is to completely remove the second "Disk not present in database." which is now useless. All this is unexpected consequences of the introduction of CTDB informations in the middle of AR informations. That's why I would prefer to have it in the end with the possibility of splitting the log in two logs (.accurip .ctdb).
The only drawback of having the CTDB information at the end is that with CD with plenty of pressings it forces you to look at the bottom. If this is really an issue then display the CTDB information in absolute first place just after the first line (Date) because IMHO the actual way of splitting the AR information in two to artifially put the CTDB checksum next to the AR checksums is only making things harder to read IMHO. Specially as the CTDB database is actually very small.
Also I noticed an unoptimised behavior of Cuetools:
When you "Verify"+"only if found", cuetools doesn't display the possible data track length if one if found in the CTDB database, this is sub-obtimal because the reason why the CD is not found in the AR database might be that the data track length is missing. So in this case Cuetools doesn't display an important information for you. It's normal but it's paradoxal.
Example:
Verify+Only if found:
[Verification date: 06/05/2010 00:02:41]
[AccurateRip ID: 0016f8d6-00d48840-a50c040d] disk not present in database.
CD-Extra data track length 08:56:44 - 08:57:43.
[CTDB TOCID: jYPeHFZN6n2dunXqLH_YAlPVfIs-] found.
You wasted the exact data track length which is included in CTDB but not displayed.
Same Verify+Default:
[Verification date: 06/05/2010 04:49:01]
[AccurateRip ID: 0016f8d6-00d48840-a50c040d] disk not present in database.
CD-Extra data track length 08:56:44 - 08:57:43.
[CTDB TOCID: jYPeHFZN6n2dunXqLH_YAlPVfIs-] found.
[ CTDBID ] Status
[75314992] (40/78) Is an Enhanced CD, data track length 08:57:40, Accurately ripped
[853a89a6] (38/78) Is an Enhanced CD, data track length 08:57:40, No match
Disk not present in database.
Track Peak [ CRC32 ] [W/O NULL]
-- 99,4 [297DBA6E] [FB457C98]
01 99,4 [55D2767C] [594EC380]
02 99,4 [AE16827C] [4CECCE03]
03 99,4 [89B41C5C] [3493DC21]
04 99,4 [9DC6F91F] [DCE80902]
05 99,4 [2AA3EF16] [E3749205]
06 99,4 [124F5ADD] [2620D55A]
07 99,4 [250BBA83] [982E88AE]
08 99,4 [9EE7922B] [1CF6AAF0]
09 99,4 [69DC48DF] [ACBE00DF]
10 80,6 [E7AB247B] [57201234]
11 99,4 [3B379612] [4EBC6F88]
12 99,4 [5A324E99] [20437F56]
Conclusion:
In some case it might be usefull to display CTDB information even if the rip is not found in the AR database.
IMHO, it's either you always display the CTDB information by default or you introduce a new verify mode, something like "Verify+Only if found+Always display CTDB information no matter AR result".
Thx Greg.
Topic: CUETools versions 1.9.5 through 2.1.6 (Read 1907342 times)
previous topic - next topic