GNOME Bugzilla – Bug 677263
input-selector: playback freezes under some conditions
Last modified: 2012-06-01 18:14:45 UTC
Created attachment 215401 [details] test case to reproduce freeze With recent changes to input-selector (cf. #676739) playback freezes some seconds after a finished seek if ... ... pads are always-ok=TRUE ... input-selector has sync-streams=TRUE ... a multiqueue with buffer is involved (use-buffering=TRUE) The attached test-prog can be used to reproduce the issue with e.g.: ./is "input-selector sync-streams=true name=sel ! audioconvert ! audio/x-raw-int,width=16 ! audioresample ! alsasink uridecodebin uri=file:/mnt/ltmp/vid/sintel_cropped_multilingual.webm use-buffering=true name=bin ! xvimagesink bin. bin.src1 ! sel. bin.src2 ! sel. bin.src3 ! sel." No problems though without "use-buffering=true" Problems disappears when reverting following commit: commit cd798a0a527bb365934392e3be7a8cf526e7f1ac Author: Andre Moreira Magalhaes (andrunko) <andre.magalhaes@collabora.co.uk> Date: Mon May 28 14:29:00 2012 -0300 inputselector: Properly sync when changing streams This adds properties to use the clock time for deciding when to drop buffers for inactive pads and a property to buffer all not rendered buffers for the active pad to allow pad switching without losing any buffers at all.
And no problems with always-ok=FALSE too.
commit 2424d9896cd6a473638a718ace54e5b8cf89f021 Author: Andre Moreira Magalhaes (andrunko) <andre.magalhaes@collabora.co.uk> Date: Fri Jun 1 16:34:16 2012 +0200 inputselector: Correctly get current running time when syncing to the segment information Fixes bug #677263.
I tested all, that got stuck before: play well now under same conditions with this commit! Thanks!