-
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
Access MusicBrainz series (releases, release groups, recordings) #1273
Comments
Interesting. Shall we make a list of useful information to pull from the series?
|
This would be a great addition! Here's an example of some pain that would be alleviated by support for series :) http://musicbrainz.org/edit/31856400 |
Hi I just tried to find out what is necessary to achieve this functionality. But I had no success getting series information from the MB API. I have put some questions here: If you can help me, I will help you :D |
You might be better asking in the MusicBrainz IRC channel (#musicbrainz on freenode.net) 😄. |
Good point! You'll hear from me if I had success |
Any thoughts how this might work? I guess one approach is have some configuration where the user can list MBIDs of series they want to have grouped. Each MBID can also optionally have a flag indicating that all the recordings should be in one directory (often each release just contains a single recording, e.g. a podcast and you wouldn't want them to be in separate directories), possibly also overriding the album tag with the series name. In the rare case a release belongs to more than one series that is listed in the config, throw an error? |
See https://musicbrainz.org/doc/Series
It would be great if beets could pull series information so you could sort e.g. podcasts like https://musicbrainz.org/series/f158ad31-bc44-4b22-94a4-025a8d6375cf into their own folder, using the ordering number in the filename, also releases/release groups that are part of a series could be sorted into some folder structure using the series or something. Either way, it would great to at least have the information handy. ;)
One caveat:
The text was updated successfully, but these errors were encountered: