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 1928084 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 #1550 –
Quote from: Gregory S. Chudov on
Probably. I got married and moved from Russia to Canada just three weeks ago, so i am a bit busy at the moment


I already suspected you are human. Congrats and best wishes to you and your wife!! If you still have some habits of your homeland celebrating such things takes its time

Please, when you just find some time you may do a little new compile 2.12.b for example with the recent fix for FlacCL, so i have to celebrate something at least.

Cheers!
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1551 –
Oh my god  ... I just had the same bad feeling as when I learned that Xiphmont had kids ... that day I deleted all my vorbis files & switched to lossless
 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1552 –
Don't worry, we don't have kids  And we actually have been together for 6 years now, we just weren't able to marry before, because Russia is such a backwards country, and because i have a husband, not a wife
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1553 –
Quote from: Gregory S. Chudov on
Don't worry, we don't have kids  And we actually have been together for 6 years now, we just weren't able to marry before, because Russia is such a backwards country, and because i have a husband, not a wife


Ouch! SORRRY! So congrats to you and your husband  Seldom was wrong with that sentense before... Always good for a surprise this forum
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1554 –
Thank you
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1556 –
Oh my  Thanks
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1557 –
Well, that was slightly unexpected. Congratulations and best wishes to you and your husband! I hope you settle in quickly and enjoy living Canada.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1558 –
Quote from: Wombat on
Please, when you just find some time you may do a little new compile 2.12.b for example with the recent fix for FlacCL, so i have to celebrate something at least.

Cheers!

What for a fix is that, if I may ask? 

Congrats to the newlyweds too... If not for the 100000th disc in the CTDB, that's another valid reason to celebrate

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1559 –
Quote from: HotShotFR on
What for a fix is that, if I may ask?

Nothing to wurry to much. I stumbled across a file that gave a verify error. It only seems to happen on files with a special kind of its final block and is ultra-rare. Gregory already has the fix in the Repository.
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1560 –
Yes, CONGRATS! Ain't love grand?

I'm about to split all of my single-file FLACs into multi-tracks. They were ripped with EAC many, many moons ago.

As a noobie to CUETools I was just wondering, should I be applying any offset when splitting? Want to keep everything as original to my CDs as possible!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1561 –
No

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1562 –
That's a bug report, sometimes my CUEtools config file gets reset to defaults.
I've created some new profiles today and added several encoder profiles. After restart the cuetools config were set to defaults and new encoder profiles were lolst. Dunno on which conditions this happens. Mostly my config is kept.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1563 –
I own two copies of the same CD. Why is the first log adding "CD-Extra data track length 18:37:21" to the results line?

Does it mean that CD 1 *should* have the CD-Extra data track, but it doesn't?

Code: [Select]
CD 1:
[CUETools log; Date: 9/19/2011 3:26:14 PM; Version: 2.1.2a]
Pregap length 00:00:01.
[CTDB TOCID: ujvjyuIIqdR61HbcM3huXrxTUi8-] found.
        [ CTDBID ] Status
        [4996818b] (002/224) Has pregap length 00:00:00
        [04b5dfbf] (222/224) [b]CD-Extra data track length 18:37:21, Accurately ripped[/b]
Code: [Select]
CD 2:
[CUETools log; Date: 9/19/2011 3:29:38 PM; Version: 2.1.2a]
Pregap length 00:00:01.
[b]CD-Extra data track length 18:37:21.[/b]
[CTDB TOCID: ujvjyuIIqdR61HbcM3huXrxTUi8-] found.
        [ CTDBID ] Status
        [4996818b] (002/224) Has pregap length 00:00:00
        [04b5dfbf] (222/224) [b]Accurately ripped[/b]

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1564 –
Quote from: a1020012 on
I own two copies of the same CD. Why is the first log adding "CD-Extra data track length 18:37:21" to the results line?

Does it mean that CD 1 *should* have the CD-Extra data track, but it doesn't?

CUETools did not find evidence of a data track for CD 1. By evidence I mean a line in the cue file showing an extra data track or the TOC in the extraction log file showing an extra track. CD 2 has one or both. The audio tracks are showing 'Accurately Ripped' regardless.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1565 –
Quote from: Anakunda on
That's a bug report, sometimes my CUEtools config file gets reset to defaults.
I've created some new profiles today and added several encoder profiles. After restart the cuetools config were set to defaults and new encoder profiles were lolst. Dunno on which conditions this happens. Mostly my config is kept.

I thought  it was my unstable system when it happened to me. Only happened a couple times in v2.1.1. I keep backups now just in case but haven't needed them.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1566 –
> Does it mean that CD 1 *should* have the CD-Extra data track, but it doesn't?
Basically, yes. It means that CD in database has data track, but yours doesn't. I wouldn't go as far as saying that it *should*
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1567 –
Quote from: korth on
Quote from: a1020012 on
I own two copies of the same CD. Why is the first log adding "CD-Extra data track length 18:37:21" to the results line?

Does it mean that CD 1 *should* have the CD-Extra data track, but it doesn't?

CUETools did not find evidence of a data track for CD 1. By evidence I mean a line in the cue file showing an extra data track or the TOC in the extraction log file showing an extra track. CD 2 has one or both. The audio tracks are showing 'Accurately Ripped' regardless.

Very helpful info, thank you! My last question on CD-Extra data tracks then, would be this: To repair CD 1 (add the data track) with CUETools, do I simply enter the proper Data Track into the Extra box in CUETools and re-encode?

Keep in mind, I get it that the album is already good to go. Just trying to get 'er as close to original as possible (and almost done learning CUETools! =) ).

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1568 –
I forgot to mention CUETools looks at the DISCID in the cue file.
No need to re-encode. The data track is not ripped but when calculated into the TOC it changes the DISCID and the AccurateRip ID. If you verify with the data track info entered in the box, the AccurateRip results will be for a different AccurateRip ID. The audio tracks do not change.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1569 –
I get it. Makes perfect sense.

From what I gather, the same also applies to the Pregap. Neither the Pregap nor the Data Track affect the actual audio files, they are just lines in the .cue and/or .log which helps identify a particular Disc. If I'm looking for "bit-perfect" results when burning my files to CD-R, I should have this info.

Again, thank you! Very helpful forum!

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1570 –
By the way, why is it that in foobar2000, the "File Verifier" component is able to correctly verify an album with AccurateRip, even when the Pregap or Data Track info is missing, and CueTools is not able to do this?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1571 –
foo_verifier is verifying against results submitted without pregap or data track. If you try to verify where there isn't a record you'll get
Quote
No such disc found in the AccurateRip database.
Please make sure you have selected a complete disc rip with correct track order.
If the disc contains hidden tracks, you can only verify it through a matching cuesheet with hidden track information intact.
for both missing pregap and missing data track info.
I just checked several discs and the accuraterip results were different (when found) when the pregap or data track info was removed.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1572 –
More testing. Cannot edit previous message. I was testing cue file vs tracks instead of editing the cue file.
Actually the DISCID in the cue file seems to be ignored by foo_verifier and get a syntax error when data track included in cue file. Looks like results are always for a disc without a data track. Jumped the gun on the previous post.

example
foo_verifier (using cue file, DISCID includes data track)
Code: [Select]
Track  Status
01     Accurately ripped, confidence: 7.
02     Accurately ripped, confidence: 7.
03     Accurately ripped, confidence: 7.
04     Accurately ripped, confidence: 7.
05     Accurately ripped, confidence: 7.
06     Accurately ripped, confidence: 8.
07     Accurately ripped, confidence: 7.
08     Accurately ripped, confidence: 7.
09     Accurately ripped, confidence: 8.
10     Accurately ripped, confidence: 8.
11     Accurately ripped, confidence: 7.
12     Accurately ripped, confidence: 7.
CUETools (using same cue file, DISCID includes data track)
Code: [Select]
Track   [ CRC    ] Status
 01     [e2b1cbab] (095/107) Accurately ripped
 02     [c74f8c0f] (096/108) Accurately ripped
 03     [30742b55] (097/108) Accurately ripped
 04     [c36bcd74] (097/109) Accurately ripped
 05     [a8525823] (096/107) Accurately ripped
 06     [74f1b33f] (097/108) Accurately ripped
 07     [4cd6bbdd] (095/106) Accurately ripped
 08     [0273e25a] (094/105) Accurately ripped
 09     [4bf380c6] (094/106) Accurately ripped
 10     [69f77194] (095/107) Accurately ripped
 11     [a9edd59c] (094/106) Accurately ripped
 12     [e2ddc88e] (095/107) Accurately ripped
AccurateRip v2:
 01     [0b7fc922] (006/107) Accurately ripped
 02     [32ee4cd2] (006/108) Accurately ripped
 03     [a8f5820c] (005/108) Accurately ripped
 04     [25dc0d4e] (006/109) Accurately ripped
 05     [ae19fdcb] (005/107) Accurately ripped
 06     [f5cf0306] (005/108) Accurately ripped
 07     [13293e2c] (005/106) Accurately ripped
 08     [4bf07b48] (006/105) Accurately ripped
 09     [aa2f352e] (006/106) Accurately ripped
 10     [3cc3b0c7] (006/107) Accurately ripped
 11     [fef6160e] (006/106) Accurately ripped
 12     [794fe5df] (006/107) Accurately ripped
Offsetted by -646:
 01     [700314b4] (006/107) Accurately ripped
 02     [403c0a7a] (006/108) Accurately ripped
 03     [a30e8c9e] (006/108) Accurately ripped
 04     [7eca1d58] (006/109) Accurately ripped
 05     [5745968f] (006/107) Accurately ripped
 06     [877732bb] (006/108) Accurately ripped
 07     [ed0626a3] (006/106) Accurately ripped
 08     [2f32b28a] (005/105) Accurately ripped
 09     [ef5e582d] (006/106) Accurately ripped
 10     [6e7301ad] (006/107) Accurately ripped
 11     [e47058b1] (006/106) Accurately ripped
 12     [d3ca62a5] (006/107) Accurately ripped
CUETools (no DISCID in cue file, no data track info)
Code: [Select]
 01     [e2b1cbab] (07/09) Accurately ripped
 02     [c74f8c0f] (07/09) Accurately ripped
 03     [30742b55] (07/09) Accurately ripped
 04     [c36bcd74] (07/09) Accurately ripped
 05     [a8525823] (07/09) Accurately ripped
 06     [74f1b33f] (08/10) Accurately ripped
 07     [4cd6bbdd] (07/09) Accurately ripped
 08     [0273e25a] (07/09) Accurately ripped
 09     [4bf380c6] (08/10) Accurately ripped
 10     [69f77194] (08/10) Accurately ripped
 11     [a9edd59c] (07/09) Accurately ripped
 12     [e2ddc88e] (07/09) Accurately ripped
AccurateRip v2:
 01     [0b7fc922] (02/09) Accurately ripped
 02     [32ee4cd2] (02/09) Accurately ripped
 03     [a8f5820c] (02/09) Accurately ripped
 04     [25dc0d4e] (02/09) Accurately ripped
 05     [ae19fdcb] (02/09) Accurately ripped
 06     [f5cf0306] (02/10) Accurately ripped
 07     [13293e2c] (02/09) Accurately ripped
 08     [4bf07b48] (02/09) Accurately ripped
 09     [aa2f352e] (02/10) Accurately ripped
 10     [3cc3b0c7] (02/10) Accurately ripped
 11     [fef6160e] (02/09) Accurately ripped
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1573 –
Two easy Q's about offsets, then I think I'm good to go with CUETools (love this app!).

1. Approximately how many seconds (milliseconds) are there for one offset? e.g. +6 offset = X milliseconds. Or, stated differently, how many write offsets would equal one second of audio? Just looking for a guesstimate, not an exact calculation.

2. When selecting "fix offset", does CUETools GUESS which offset is correct (assuming there are multiple offsets that would make all tracks Accurate) or does it use info from the .cue (DISCID?) and/or .log?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1574 –
1: As far as I remember 1 is 1/75 of a second.
2: By default CT fix to closest, there is a radio button to fix to highest. (It doesn't guess.)