GST_QUERY_POSITION on a GstBin

[mafaneh]

Hi All,

I noticed that when querying the position of a pipeline, GstBin is looking for the maximum position reported by the elements within that bin. What is the reasoning behind that?

In a custom pipeline that I have running (with a couple of appsinks and a video renderer acting as sinks), the appsinks were reporting a position in response to the query. The correct position was reported by the video renderer but since it was less than the position reported by the appsinks it was masked (this was after some trick modes were performed). I guess I could query the video renderer element directly for its position but I was just trying to understand the reasoning behind reporting the max position.

Thanks,

Mohammad

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

[Martin.cheng]

why dont you query the top pipeline position?

I was doing that. it worked fine.

On Tue, Jan 3, 2012 at 10:41 PM, Mohammad Afaneh <[hidden email]> wrote:

Hi All,

I noticed that when querying the position of a pipeline, GstBin is looking for the maximum position reported by the elements within that bin. What is the reasoning behind that?

In a custom pipeline that I have running (with a couple of appsinks and a video renderer acting as sinks), the appsinks were reporting a position in response to the query. The correct position was reported by the video renderer but since it was less than the position reported by the appsinks it was masked (this was after some trick modes were performed). I guess I could query the video renderer element directly for its position but I was just trying to understand the reasoning behind reporting the max position.

Thanks,

Mohammad

_______________________________________________
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

[mafaneh]

That is essentially what I was doing, but in some cases (which it may be related to something wrong I might be doing) I would get the position query handled by the appsinks in the pipeline and providing a different value that what it should be. 

I will have to look into and see why the appsinks are reporting different values that my video renderer. But my question really was: why does GstBin choose the maximum position and decides to report that as the current position?

Thanks,

Mohammad

On Fri, Jan 6, 2012 at 5:09 AM, Mo Cheng <[hidden email]> wrote:

why dont you query the top pipeline position?

I was doing that. it worked fine.

On Tue, Jan 3, 2012 at 10:41 PM, Mohammad Afaneh <[hidden email]> wrote:

Hi All,

I noticed that when querying the position of a pipeline, GstBin is looking for the maximum position reported by the elements within that bin. What is the reasoning behind that?

In a custom pipeline that I have running (with a couple of appsinks and a video renderer acting as sinks), the appsinks were reporting a position in response to the query. The correct position was reported by the video renderer but since it was less than the position reported by the appsinks it was masked (this was after some trick modes were performed). I guess I could query the video renderer element directly for its position but I was just trying to understand the reasoning behind reporting the max position.

Thanks,

Mohammad

_______________________________________________
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

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