GNOME Bugzilla – Bug 786056
queue/queue2:: Allow re-usability after EOS
Last modified: 2017-08-11 08:15:51 UTC
See patch message
Created attachment 357272 [details] [review] queue2: Allow re-usability after EOS After EOS, it is possible for a pad to be resetted by sending either a STREAM_START or SEGMENT event Mimic the same behaviour when receiving STREAM_START/SEGMENT events in queue2 if we are EOS'd
Comment on attachment 357272 [details] [review] queue2: Allow re-usability after EOS Looks good to me, but queue/multiqueue might need the same
commit 6566eff20d250c6253af8dfc9b603c8d0850e257 Author: Edward Hervey <edward@centricular.com> Date: Wed Aug 9 16:15:23 2017 +0200 queue2: Allow re-usability after EOS After EOS, it is possible for a pad to be resetted by sending either a STREAM_START or SEGMENT event Mimic the same behaviour when receiving STREAM_START/SEGMENT events in queue2 if we are EOS'd https://bugzilla.gnome.org/show_bug.cgi?id=786056 Indeed, queue also needs to be adjusted accordingly. multiqueue seems ok though.
Patch is also in 1.12 now, queue patch should too
commit 36372a9f4c515b93011ff78d898f63b2352cc9db (HEAD -> master, origin/master, origin/HEAD) Author: Sebastian Dröge <sebastian@centricular.com> Date: Fri Aug 11 11:12:09 2017 +0300 queue: Allow re-usability after EOS After EOS, it is possible for a pad to be resetted by sending either a STREAM_START or SEGMENT event Mimic the same behaviour when receiving STREAM_START/SEGMENT events in queue if we are EOS'd https://bugzilla.gnome.org/show_bug.cgi?id=786056