"GST_MESSAGE_WARNING: Pipeline construction is invalid, please add queues"

[Ben Rush]

Why would I get that for the following pipeline? 

rtspsrc location=rtsp://<myip>:8554/<streamName> drop-on-latency=true ! decodebin ! mfxvpp ! video/x-raw(memory:MFXSurface),format=BGRA,width=256,height=192 ! queue leaky=1 max-size-buffers = 0 ! appsink name = sink

There is a queue in the pipeline. 

It's also worth noting I need this to be as real-time as possible. I'd rather not have a lengthy queue. 

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

[David Ing]

A queue is not just a queue, it is also a thread boundary.  Some elements require separation across a thread boundary (especially after elements with multiple src pads ... you want a queue after each src).

You can probably experiment with placing queues in various locations until it works.

On Fri, Sep 6, 2019, 8:25 PM Ben Rush <[hidden email]> wrote:

Why would I get that for the following pipeline? 

rtspsrc location=rtsp://<myip>:8554/<streamName> drop-on-latency=true ! decodebin ! mfxvpp ! video/x-raw(memory:MFXSurface),format=BGRA,width=256,height=192 ! queue leaky=1 max-size-buffers = 0 ! appsink name = sink

There is a queue in the pipeline. 

It's also worth noting I need this to be as real-time as possible. I'd rather not have a lengthy queue. 

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

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

[Ben Rush]

I see. With your description, I found this, and it clears things up. Again, thanks for your continual help David. 

https://gstreamer.freedesktop.org/documentation/application-development/advanced/threads.html?gi-language=c  

On Fri, Sep 6, 2019 at 11:14 PM David Ing <[hidden email]> wrote:

A queue is not just a queue, it is also a thread boundary.  Some elements require separation across a thread boundary (especially after elements with multiple src pads ... you want a queue after each src).

You can probably experiment with placing queues in various locations until it works.

On Fri, Sep 6, 2019, 8:25 PM Ben Rush <[hidden email]> wrote:

Why would I get that for the following pipeline? 

rtspsrc location=rtsp://<myip>:8554/<streamName> drop-on-latency=true ! decodebin ! mfxvpp ! video/x-raw(memory:MFXSurface),format=BGRA,width=256,height=192 ! queue leaky=1 max-size-buffers = 0 ! appsink name = sink

There is a queue in the pipeline. 

It's also worth noting I need this to be as real-time as possible. I'd rather not have a lengthy queue. 

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

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

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

[Nicolas Dufresne-5]

Le vendredi 06 septembre 2019 à 22:24 -0500, Ben Rush a écrit :
> Why would I get that for the following pipeline?
>
>
> rtspsrc location=rtsp://<myip>:8554/<streamName> drop-on-latency=true ! decodebin ! mfxvpp ! video/x-raw(memory:MFXSurface),format=BGRA,width=256,height=192 ! queue leaky=1 max-size-buffers = 0 ! appsink name = sink

That warning on the Bus are in two parts. See the "debug" out parameter
for gst_message_parse_warning(). In the second part, it sais that there
is isn't enough queuing in the pipeline to accommodate a relatively new
basesink mechanism called "processing-deadline". This new configuration
gives room for element processing time in the synchronisation process,
without scarifying the the synchronisation between multiple sink
elements like it use to do.

To be fair, that seems like a bug, since leaky queues are suppose to
the set the max latency to -1 (infinite). Let me CC OLivier who
introduced this warning in the first place.

>
> There is a queue in the pipeline.
>
> It's also worth noting I need this to be as real-time as possible. I'd rather not have a lengthy queue.
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel


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