Skip to content
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

Support Multiple Artists/Composers/Performers #15

Open
tkem opened this issue Aug 24, 2014 · 16 comments
Open

Support Multiple Artists/Composers/Performers #15

tkem opened this issue Aug 24, 2014 · 16 comments
Labels
C-enhancement Category: A PR with an enhancement or an issue with an enhancement proposal

Comments

@tkem
Copy link
Member

tkem commented Aug 24, 2014

As stated in the README.rst, the current DB schema does not support multiple artists, composers, or performers.

(Non-functional) Requirements:

  • At least for the common, single-artist case, there should be no noticable performance impact (especially on small platforms like the Raspberry Pi).
  • The one result row per track property of the tracks view should be maintained.
  • Denormalization of the schema in general should be avoided, if feasible.
  • Storing data as text ist preferred.
  • An upgrade path for existing users must be provided.
@tkem
Copy link
Member Author

tkem commented Aug 24, 2014

See also beetbox/beets#505 for inspiration.

@tkem
Copy link
Member Author

tkem commented Aug 26, 2014

Actually considered to be of minor priority, since media files containing multiple artist/composer/performer tags are rare. Practically non-existant, IMHO.

@tkem
Copy link
Member Author

tkem commented Oct 8, 2014

Officially deferred until Mopidy gets its new Metadata API, which will require a redesign of the whole database schema anyway.

@tkem
Copy link
Member Author

tkem commented Mar 15, 2015

Current plans for Mopidy Core v1.0 have tracks and albums only contain artist URIs and no longer full Artist models. This better fits the current schema, since the main issue with this is efficiently generating the list of artist models for each track. So track.artists could remain a TEXT field containing ws-seperated URIs as originally planned.

@tkem
Copy link
Member Author

tkem commented Jun 14, 2015

I guess that's Mopidy v2.0 now.

@tatoosh

This comment has been minimized.

@tkem

This comment has been minimized.

@tatoosh

This comment has been minimized.

@tatoosh

This comment has been minimized.

@tkem

This comment has been minimized.

@tatoosh

This comment has been minimized.

@tkem

This comment has been minimized.

@tkem

This comment has been minimized.

@tatoosh

This comment has been minimized.

@Shadowghost
Copy link

So what about this? Any news or (further) implementation plans?
To explain my situation: I use (self-tagged) multiple artist tags mostly because of Kodi, which allows me to have all artists to be listed in the artist category, but the albums to be listed with the artists from album-artist tag if present. Since ID3v2.4 (and APEv2) multiple tags are an officially supported scheme.

@tkem tkem transferred this issue from mopidy/mopidy-local-sqlite Dec 9, 2019
@jodal jodal added the C-enhancement Category: A PR with an enhancement or an issue with an enhancement proposal label Dec 21, 2019
@fran-penedo
Copy link

I just updated to mopidy 3 and I swear I remember multiple artists working, but I can't find any reference to it being implemented, so I actually don't know why they used to work? In any case, I'd like to request this feature or at least start some discussion about it. I might be able to work on it myself if I can get a few pointers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: A PR with an enhancement or an issue with an enhancement proposal
Projects
None yet
Development

No branches or pull requests

5 participants