Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-2825

Picard writes MVIN and MVNM tags when configured for id3v2.3

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Normal Normal
    • None
    • 2.8.5
    • Plugins, Tags & Metadata
    • None
    • Debian Bookworm amd64

      When using Picard with mp3 files and id3v2 version 2.3 tagging configured, the "Work and Movement" plugin writes MVIN and MVNM tags even though these are not valid tags for id3v2.3.  If id3v2.3 tagging is selected, these tags should be written as some form of TXXX tags.

      Granted this is probably mostly the fault of the "Work and Movement" plugin, but at a minimum Picard should not allow invalid tags to be written, and preferably they should be converted to a TXXX tag (like other tags that are not valid in id3v2.3).

          [PICARD-2825] Picard writes MVIN and MVNM tags when configured for id3v2.3

          Closing this as wontfix, as there is no intention to change the behavior. The tag is non-standard, but commonly used, specifically it was introduced by Apple Music / iTunes

          Philipp Wolfer added a comment - Closing this as wontfix, as there is no intention to change the behavior. The tag is non-standard, but commonly used, specifically it was introduced by Apple Music / iTunes

          I don't think that's true. Both tags are not part of the ID3 standard at all but got introduced by Apple iTunes, but nowadays commonly understood and used by software. iTunes / Apple Music uses them for ID3 v2.3 as well (actually iTunes for a long time did not properly support v2.4 at all).

          Given that other software supporting these tags, such as MusicBee or MP3Tag, also uses them for both ID3 versions I don't think we should change this and break compatibility.

          Is there a specific reason you want this changed?

          Philipp Wolfer added a comment - I don't think that's true. Both tags are not part of the ID3 standard at all but got introduced by Apple iTunes, but nowadays commonly understood and used by software. iTunes / Apple Music uses them for ID3 v2.3 as well (actually iTunes for a long time did not properly support v2.4 at all). Given that other software supporting these tags, such as MusicBee or MP3Tag, also uses them for both ID3 versions I don't think we should change this and break compatibility. Is there a specific reason you want this changed?

            Unassigned Unassigned
            RoboTardis Robo Tardis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package