<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Maximum latency handling broken everywhere" href="https://bugzilla.gnome.org/show_bug.cgi?id=744106#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Maximum latency handling broken everywhere" href="https://bugzilla.gnome.org/show_bug.cgi?id=744106">bug 744106</a> from <a href="page.cgi?id=describeuser.html&login=slomo%40coaxion.net" title="Sebastian Dröge (slomo) <slomo@coaxion.net>"> Sebastian Dröge (slomo)</a> <pre><wtay> slomo, yeah, I saw it. popcorn time <wtay> slomo, I think the only problem is that the default for basesrc should be 0,0 instead of 0,-1 <slomo> wtay: that might be one change, but how should overall be the expected behaviour? -1 meaning infinite maximum latency, meaning that usually elements just pass that through... unless they themselves have leaky queueing behaviour like audioringbuffer, in which case they would reset it to their queue size? also do you agree that all our queues should do something with the latency query somehow? :) <wtay> slomo, yes, -1 in infinity and stays that way unless you have a leaky queue that actually throws away things <wtay> slomo, queues should do something with the query. I think queue does (but only when time limits are set, bytes and buffer limits can't be taken into account) <slomo> they could be taken into account if upstream properly implements the convert query i guess :) <wtay> probably <slomo> ok, i think then it all makes sense now and needs some clarification in part-latency.txt :) i'll do that later and fix all the code that is currently doing weird things <slomo> thanks</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>