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: [Feature request] Support MusicBrainz ID tag mapping (Read 2576 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[Feature request] Support MusicBrainz ID tag mapping

MusicBrainz enabled taggers, such as MusicBrainz Picard, Jaikoz, Mp3tag and others, can write various MusicBrainz IDs for e.g. the recording, release, release group etc. to the tags. For this MusicBrainz has a specification of tag mapping at https://picard.musicbrainz.org/docs/mappings/

Unfortunately foobar2000 does not support the MusicBrainz ID tags, making it difficult for fb2k users to make use of those tags, especially if they use different tagging formats. It would be great if fb2k could support the MusicBrainz ID tags as specified.

As one of the developers of MB Picard I know that this is a pain point for users of both the MB database and fb2k. Given that fb2k otherwise is one of the most customizable players I think it would make sense to offer proper support for the MB specific tags.

Re: [Feature request] Support MusicBrainz ID tag mapping

Reply #3 –
Quote from: fuffi on
How would you expect the tags to be written or shown in f2k?

What should it look like?

I would expect for foobar2000 to fully support those tags and map the different tag names used in different file formats to a single name. E.g. the MusicBrainz Artist ID is written to MUSICBRAINZ_ARTISTID on Vorbis, as a TXXX tag "MusicBrainz Artist Id" on ID3 and to "----:com.apple.iTunes:MusicBrainz Artist Id" on MP4 files.

It would be great if f2k would map this all to one internal name, e.g. "MUSICBRAINZ_ARTISTID". This would allow users to easily make use of the IDs in e.g. scripting.

Quote from: fuffi on
This is not helping?
https://www.foobar2000.org/components/view/foo_musicbrainz

I was told that this mapping is outside the scope of such a plugin. While a plugin could probably write to different tags, I'm not sure it is possible to have it mapped the loaded tags to a single name. But I personally don't know the f2k plugin API, this is just the information I got from others.

Re: [Feature request] Support MusicBrainz ID tag mapping

Reply #4 –
Quote from: anamorphic on
Quote from: fuffi on
This is not helping?
https://www.foobar2000.org/components/view/foo_musicbrainz

Incidentally, this one is possibly outdated. There is a new version by marc2k3. Thread here.

(I'm not sure what MusicBrainz ID tags it writes if any)
Thanks for that! (Not that I've used that component more that once in a year, but nice to know, its not dead. So it maybe will be of any use, someday)

According to what I read on https://marc2k3.github.io/foo_musicbrainz.html (The Nerdy Stuff),
there are some explanations, of what tags are written, but I doubt, phw's questions will be answered.

Quote
When it comes to tagging MBIDs, this component always follows the naming conventions used for Vorbis comments regardless of the underlying file format/tagging sheme.

For example, it will write MUSICBRAINZ_ARTISTID instead of MUSICBRAINZ ARTIST ID to mp3 and m4a files. Repeat that for all tags prefixed with MUSICBRAINZ.

The following differences affect id3 tagging only:

    DISCSUBTITLE is written to TXXX:DISCSUBTITLE rather than TSST
    LABEL is written to TXXX:LABEL rather than TPUB
    MEDIA is written to TXXX:MEDIA rather than TMED
    MUSICBRAINZ_RECORDINGID is written to TXXX:MUSICBRAINZ_TRACKID rather than UFID://musicbrainz.org
    RELEASECOUNTRY is written to TXXX:RELEASECOUNTRY rather than TXXX:MUSICBRAINZ ALBUM RELEASE COUNTRY

For Vorbis comments only, ORIGINAL RELEASE DATE is written in place of ORIGINALDATE. Also, this tag is only written when it differs from DATE.

The whole purpose of this is to unify tag display/search across foobar2000 but it comes at the expense of potentially breaking compatibility with other taggers/players that can make use of MusicBrainz specific data.


Re: [Feature request] Support MusicBrainz ID tag mapping

Reply #5 –
I know about both plugins, and actually the updated foo_musicbrainz is pretty great.

But fuffi is right that it actually does not answer my question. But the quoted text quite nicely explains the issue: In order to make efficient use of the tags in foobar a unified internal tag name independent of format would be required. Many other tools implement the tag mapping for MusicBrainz IDs (in the same way other standard tags get mapped to their corresponding representation in different formats).
 

Re: [Feature request] Support MusicBrainz ID tag mapping

Reply #7 –
Quote from: phw on
This issue is also discussed at https://hydrogenaud.io/index.php?topic=118656.0

As the OP of that thread, I fully appreciate that fact that I'm not alone in my love for the MusicBrainz IDs, and the desire for support by fb2k.

Haven't tried the updated foo_musicbrainz plugin, but I will.

Re: [Feature request] Support MusicBrainz ID tag mapping

Reply #8 –
Picard's fields are generally quite reasonable and unified across formats. Why did you (MB developers) choose to write the ID fields, which you had the freedom to define, differently in MP3 and MP4? Why not have spaces or no spaces in all cases, which would avoid the need for applications handling the mapping?

Re: [Feature request] Support MusicBrainz ID tag mapping

Reply #9 –
Quote from: j7n on
Why did you (MB developers) choose to write [...]
If you want to talk to the devs about their components (which you shoud, when you have something productive to say or ask), you surely at the wrong counter.
Try the next door... :>
(Aka: search for an existing, or create a new thread at a fitting sub-board (i.e. 3d party components), where one of them usually pops up and ask your question.)
They won't come here to check if there is something to solve. (If they even exist...)