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
Postpone set metadata until track is ready #1357
Comments
Idea fix IMO would be to deprecate the |
Assigning to @adamcik as he has a working patch that just needs sanity checking for concurrency issues. |
Is there a Fix for this issue ? |
I haven't completed this yet. We prioritized getting 2.0 out instead of blocking on something which wasn't a regression. |
When using mopidy and mopidy-spotify with git master, I'm having the same problem as Leicas when manually trying to apply my old patch to the new actor.py. I want to use the latest code for numerous good reasons (GST 1.0, many many great bugfixes), but I can't really use it without good support for tags. Count me among the users waiting for this to land / willing to test any WIP code that will fix this...! I think it's probably because set_metadata isn't being called once per track change. And I can't keep a reference to the latest track with set_uri (which I guess is being called when the track changes) because set_uri doesn't create or receive a track object. Just mucking around in the code like a n00b but not seeing any obvious workaround right now. Looks like gapless has buried the place where this needs to be set. |
Yes. |
What is the right way to set metadata once you add a uri to the tracklist? How can I specify a track name before playing? |
Doing a set metadata inside change track isn't "safe". We need to postpone this until the track is ready. Without this appsrc based backends never propagate metadata to sinks.
The text was updated successfully, but these errors were encountered: