Replies: 2 comments
-
Alternatives:
Above solutions dont work retrospectively though. Built-in Statistics / analyticsHaveing listening statistics and analytics built into navidrome would be great, but I don't think navidrome retains detailed playback statistics to support this. And Maloja exists and is pretty much tailormade for this usecase. |
Beta Was this translation helpful? Give feedback.
-
Thank you for the suggestion for maloja, I think this works perfectly for my use being self-hosted datawise, while still integrating very cleanly in to Navidrome :) I agree that a built-in statistics page would be nice, but definitely there are more important issues at hand to resolve. Thank you again for the ideas! 👍 |
Beta Was this translation helpful? Give feedback.
-
I would like to poll my Navidrome server scrobble data from the last year, to then use it to generate my own "Year in Review" (similar to Spotify Wrapped or other such services).
Not entirely sure what the best approach to this is. Going off of "# of Plays" within the webUI isn't that nice because that includes all sorts of music I may not have even played in the last year...
Are scrobbles stored with exact timestamp inside the database? Or is the play count simply incremented on the specific track ID?
I am thinking that if individual scrobbles data is stored, I can poll each track associated with the scrobble, get it's ID Tags and playcount within the last year, then put that all in a CSV esque format for further processing.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions