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: Lossless transcodes with verification of audio MD5 (Read 4681 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Lossless transcodes with verification of audio MD5

How do I transcode from WavPack <-> WavPack or WavPack <-> FLAC while verifying that audio md5 in source and destination files is identical? As far as I know the verify option of WavPack only operates on the output file and doesn't compare it to the input file.

Does dbPowerAmp do it when transcoding between FLAC and WV?

Any other option to transcode a huge directory tree with md5 verification?

Can caudec do it?

Re: Lossless transcodes with verification of audio MD5

Reply #1 –
I'm not sure about the other options, but if the source files contain MD5 sums and you use the wavpack executable to transcode and specify -v, then the source file will be verified with its MD5 and the destination file will be reread and verified with the same MD5. All of this is done before the original file is deleted (assuming it's being overwritten). Obviously this is only true transcoding wavpack to wavpack.

Re: Lossless transcodes with verification of audio MD5

Reply #2 –
Thanks. So the following is safe to transcode an entire collection in-place?

Code: [Select]
find . -name '*.wv' -print0 | xargs -n1 -P4 -0 wavpack -qyztvm -x4

If no output no errors?

Re: Lossless transcodes with verification of audio MD5

Reply #3 –
Yeah, that should work fine. No output; no errors.

One thing to keep in mind though is if you have hybrid files. If they're lossy then they won't be converted to lossless (that's an error). If they're hybrid lossless then the correction files won't be deleted (although they won't cause trouble, they'll just take up space). You can fix that by adding a -d (for delete source) to your command string.