You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the api calls to connect with MusicBrainz are added in order to embed the metadata in the output file, would it be reasonable to also allow MusicBrainz ids as inputs? It gets a bit strange with the release vs. release-group distinction, but other than that I think it would be a fairly straightforward addition.
Ooh, this is slick. I, for one, certainly think this will be nice to have. I haven't looked into their API, but I think standardizing the URI might be a bit tricky.
If you feel you want to take this on, please, you're very much welcome to.
Somewhat related to #81
If the api calls to connect with MusicBrainz are added in order to embed the metadata in the output file, would it be reasonable to also allow MusicBrainz ids as inputs? It gets a bit strange with the release vs. release-group distinction, but other than that I think it would be a fairly straightforward addition.
URL example: https://musicbrainz.org/release-group/082c6aff-a7cc-36e0-a960-35a578ecd937
Short URL example: mb:release-group:db92a151-1ac2-438b-bc43-b82e149ddd50
I have spare time and would be happy to help if this is a reasonable ask.
The text was updated successfully, but these errors were encountered: