IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> [X] MP4 New Tag Problems
AlanH520
post Oct 27 2017, 23:17
Post #1


Member


Group: Members
Posts: 2
Joined: 24-October 17
Member No.: 24075
Mp3tag Version: 2.84a



This is a problem I have with %movementname%, %movement%, and %showmovement%. Everything works correctly for %work%.

I have, for example, an album that I have recorded, with three multiple-movement classical works on it, rendered as ALAC files for this example. I tag it with mp3tag, including the new iTunes tags. When I add these files to iTunes, a few files show up correctly but most are missing the movement name and number and the showmovement tag does not take effect on these files.

I manually edit the missing information in iTunes, and mp3tag shows the original information. dbPoweramp's ID-Tag then shows two tags for each of these elements, one supplied by mp3tag and one supplied by iTunes (I do not have a lower-level mapping of these tags than the ID-Tag descriptions): ID-Tag reports the original "showmovement" with the iTunes "Show Work Movement", the original "movementname" with the iTunes "Movement Name", the original "movement" with the iTunes "Movement Number", and iTunes also adds "Movement Count" (which I did not originally supply) with a value of 0. mp3tag only sees the originals it put there in the first place, and I confirmed by changing them in fresh copies before importing to iTunes, tagging in iTunes as before, and the result was two distinct versions of each tag.

dbPoweramp appears to read the atoms created by iTunes correctly but these appear to be different than what mp3tag writes.

I tried reading a hex dump of one of the ALAC files and it appears that Movement Name is mvn, Movement Count is mvc, and Show Work Movement is shwm, but I have not (yet) found the iTunes value for Movement Number. The mp3tag %work% maps to ©wrk according to main_tags.html and appears to be accepted as is by iTunes.

UPDATE: I have attached a binary file (renamed as .txt so it would upload, but please open with a hex editor) with extracts from the metadata encountered in one of the files. The tags added by iTunes are at the end (after a 16-byte "line" as displayed in a hex editor as all 00, and they are ©mvn, ©mvi, ©mvc, and shwm. All original tags are in the first portion of the file, including correctly written ©wrt etc. but the problem tags seem to have munged keys "M----", "I----" and "s----" with further information marked "mean" then "com.apple.iTunes" then "name" then, respectively, "showmovement", movement", and "movementname". I do not know if these were created by mp3tag or interpreted from the original tags and inserted by iTunes.

This post has been edited by AlanH520: Oct 28 2017, 17:06
Attached File(s)
Attached File  metaextracts_binary_file.txt ( 1.06K ) Number of downloads: 16
 
Go to the top of the page
 
+Quote Post
AlanH520
post Oct 29 2017, 17:27
Post #2


Member


Group: Members
Posts: 2
Joined: 24-October 17
Member No.: 24075
Mp3tag Version: 2.84a



QUOTE (AlanH520 @ Oct 28 2017, 00:17) *
This is a problem I have with %movementname%, %movement%, and %showmovement%. Everything works correctly for %work%.

I have, for example, an album that I have recorded, with three multiple-movement classical works on it, rendered as ALAC files for this example. I tag it with mp3tag, including the new iTunes tags. When I add these files to iTunes, a few files show up correctly but most are missing the movement name and number and the showmovement tag does not take effect on these files.

I manually edit the missing information in iTunes, and mp3tag shows the original information. dbPoweramp's ID-Tag then shows two tags for each of these elements, one supplied by mp3tag and one supplied by iTunes (I do not have a lower-level mapping of these tags than the ID-Tag descriptions): ID-Tag reports the original "showmovement" with the iTunes "Show Work Movement", the original "movementname" with the iTunes "Movement Name", the original "movement" with the iTunes "Movement Number", and iTunes also adds "Movement Count" (which I did not originally supply) with a value of 0. mp3tag only sees the originals it put there in the first place, and I confirmed by changing them in fresh copies before importing to iTunes, tagging in iTunes as before, and the result was two distinct versions of each tag.

dbPoweramp appears to read the atoms created by iTunes correctly but these appear to be different than what mp3tag writes.

I tried reading a hex dump of one of the ALAC files and it appears that Movement Name is mvn, Movement Count is mvc, and Show Work Movement is shwm, but I have not (yet) found the iTunes value for Movement Number. The mp3tag %work% maps to ©wrk according to main_tags.html and appears to be accepted as is by iTunes.

UPDATE: I have attached a binary file (renamed as .txt so it would upload, but please open with a hex editor) with extracts from the metadata encountered in one of the files. The tags added by iTunes are at the end (after a 16-byte "line" as displayed in a hex editor as all 00, and they are ©mvn, ©mvi, ©mvc, and shwm. All original tags are in the first portion of the file, including correctly written ©wrt etc. but the problem tags seem to have munged keys "M----", "I----" and "s----" with further information marked "mean" then "com.apple.iTunes" then "name" then, respectively, "showmovement", movement", and "movementname". I do not know if these were created by mp3tag or interpreted from the original tags and inserted by iTunes.


Please remove this from Bug Reports. I have ascertained that this problem is introduced by relying on dbPoweramp to write the tags when I use it to batch convert from FLAC to MP3, OGG, AAC, and ALAC. I have solved this by doing all the conversions first, then using mp3tag to tag the FLAC files, then copying and pasting the FLAC tags to the other formats. I apologize for the time anyone spent analyzing this. I will take the issue up with dbPoweramp. To be posted in General Discussion, I may note that iTunes does not correctly implement "show work and movement" in the Album View (single-movement works are aggregated with the previously track's composer but the right composer is shown in Song and Composer views).
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 20th November 2017 - 03:08