-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New "artists" tag #1824
Comments
Can you please do a little more investigation into this tag?
|
The tag comes from the Musicbrainz database and has been introduced since picard 1.3 KODI 16 will incorporate the tag to distinguish between multiple artists on on track, that way the artist library is clean and will only contain "Lost Frequencies" and "Janieck Devy" as separate entries instead of one entry as "Lost Frequencies feat. Janieck Devy" |
Thanks for the additional digging! Sadly, Picard's tag mapping page doesn't describe how the field is stored. https://picard.musicbrainz.org/docs/mappings/ In any case, though, this seems like a fine addition if someone's interested in doing the necessary detective work. |
With detective work do you mean what the separator is? |
That's part of it. We also need to investigate whether there's a standard tag storage key/frame type for all of the file types beets supports (MP3, Vorbis comments, ASF, etc.). Or in the absence of a standard, we'll need to figure out what a collection of other software does. |
This is the Artists tag in Picard, as far as I can tell they are separated using the default configured separator in Picard Because there are multiple Artists that also means that there are multiple musicbrainz_artistid The http://id3.org/id3v2.4.0-frames standard states:
This is the Picard ticket about the Artists tag. This post gives some more info on the tag and separators I created test tracks for the KODI team, feel free to use them. Tagged as: Also the same songs tagged with id v2.3 |
Thank you! These sample files (and the Picard ticket for |
You are welcome, let me know if you need anything else. |
@sampsyo, How could I set the separator tag for instance for Genre also to be the one as specified in the standard? I get this error in beets.
|
Perhaps it's possible to use a YAML escape? You'll probably want to google the syntax, but maybe it's |
Great! |
@sampsyo, I'm curious what if I start using Beets now and the extra Artists tag would be included later in Beets. How hard would it be to update all my music with those tags? On a side note I checked the Artists tag and Artist Id tag and they are also separated with the |
Getting new data in the future should just entail an
Can I ask you the favor of looking into exactly what's confusing about the current documentation and improving it with a PR? You're not the only one who has been confused, which suggests that we could do a better job of explaining these commands. |
So let's see if I get it. Do I understand correctly like this? With the multiple artists you will probably run into the same issue as #505 |
Yep, exactly! |
Will give it a try, but I'm no git wizard 😄 |
Could this be treated similarly to how the current 'genres' field works? |
Unfortunately no—the |
I noticed my library was ok with Picard but I had many artists with beet. This was the issue. Will this be implemented? It is time consuming to tag with beet first then make a second pass with picard for the ❤️ |
FYI I added ARTISTS to Songkong and Jaikoz for all formats in order to be able to store multiple artist separately where as ARTIST stores to match the cover e.g Artist=Johnny Cash & June Carter, Artists=Johnny Cash; June Carter. ARTIST only stores one value, ARTIST stored a value per artist so for ID3 format would have a TXXX:ARTISTS frame with '\0' between each artist, for Flac would have two ARTISTS fields. Picard then added in support for this field to match SongKong/Jaikoz. Also have an equivalent ALBUMARTISTS field for the album artist |
Hi, I'd be interested to work on this along with the ability to identify the primary artist (and use it place of the current concatenated artist name). I'd like to know what steps are required to implement this feature and where can I start. |
Definitely very interested to see this implemented alongside #3107. I've tried to create a "Correct" artist model in my music app Auxio that hinges on this kind of multi-artist support, and am now somewhat dismayed that the tags produced by Beets really don't play along well with this system. In particular, I really wish beets defaulted to native multi-value information rather than separator-based information. I would work on this, but given the sheer amount of dependencies on the current artist model by plugins and configuration, I'd imagine it would be extremely difficult. |
Just wondering if this got worked on at all? Is there is any way of using flexible attributes to write the tag in the meantime? |
Musicbrainz Picard can set the Artists tag as far as I can see beets does not do that. Would that be possible?
The text was updated successfully, but these errors were encountered: