(2) Can we please have some documentation for mp3tag about the special fields like "COMMENT ITUNPGAP"? I searched through the help and couldn't find anything about these field types. (1) Is my description above correct or have I misunderstood what is happening? I wrote something into the "Disk n of n" field which then updated everything in the database over several minutes. You actually need to write something to make it work, so pick an unwanted field. ![]() The best way I found was to select everything then open Get Info on all the files together. So it's a bit tricky to update the whole database at once. iTunes will only read the tags from the file when you play it or open the Get Info dialog. I then updated the database in iTunes by re-reading the tags from the files. This is important if you want iTunes to read the new value and discard the one it already has. I then selected the files which had corrupted comments and changed the comment to a single space. In mp3tag I selected all the files at once and used the extended tag editor to delete the extra iTunes tags. So I have done a mass cleanup and removed these unwanted tags completely to avoid further trouble. ![]() You can then edit the contents or delete the tag completely. It displays the extra comments in the extended tag editing box like this "COMMENT ITUNPGAP". The good news is that mp3tag handles everything correctly. There are lots of reports of other people with this problem, but few explanations. You end up with lots of files where the comments are strings of hex numbers. But something messes up the tags so that the data from the special comment turns into a regular comment. They are all good programs and I wouldn't criticise them. At various times I have used MediaMonkey, XMPlay, Winamp and others. I haven't been able to track down which program is mangling these frames in my files. Presumably when the program sees a null in the middle of the comment it ignores the whole thing. I'm not sure what algorithm programs use for this. In most programs you wouldn't know these extra COMM frames were there at all. I've seen content descriptors like iTunPGAP, iTunNORM, iTunSMPB, iTunes_CDDB_1, iTunes_CDDB_TrackNumber. ITunes adds several of these extra COMM frames for its own purposes. There is a null between the content descriptor and the actual value. Then any additional comments are in extra COMM frames which have a special content descriptor. The regular comment is in a frame called COMM (or COM in the earlier v2.2 standard). This is unlike most other tag types which can only occur once in a file. In ID3 a file can have multiple comment tags. Please correct me if I got anything wrong. I've written down what I found so far to help other people. Few people seem to understand it fully and most of them are on this board. ![]() I've done a lot of searching but there isn't much information around. The result is the tags often get mangled and you end up with garbage in the comments like strings of hexadecimal numbers. iTunes and mp3tag can handle them correctly, but some other programs get confused. It looks like iTunes adds these as multiple comment frames. These are for things like volume normalising (SoundCheck), gapless playback, CDDB, etc. ![]() I was confused by the special tags that iTunes adds to mp3 files. But my NAS is set up to use iTunes and I wanted to stick with WAV files so glad to have found a working solution.I'd like some help, please, from Florian and the experts here. The insurmountable problem appears to be the artwork, which iTunes won't export as far as I can tell. Probably the best solution is not to use iTunes at all. (Thank goodness the NAS stores each album in a separate folder.) This is a bit laborious and I need to delete the index each time I want new music to appear in the BlueSound app but it works and the Node is spectacular. I simply select the relevant songs and an edit box appears that allows me to insert this information. In MediaMonkey I found the files stored on my NAS and what I found was the song titles but no album or artist info. My solution however was to download a programme called MediaMonkey onto my PC and use that to alter the files so the Node can recognise the artists and the album title. (Thank you to BlueSound support for running the tests to find this out). One answer is that WAV files in iTunes do not support metadata (which is already too technical for me but what it means is you get the song titles only, not artist or album info!) but other iTunes files do.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |