Currently, when you try to use "rate" in the tagging dialog directly, it again uses the same free-form mechanism it uses for "RATING": "���name����rate���data�������50". What fb2k really should do is map "RATING" from the dialog to the MP4 tag field "rate", which seems to use decimal values from 0 to 100 as text. m4a file, fb2k obviously uses a mechanism of MP4 tags where you can freely define the name field and writes the following bytes where it retains the value from the dialog (doesn't virtualize it): "���name����RATING���data�������4".
When you use fb2k's tagging dialog to set "RATING" for an. m4a files, but I seem to understand enough to tell what's the problem here. I'm not an expert regarding the inner structure of.
This also shows that fb2k virtualizes the "RATING" value, because it's not directly the one shown in the dialog and I need to do the following calculation to get from what HxD shows to what the dialog shows (guessed formula): byte_value / 255 * 4 + 1. mp3 file, it writes the "POPM" field to the file as my hex editor HxD shows: "POPM���#��Windows Media Player 9 Series�€����". When you add a "RATING" field with the tagging dialog of an. mp3 files that fb2k already is capable of: First, a few words on the sane handling of rating tag fields for.
0 kommentar(er)
