GNOME Bugzilla – Bug 704927
queue2: forward the upstream scheduling flags
Last modified: 2013-08-27 11:44:06 UTC
Created attachment 250197 [details] [review] proposed patch Current muxers can't know that they should avoid seeks if possible when queue2 is used as it only indicates the _SEEKABLE scheduling flag. By letting queue2 by default forwards the upstream, and add _SEEKABLE if required we can ensure information about _SEQUENTIAL and _BANDWIDTH_LIMITED also reaches the demuxer so they can act on them. Proposed patch attached. One thing i'm not entirely sure about is whether _SEEKABLE should be masked if we're not using a tmpfile (I would assume not, but worth another look i guess)
Comment on attachment 250197 [details] [review] proposed patch Why should SEEKABLE be masked? queue2 does passthrough of seeks if necessary
commit 7f8fb3861ed15c6b858f1ec81f980944514722db Author: Sjoerd Simons <sjoerd.simons@collabora.co.uk> Date: Fri Jul 26 15:08:13 2013 +0200 queue2: Forward the schedule query upstream When asked about the scheduling flags first check with upstream and simply add the _SEEKABLE flag when using a temporary file as storage. This enables the forwarding of _SEQUENTIAL and _BANDWIDTH_LIMITED from sources if needed. https://bugzilla.gnome.org/show_bug.cgi?id=704927