Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: “Movement” tags not mapping consistently (Read 793 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

“Movement” tags not mapping consistently

When reading Movement tags from an MP3 or MP4, foobar2000 maps these to the following fields:

MP3
MVIN = %MOVEMENT INDEX%
MVIN = %MOVEMENT COUNT%
MVNM = %MOVEMENT NAME%

MP4
©mvi = %MOVEMENT INDEX%
©mvc = %MOVEMENT COUNT%
©mvn = %MOVEMENT%

This means there are two possible field names for the same value of “Movement Name”, depending on the file type.

If you have a source file (e.g. FLAC) that uses %MOVEMENT NAME% and convert this to MP3, you get a MVNM tag. However, if you convert the same source file to MP4, you get a custom com.apple.iTunes:MOVEMENT NAME tag instead of ©mvn.

The reverse applies if you have a source file that uses %MOVEMENT% – you get an MP4 with a ©mvn tag, but the MP3 ends up with a TXXX:MOVEMENT tag instead.

Would it be possible to update the handling of MP4’s ©mvn to map to %MOVEMENT NAME% instead?

(I’d add that MusicBrainz and Mp3tag use %MOVEMENT% for MVIN/©mvi, and %MOVEMENTNAME% for MVNM/©mvn, which could cause tagging issues when using %MOVEMENT% for the Movement Name if using both foobar2000 and Mp3tag for tagging.)

Re: “Movement” tags not mapping consistently

Reply #1 –
Noted, thanks for bringing this up.
Microsoft Windows: We can't script here, this is bat country.