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: Track file size changed after cuetools fix (Read 401 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Track file size changed after cuetools fix

Hello

I sometimes uses cuetools in order to repair slightly damaged rips.

When I run cuetools to repair an entire CD rip, but with just one track in error, the size of all the files
change. And the file size change can be a few hundred of KBytes !

Is there an explanation for that : is it only the tagging space use in the files ?

Thank you for your answer. I hope I've been clear enough

linuxgalere

Re: Track file size changed after cuetools fix

Reply #1
CUETools will encode again (losslessly, so that is no problem but for the time it takes).

Say you are using FLAC, try to drag the slider to 0 and to 8 and see the difference.
High Voltage socket-nose-avatar

Re: Track file size changed after cuetools fix

Reply #2
Code: [Select]
metaflac --show-md5sum *.flac
Shows the stored (calculated during the creation of the flac file) md5 hash of the decoded audio in the flac file, so no matter what compression you use it should always be the same. In your scenario, if you ran it before and after a fix only the track that was fixed should change.

Code: [Select]
flac --test *.flac
Can be used to check that the stored MD5 still reflects the decoded audio. This shouldn't be necessary in your scenario, but is useful if you want to check for potential bit-rot of the audio data.

Re: Track file size changed after cuetools fix

Reply #3
If you want to do this kind of exercise, it is probably easier to dump the "before" and the "after" into foobar2000 and user the foo_bitcompare component. Especially since one can also use CUETools to fix offset (shifting the bitstream to the left or right), an operation that moves audio in between files and thereby does alter the MD5.
High Voltage socket-nose-avatar

 

Re: Track file size changed after cuetools fix

Reply #4
@Porcus
I was not only giving @linuxgalere a simple way to compare the audio of flac files using the native flac methods, but hopefully educating them about the fact that there's a hash of the audio data contained in the FLAC metadata itself.

If you want to do this kind of exercise, it is probably easier to dump the "before" and the "after" into foobar2000 and user the foo_bitcompare component.
Given that this is probably just a one off learning exercise, I doubt unzipping metaflac is harder than installing and configuring foobar and bitcompare!

I'm struggling here, but what is a real life use case for that component? We have AccurateRip and CTDB to verify files/rips, and you can run a test against a FLAC to see if the audio is still correct (that it matches the stored MD5), so what do people use this for?