GNOME Bugzilla – Bug 354594
multifdsink doesn't work reliably with sync-method = 'next-keyframe'
Last modified: 2006-09-08 10:41:16 UTC
If you use multifdsink with sync-method set to 'next-keyframe', a race condition causes the clients attached to multifdsink to (usually) never start, or sometimes start after a very long time, etc. If two buffers (e.g. a keyframe and a non-kf) are added to the queue in quick succession, then the new-client check would only check the second of these, not see the keyframe, so not start the client. Patch forthcoming. In latest-keyframe mode, if there was no latest-keyframe in the queue (yet), we switch to next-keyframe mode, so see the same behaviour.
Created attachment 72303 [details] [review] Fix next-keyframe sync-method
Setting to blocker, this fixes important things for flumotion.
Created attachment 72305 [details] [review] Test for this This test passes with the patch applied. I haven't tested it without the patch; it may pass anyway since it would only fail intermittently due to a race condition, previously.
Zaheer confirms for me that this test fails (times out) without the multifdsink patch applies.
commited, thanks
Closing, thomas committed the fix.