Open Mrman1093 opened 2 years ago
Just want to add that there's already a self-hosted option for music tracking https://listenbrainz.org/ https://github.com/metabrainz/listenbrainz-server
Still it would be nice to have something to track new releases and maybe even concerts.
As far as I can tell, listenbrainz is for scrobbling, not for keeping track of albums you've listened to and rated.
One alternative is https://critiquebrainz.org/ , but as far as I could tell it is not self-hostable. https://github.com/krateng/maloja is self-hostable, but it is also for scrobbling.
@bonukai I am interested in working on this issue. Would you be interested in me looking into this and raising a PR? Is there anything I need to know? I was thinking of using musicbrainz's API/database for this.
MusicBrainz API has global limit of requests (300 requests per second), so I would encourage you to explore other providers.
What features would you like to have? This will dictate the structure and complexity of this update. If, for example you would only be able to search, and mark as seen, add to watchlist albums, without individual songs, this would be very straight forward. But more complex features would require larger changes to the database and the application, and I am not willing to work on this.
I am currently rewriting entire project, I will try to publish new branch this week, we could work on this feature on the new branch.
My wanted features are pretty much the ones you've cited. It's essentially an audiobook by another name.
I wish I had seen this message before attempting my PR, I'm almost done with everything except for the unit tests. Not sure how to proceed now. I can clean everything up and open a draft PR so you take a look at it if you want, but I understand if the rewrite is higher-priority conflict-wise.
As for the request limits, that was definitely on my mind. I am not sure what the ideal solution is, I don't think I'll be able to find a better datasource.
Anyway, thanks a lot for your help. This is a cool project. I've humbly opened my draft PR. I'll look into provider alternatives, and re-apply my changes after the rewrite. I'm hoping this gives you an idea of what I had in mind and how it could be implemented.
I apologise for the delay, but now I have published wip branch, with the new version, still work in progress
No problem! I'll wait for the rewrite to be finished and then I'll re-do all of my changes and open a proper pull request. Thanks!
Small update regarding which datasource to use: lidarr uses MusicBrainz data without any issue, and I am not sure how that works. Does it use a separately hosted database based on MusicBrainz, meaning they can have their cake and eat it too (get the data without the rate limiting?) - I need to look more into this. If I can't find a better datasource than MusicBrainz, perhaps it is feasible/good to ask the user to point to their own MusicBrainz database before they can use the music feature? Again, I need to look into all of this into more detail, just an idea I want to write down so I don't forget.
It would be nice if this could track music using one or more of the various music apis out there (MusicBrainz, Discogs, Deezer, etc.) If this does get added, I would like the option to follow artists to see new releases as well as the ability to save artists for later listening.