Should sync=false, async=false be set in case of live sources ?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Should sync=false, async=false be set in case of live sources ?

Manoj

Hi,

Searched a lot on web but still have confusion regarding 'sync=false, async=false' in case of live and non-live sources.

If i am not wrong, when using NON-LIVE sources like filesrc, GstBaseSink will synchronise on the clock and hence we need to have 'sync=true' (if not specified it is default set to true)
And hence all the clock waiting/dropping will be handled in GstBaseSink during rendering as mentioned at,
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-libs/html/GstBaseSink.html#GstBaseSink--sync


However, when using LIVE sources like udpsrc, source element will become the clock provider. If demuxer in pipeline, it will become the clock provider and hence take care to output the demuxed buffers as per their timestamps.

So confusion is, should we explicitly set 'sync=FALSE async=FALSE' in this case ? To avoid double timestamp checking in GstBaseSink ?


Please suggest if any gstreamer link explains/mentions about this.


Apologies if it's too basic and thanks a lot in advance,



Reply | Threaded
Open this post in threaded view
|

Re: Should sync=false, async=false be set in case of live sources ?

Manoj

Hi,

Need experts inputs on this to clear the confusion?

Thanks a lot,
Reply | Threaded
Open this post in threaded view
|

Re: Should sync=false, async=false be set in case of live sources ?

Wim Taymans
In reply to this post by Manoj
On 09/10/2012 06:40 PM, Manoj wrote:

> Hi,
>
> Searched a lot on web but still have confusion regarding 'sync=false,
> async=false' in case of live and non-live sources.
>
> If i am not wrong, when using NON-LIVE sources like filesrc, GstBaseSink
> will synchronise on the clock and hence we need to have 'sync=true' (if not
> specified it is default set to true)
> And hence all the clock waiting/dropping will be handled in GstBaseSink
> during rendering as mentioned at,
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-libs/html/GstBaseSink.html#GstBaseSink--sync
>
>
> However, when using LIVE sources like udpsrc, source element will become the
> clock provider. If demuxer in pipeline, it will become the clock provider
> and hence take care to output the demuxed buffers as per their timestamps.
>
> So confusion is, should we explicitly set 'sync=FALSE async=FALSE' in this
> case ? To avoid double timestamp checking in GstBaseSink ?
No, you should not change these properties.

Wim

>
>
> Please suggest if any gstreamer link explains/mentions about this.
>
>
> Apologies if it's too basic and thanks a lot in advance,
>
>
>
>
>
>
>
> --
> View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Should-sync-false-async-false-be-set-in-case-of-live-sources-tp4656241.html
> Sent from the GStreamer-devel mailing list archive at Nabble.com.
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel