-dump $FRAMEID print a hex dump of a specific frame. That's just ugly but not really a problem with the ID3 Tag itself.įirst lets check whats wrong with the song name ( TIT2): The artworks width is shorter than its height.It also explains why the genre name in the first screenshot looks so strange. This is an indicator that the mp3 file was tagged by a software that is not ID3v2 conform and/or has problems with Unicode encoded data. There are two BOMs (Byte Order Marks) in the TCON frame.ID3 allows padding bytes that get striped away by id3edit. This must not be a sign of an invalid Tag. The size given in the ID3 Tag Header will be adjusted. The claimed size of the ID3 Tag is greater than the actual size.The TDRC frame is not defined in ID3v2.3.0 version of the standard that is defined by the header.That's why they do not appear in the result of -get-all. There is a frame not fully supported by id3edit ( TSSE).The result of this first look into the details give us the following information: If there is an artwork embedded, details like the mime type and dimension of the image are displayed.When there is a problem with the UTF-16 encoding, it gets mentioned in yellow.(When they start with a T we can work with them anyway) Gray IDs are IDs that are not directly supported by id3edit.The first column checks if the frames are defined or deprecated in the specific ID3v2 standard.-get-frames prints a list of all available frames including details of their size and encoding as well as other useful information.-showheader prints lots of details of the ID3 header and the frame headers while reading the ID3 Tag.Now we can use id3edit to further inspect the file to figure out what's wrong: We will look at the song name ( TIT2 frame) and genre ( TCON frame) in detail later. Obviously there are some encoding problems and two different release dates. As we discover in this section, this was not true :) Printing the meta data The file was originally tagged by a tool that claimed to support Unicode. Id3edit -get-all Example \ Song.mp3 Debuggingįollowing scenario: The meta data of a song stored in an ID3 tag is invalid.Īs an example I use a song from the band Hämatom. The following example first gets the name of audio file example.mp3, then changes its name to "Example Song Name". Here are some everyday examples as well as an example of how to fix a broken ID3 tag. Lessons learned: Also backup huge data collection and test foreign tools properly before using it in scripts :)Īfter separating id3edit from MusicDB I reviewed the whole code and added some missing features. That's why I needed a "ID3 Debugger" and this project was born. This tool complete messed up all my tags because the promised Unicode support did not work. Only one of them provided a command line interface. I only found only a few editors that were able to work with Unicode at all. Therefore I need an ID3 editor I can call from a script to automate the tagging process.įurthermore they had to be able to use Unicode encoded string (Think of Japanese bands). In the year 2013 I wanted to unify all tags of my music collection. The last three points form the feature list are the reason I developed this tool. For example text frames start with a byte defining the encoding of the text. This information itself can have a further header.
0 Comments
Leave a Reply. |