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
Hi, since you'd be coding this feature from scratch, for the database key, can you try to use something like acoustid_id field if present, with the filepath as a fallback? That way, if a user finds out they need to modify some metadata or rename the files, they can do it without losing track of their tracks.
I bet a lot of people running gonic already use some form of beets/picard or similar and have musicbrainz tags in their files.
it wouldn't be from scratch, just remodelling the schema to key by track,user instead of album,user
acoustid or maybe mb recordingid is interesting though. I'll consider that
for my personal usecase it's not as important since my source of truth for playcounts is lastfm which are synced to my beets database (beets can also generate smart playlists that gonic can parse and serve)
I do that too (beet lastimport) but I supposed it'd be way out of scope of gonic to parse beets database directly, hence my suggestion.
I like your workflow suggestion though. I could rely on beets smart playlists instead of symfonium's, since all I'm doing is maintaining offline downloads using them.
No description provided.
The text was updated successfully, but these errors were encountered: