Relatedly, I was contemplating running through my entire library with:
"mp3check --cut-junk-start --cut-junk-end --recursive --only-mp3"
But i'm now concerned that it might be stripping IDEv2 frames etc.
Would
"mp3check --recursive --only-mp3 --ign-junk-end --ign-junk-start
--ign-bitrate-sw --log-file=mp3checklog.txt"
create a log of only mp3 files with:
128 byte TAG after last frame,
invalid frame header,
crc errors,
truncated last frames,
switching of constant parameters, such as sampling frequency?
Also: Given the existence of "--ign-bitrate-sw", would running "mp3check
-e --fix-headers" over a VBR MP3 cause the problem in stage 15 of my
main message above? If so, please could that be added to the manpage
e.g.
"
--fix-headers
fix invalid headers (prevent constant parameter switching),
implies -e, use with care. Incompatible with VBR files and will
destroy them
"
Or potentially add an IF statement into the codebase along the lines of
"IF --fix-headers = TRUE
IF file = VBR
THEN --ign-bitrate-sw"
?
I don't know how to code really so this is just a guess, but you get the gist.
Cheers!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348223
Title:
Mp3check corrupting IDEv2 tags? FixHeaders kills files?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mp3check/+bug/1348223/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
