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 1925758 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 #1500 –
Thanks for the replies.

Quote from: Gregory S. Chudov on
Quote from: giant walking robot on
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?



Forgive my naivety, but if they're virtually meaningless why does everyone crap their drawers about them?

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1503 –
Quote from: Gregory S. Chudov on
Quote from: robbo1802 on
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.


Hello Gregory,


Yes, so do I.  I suspect that I am unaware of many of the capabilities of Cuetools and it will take a while to learn with many discarded FLACs along the way.  A quick scan of this thread seems to show 3 main topics:

1.  general enquiries about how to do things,
2.  suggestions for new features/improvements,
3.  what does this log mean?

Of these the third seems the one that causes the most confusion.  One suggestion might be to create 3 stickies rather than just one big one.

I am still very happy that my searching lead me to CueTools.

Regards,
Bob

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1504 –
I agree, robbo1802. IMVHO Cuetools and its CTDB would deserve a category on its own

Bug report (?): when converting with Cuetools 2.1.2a, the resulting files have their name truncated at dots ('.') if the naming template uses %filename% and the converted file has dots in its name.
edit: The same seems to apply for other tags, for instance %album%.

e.g. Aaron Copland - Symphony No.3 and 4.wav converts to Aaron Copland - Symphony No.flac

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1505 –
Hi 

Using CUETools can i split one big FLAC image with cue sheet into tracks without any conversion ? I mean split it into number of wavs and than convert them back into number of flac files...

thnx in adv. 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1506 –
Quote from: ladjack on
Hi 

Using CUETools can i split one big FLAC image with cue sheet into tracks without any conversion ? I mean split it into number of wavs and than convert them back into number of flac files...

thnx in adv. 


FLAC is lossless compression, not a conversion. No wavs are harmed in the process. No audio data is lost.
CUETools does everything on-the-fly so a big flac goes in, little flacs come out. You don't need to decompress the file first.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1507 –
Quote from: korth on
FLAC is lossless compression, not a conversion. No wavs are harmed in the process. No audio data is lost.
CUETools does everything on-the-fly so a big flac goes in, little flacs come out. You don't need to decompress the file first.


Yes, but the bitrate changes...obviously it depends on what level of compression i select under the `Encoder to use` drop down.

Anyway, thnx korth 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1508 –
Quote from: ladjack on
Yes, but the bitrate changes...obviously it depends on what level of compression i select under the `Encoder to use` drop down.

Yes the bitrate changes depending on how much effort the encoder is asked to make.  The end result is still lossless.  Maybe I'm missing your point.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1509 –
Quote from: greynol on
Yes the bitrate changes depending on how much effort the encoder is asked to make.  The end result is still lossless.  Maybe I'm missing your point.


Ok, i see...so as a result i can get multiple tracks in flac with bitrate greater or smaller than original...
The point was to get those tracks with equal bitrate as in the original flac image.

thnx 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1510 –
I can't imagine why you might want to have equal bitrate. In lossless compression bitrate doesn't affect the audio quality.
Back to your original question, it's not possible to split FLAC without reencoding, because track boundaries don't match frame boundaries, and FLAC format (to be more precise, FLAC subset format which is designed to be compatible with hardware devices etc) doesn't allow variable frame size. Only the last frame in file can be shorter than other frames, so you can shorten the file by reencoding only it's last frame, but you can't extract e.g. second track by reencoding only the first and the last frame, because first frame cannot be shorter than other frames.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1511 –
Gregory S. Chudov, very thank you! It is quite useful information for me.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1512 –
I cannot figure out why the files are not being split with Cue Tools 212a.  I'm using Windows 7.  When I select go, I get no change. Any help would be greatley appreciated.  Worked with XP perfectly

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1513 –
Hi everyone !

Does anybody know if the "Correct filenames" option is available from the command line ? 
I recently renamed a big part of my library and I would like to "correct the filenames" in batch.   

Thanks in advance

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1514 –
Quote from: amberdevo on
When I select go, I get no change.

Hmm... AFAIK this only happens if you select a folder with no cue sheets and/or supported audio files in it.
CUETools batch-processes this folder, finds nothing, so has nothing to report.

Quote from: eyes adrift on
Does anybody know if the "Correct filenames" option is available from the command line ? 
I recently renamed a big part of my library and I would like to "correct the filenames" in batch. 

It is not (yet) supported from the command line, but you can process the whole folder from the GUI.

BTW, are there any CUETools users in Ottawa?
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1515 –
Quote from: Gregory S. Chudov on
Quote from: Tigerman on
Problem: I can't repair it, there 's no possibility (afaict) to tell cuetools which CTDBID to use  if there's more than 1.

I thought CUETools was displaying a choice in such cases. I'll check if it's broken when i get home.
UPD: works for me:
Make sure you selected 'Encode' action and 'repair' script. Just in case, i removed the duplicate entry from the database. There was a bug for some time last year which caused some duplicate entries, i thought them harmless and didn't get around to remove them.


Should I have a choice to repair in the example below?

[ CTDBID ] Status
[ef492ed9] (330/332) Differs in 3875 samples @48:39:40-48:39:49
[97d87220] (002/332) Accurately ripped

The repair script stops after verify.
korth

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1517 –
Not yet, but I'm there anyway
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1518 –
Extreme noob here lol

OK after I use cuetools how do I use the resulting .cue file to get the single tracks?   
I use winamp.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1519 –
Not sure what you mean, but my guess is you would want to enable the option to create .m3u playlists.
I'm not sure if winamp can read .cue files. But you can just add the resulting tracks to playlist manually.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1520 –
Thanks

What player can read .cue files?
Does creating .m3u files cause loss of quality? Maybe I need a different player.

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1521 –
.m3u files are playlist files, they don't affect quality in any way. Playlists actually contain only a list of audio files, so that you can easily open the whole album in winamp by clicking on this playlist file, instead of opening tracks one by one.

foobar2000 is a good alternative to winamp, but it doesn't support .cue files too well either, and it's user interface is not designed for casual user.
CUETools 2.1.6

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1522 –
If I use the .m3u's then I will see a list of each song in winamp play list then, right? So if I want to hear track3 from several albums I can. Right? Because thats what I want to do is select tracks from several artist to play.


Thanks for your help Gregory, much appreciated. I tried it and all is good.   

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1523 –
OK I'll try another question. I'm still searching to see if this or the previous question was asked before.

I've been seeing results like this one

Code: [Select]
[CTDB TOCID: 0xlC92mqIn7mwnplhFVmHA4rjlY-] found.
        [ CTDBID ] Status
        [b4592682] (88/88) Accurately ripped
[AccurateRip ID: 000b1306-004adc5d-5608ee08] found.
Track   [ CRC    ] Status
 01     [adbce40e] (029/149) Accurately ripped
 02     [e740a0db] (028/148) Accurately ripped
 03     [e79c7318] (028/146) Accurately ripped
 04     [c44295bf] (028/147) Accurately ripped
 05     [ea8c045c] (028/146) Accurately ripped
 06     [0fcba565] (027/146) Accurately ripped
 07     [8c458acd] (027/146) Accurately ripped
 08     [26ab6590] (000/142) No match but offset
Offsetted by 42:
 01     [eb8d5120] (014/149) Accurately ripped
 02     [0413bddb] (014/148) Accurately ripped
 03     [b886ea65] (014/146) Accurately ripped
 04     [49bf759a] (013/147) Accurately ripped
 05     [875de345] (014/146) Accurately ripped
 06     [f919c6b9] (014/146) Accurately ripped
 07     [8686d4c4] (014/146) Accurately ripped
 08     [1c801f94] (000/142) No match but offset
Offsetted by 298:
 01     [3a7b88e9] (002/149) Accurately ripped
 02     [d8c6053f] (002/148) Accurately ripped
 03     [84e5966e] (002/146) Accurately ripped
 04     [55d761d8] (002/147) Accurately ripped
 05     [ea708335] (002/146) Accurately ripped
 06     [7df4b101] (002/146) Accurately ripped
 07     [577a86ca] (002/146) Accurately ripped
 08     [047859ca] (000/142) No match but offset
Offsetted by 507:
 01     [cb8bebe4] (015/149) Accurately ripped
 02     [fd9fa8f4] (014/148) Accurately ripped
 03     [55b07c40] (015/146) Accurately ripped
 04     [3bd51c09] (015/147) Accurately ripped
 05     [8de4601c] (015/146) Accurately ripped
 06     [f93fe548] (015/146) Accurately ripped
 07     [f9bc529e] (014/146) Accurately ripped
 08     [063165a8] (000/142) No match but offset
Offsetted by 811:
 01     [71ec5c0e] (003/149) Accurately ripped
 02     [82299d37] (003/148) Accurately ripped
 03     [ccbfe9c4] (003/146) Accurately ripped
 04     [48f90028] (003/147) Accurately ripped
 05     [825c40e4] (003/146) Accurately ripped
 06     [981bb1a9] (003/146) Accurately ripped
 07     [53fea103] (003/146) Accurately ripped
 08     [e8fd37de] (000/142) No match but offset
Offsetted by 877:
 01     [51feea25] (025/149) Accurately ripped
 02     [7beddb21] (027/148) Accurately ripped
 03     [afa33713] (026/146) Accurately ripped
 04     [197f6ece] (027/147) Accurately ripped
 05     [d57c50fd] (026/146) Accurately ripped
 06     [fcac310b] (025/146) Accurately ripped
 07     [1878fb04] (027/146) Accurately ripped
 08     [a8158472] (000/142) No match but offset
Offsetted by 1154:
 01     [3c7eb595] (003/149) Accurately ripped
 02     [9ad1911e] (003/148) Accurately ripped
 03     [c5233b90] (002/146) Accurately ripped
 04     [25a524eb] (003/147) Accurately ripped
 05     [d4ce2e22] (002/146) Accurately ripped
 06     [74306f83] (003/146) Accurately ripped
 07     [ce99aa36] (003/146) Accurately ripped
 08     [67907443] (000/142) No match but offset
Offsetted by 1243:
 01     [edd298c6] (004/149) Accurately ripped
 02     [192987c3] (004/148) Accurately ripped
 03     [e9bbf0a8] (004/146) Accurately ripped
 04     [a91048e4] (004/147) Accurately ripped
 05     [d08f5b2c] (004/146) Accurately ripped
 06     [a649ed28] (004/146) Accurately ripped
 07     [0041dcca] (004/146) Accurately ripped
 08     [3d095324] (000/142) No match but offset
Offsetted by 1499:
 01     [6bfcf7a5] (002/149) Accurately ripped
 02     [4f442436] (002/148) Accurately ripped
 03     [2c99ac18] (002/146) Accurately ripped
 04     [6bca2f12] (002/147) Accurately ripped
 05     [ea21580d] (002/146) Accurately ripped
 06     [721c9baf] (002/146) Accurately ripped
 07     [e01cef9d] (002/146) Accurately ripped
 08     [fcacb219] (000/142) No match but offset
Offsetted by 1587:
 01     [73748552] (003/149) Accurately ripped
 02     [5d4ae6a4] (003/148) Accurately ripped
 03     [0d3dda88] (003/146) Accurately ripped
 04     [f7c4b097] (003/147) Accurately ripped
 05     [000a2afb] (003/146) Accurately ripped
 06     [68c8e36b] (003/146) Accurately ripped
 07     [66f7af31] (003/146) Accurately ripped
 08     [880d2d77] (000/142) No match but offset
Offsetted by 1823:
 01     [a8bab76f] (010/149) Accurately ripped
 02     [a00733a4] (009/148) Accurately ripped
 03     [e34a7302] (009/146) Accurately ripped
 04     [407c2bf4] (009/147) Accurately ripped
 05     [41b0f5f5] (009/146) Accurately ripped
 06     [99a26722] (009/146) Accurately ripped
 07     [e9397a91] (009/146) Accurately ripped
 08     [9e43d20a] (000/142) No match but offset
where the last track has no matches in AccurateRip yet shows Accurately ripped in the CTDB.
Sometimes even when the CTDB differs by a few samples and the rip can be repaired, after repair the results are similar to above.
korth
 

CUETools versions 1.9.5 through 2.1.5 (current)

Reply #1524 –
Quote from: korth on
Should I have a choice to repair in the example below?
The repair script stops after verify.

You should. I will look into it.

Quote from: korth on
I've been seeing results like this one
where the last track has no matches in AccurateRip yet shows Accurately ripped in the CTDB.
Sometimes even when the CTDB differs by a few samples and the rip can be repaired, after repair the results are similar to above.

AR and CTDB ignore slightly different amount of data at the start/end of the disc. CTDB entry also might have a substantial offset, adding to this blind-spot or reducing it.
CUETools 2.1.6