Pad Probe Callbacks

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

Pad Probe Callbacks

DeepakRohan
Hi,
        I have a simple clarification regarding the probe callback.
Say that probe is added on the audio input-selector src pad with GST_PAD_PROBE_TYPE_IDLE.
So when the ProbeCallback happens, will the entire pipeline be blocked that is to say that there would not be any data flow either in the Audio part of the pipeline as well no data flow in the video part of the pipeline also.
Or it is just the audio pipeline getting blocked and video part continues.

As far as I have understood it should stop the data flow in the entire pipeline. As blocking only audio part of the pipeline may cause the video synchronization issues with audio.

Please correct me if I am wrong.

Thank You In Advance.
Reply | Threaded
Open this post in threaded view
|

Re: Pad Probe Callbacks

Sebastian Dröge-3
On Sun, 2016-09-25 at 22:20 -0700, DeepakRohan wrote:

> Hi,
>         I have a simple clarification regarding the probe callback.
> Say that probe is added on the audio input-selector src pad with
> GST_PAD_PROBE_TYPE_IDLE.
> So when the ProbeCallback happens, will the entire pipeline be blocked that
> is to say that there would not be any data flow either in the Audio part of
> the pipeline as well no data flow in the video part of the pipeline also.
> Or it is just the audio pipeline getting blocked and video part continues.
>
> As far as I have understood it should stop the data flow in the entire
> pipeline. As blocking only audio part of the pipeline may cause the video
> synchronization issues with audio.
>
> Please correct me if I am wrong.
It only blocks data flow at that specific pad. Which might as a result
also block other parts of the pipeline if they are handled by the same
thread.

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

signature.asc (949 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Pad Probe Callbacks

DeepakRohan
Sebastian Dröge-3 wrote
On Sun, 2016-09-25 at 22:20 -0700, DeepakRohan wrote:
> Hi,
>         I have a simple clarification regarding the probe callback.
> Say that probe is added on the audio input-selector src pad with
> GST_PAD_PROBE_TYPE_IDLE.
> So when the ProbeCallback happens, will the entire pipeline be blocked that
> is to say that there would not be any data flow either in the Audio part of
> the pipeline as well no data flow in the video part of the pipeline also.
> Or it is just the audio pipeline getting blocked and video part continues.
>
> As far as I have understood it should stop the data flow in the entire
> pipeline. As blocking only audio part of the pipeline may cause the video
> synchronization issues with audio.
>
> Please correct me if I am wrong.

It only blocks data flow at that specific pad. Which might as a result
also block other parts of the pipeline if they are handled by the same
thread.

Thanks for the quick reply Sebastian.
So theoretically, it should block the data flow only on the pad on which the probe was installed.
But what and how can it result in the blocking of the other parts of the pipeline. Can you please share some info on this regarding "Which might as a result also block other parts of the pipeline if they are handled by the same thread."

Thank You.

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel


signature.asc (949 bytes) <http://gstreamer-devel.966125.n4.nabble.com/attachment/4679773/0/signature.asc>