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
In addition to handling live sources, we should probably also be checking if the current source i seekable and using this in core and exposing it to frontends. Step one should simply be to start emitting this info with the stream changed events.
The text was updated successfully, but these errors were encountered:
Following code is probably what we want to use to solve both this issue and #859
In [30]: q = gst.query_new_buffering(gst.FORMAT_TIME)
In [31]: src.query(q)
Out[31]: True
In [32]: q.parse_buffering_stats()
Out[32]: (<enum GST_BUFFERING_STREAM of type GstBufferingMode>, -1, -1, 0L)
jodal
modified the milestones:
v0.20 - Audio cleanup part 1,
v0.21 - Audio cleanup part 2Nov 7, 2014
adamcik
added a commit
to adamcik/mopidy
that referenced
this issue
Mar 12, 2015
Return type of scanner changed to a named tuple with (uri, tags, duration,
seekable). This should help with mopidy#872 and the related "live" issues.
Tests, local scan and stream metadata lookup have been updated to account for
the changes.
jodal
removed this from the
x1 - Audio cleanup milestone
Oct 29, 2023
In addition to handling live sources, we should probably also be checking if the current source i seekable and using this in core and exposing it to frontends. Step one should simply be to start emitting this info with the stream changed events.
The text was updated successfully, but these errors were encountered: