-
Notifications
You must be signed in to change notification settings - Fork 1
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
Chromium spotify track metadata mixed with previous track metadata #11
Comments
Thanks for the details. I recently updated my spotify native app to a new version and realized that the pattern of dbus messages had changed between versions, however the difference wasn't quite as drastic as it seems to be between native and web/chromium.
Yes, striputary can't handle this at all currently, but I think it should be possible in principle. What I don't know is what the expected behavior should be. I guess it would be best to disregard the the current song entirely (which was interrupted halfway through?) and to remember the timestamp of the next step? |
I think a possible solution might be to:
I think the expected behaviour would indeed be to disregard the song if it's skipped In any case, I'm really happy that you keep this project alive :) |
This sounds like a reasonable fix. I'll try to implement this in the coming weeks and will let you know. I'll have to try to replicate the behavior you see first, so I hope chromium behaves the same on my machine.
Of course, thank you :) |
When a track finishes playing and goes to the next track, the metadata of the track printed to the console log and saved in the yaml file is incorrect, and often intermixed with the metadata from the previous song. This is with https://open.spotify.com in chromium. I suspect that that might be the issue: the nateive Spotify application probably sends events differently to DBUS than the web app. I'm unable to run the native application, so I can't say this for certain, but I have a strong suspicion.
When I monitor the D-Bus events with dbus-monitor, I see that there are multiple events to announce the metadata of the track playing, each one with one more field filled in compared to the previous one. In the trace below, the player was at the end of "Uncle Brian's Abattoir" by "Trampolene, Peter Doherty"; the next song it started playing is "Fight On" by "The Lathums".
(Kind of related; the behaviour of the application is a bit wonky when I go to the next song by pressing the 'next' button while a song is playing, but I don't really expect striputary to handle this and don't know if this is also caused by the multiple events per song change)
The text was updated successfully, but these errors were encountered: