questions upon the "unlock" and "unlock_stop" interfaces in GstBaseSrc class

[Sebastian Dröge]

On Tue, 2017-04-18 at 02:37 -0700, caoxi wrote:
> Thanks for your reply Sebastian. Like you said, element will be shut
> down after calling "unlock" function, does it mean the pipeline is
> paused(or ceased streaming and pipeline is exited)? If it does, how
> could "unlock_stop" resume the normal operations?

unlock() is only supposed to unlock/unblock the streaming thread,
nothing else. After unlock_stop() it should be possible to call
create()/fill() again.

Take a look at existing GstBaseSrc elements that implement those
functions. Generally they just cancel a synchronous IO function call
there, e.g. a read() from some socket.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1000 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20170418/65429bf4/attachment.sig>