Author Topic: song encoding recognized incorrectly  (Read 1191 times)

getmusicbee_account1111

  • Jr. Member
  • **
  • Posts: 43
Somehow half the mp3s that I know are encoded in v0 are shown as anywhere from v5 to v10. How does MusicBee check the encoding, and why would this  be the case? Using 3.3.7109 (latest at the time of the post).
Sample file: https://www.mediafire.com/file/72er2o874gligqk/Melanie_Martinez_-_Pity_Party.mp3/file

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34344
thanks for sending the file.
The quality setting on that file is being reported as per the "Xing" header set in the file. I compared it with the "mp3 diag" tool which is reporting the same value.
I have changed MB to not display the value when set to zero as is the case here

https://getmusicbee.com/patches/MusicBee33_Patched.zip
unzip and replace the existing musicbee files
you will need to rescan the relevant file(s)
Last Edit: June 23, 2019, 04:43:12 PM by Steven

getmusicbee_account1111

  • Jr. Member
  • **
  • Posts: 43
That works, thank you!
I understand that it has nothing to do with MusicBee, but are they being reported incorrectly because the metadata is corrupt/wrong? I re-encoded most of them myself with ffmpeg (which uses Lame) with something like
Code
ffmpeg -i "file.flac" -c:v copy -q:a 0 "file.mp3"
Is there anything I can edit in the command so that newly re-encoded files are reported correctly?

Also sorry for the late reply, I just noticed this  :-[