GST_IS_BIN failuer with gst-launch-1 ignoring messages.

General
, ,
1

Dear members,

In recent days, I have been trying to follow the Multi-stream - Multi-network tutorials in the URL: Hailo-Application-Code-Examples/runtime/gstreamer/multistream_multi_networks at main · hailo-ai/Hailo-Application-Code-Examples · GitHub

I tried to construct the pipeline with ‘ONE STREAM’ using ‘two different HEF models’ and I was able to construct my own pipeline as follows:

gst-launch-1.0 hailoroundrobin mode=1 name=fun ! tee name=t hailomuxer name=hmux1 hailomuxer name=hmux2 t. ! queue leaky=no max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! hmux1. t. ! videoconvert ! videoscale qos=false method=0 add-borders=false ! video/x-raw,format=RGB,width=640,height=480,pixel-aspect-ratio=1/1 ! queue leaky=no max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! hailonet device-count=1 vdevice-group-id=0 hef-path=…/resources/object_detection/yolov8s_h8l.hef is-active=true ! queue leaky=no max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! hailofilter so-path=/home/jskang/githubs/hailo-rpi5-examples/basic_pipelines/…/resources/libyolo_hailortpp_post.so function-name=yolov8s qos=false ! queue leaky=no max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! hmux1.t. ! videoconvert ! videoscale qos=false method=0 add-borders=false ! video/x-raw,format=RGB,width=640,height=480,pixel-aspect-ratio=1/1 ! queue leaky=no max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! hailonet device-count=1 vdevice-group-id=0 hef-path=…/resources/wider_face/yolov8s.hef is-active=true ! queue leaky=no max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! hailofilter so-path=/home/jskang/githubs/hailo-rpi5-examples/basic_pipelines/…/resources/libyolo_hailortpp_post.so function-name=yolov8s qos=false ! queue leaky=no max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! hmux2.hmux1. ! hmux2. hmux2. ! queue leaky=no max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! hailooverlay ! hailostreamrouter name=sid src_0::input-streams=“<sink_0>” compositor name=comp start-time-selection=0 sink_0::xpos=0 sink_0::ypos=0 ! queue name=hailo_video_q_0 leaky=no max-size-buffers=30 max-size-bytes=0 max-size-time=0 ! videoconvert ! queue name=hailo_display_q_0 leaky=no max-size-buffers=30 max-size-bytes=0 max-size-time=0 ! fpsdisplaysink video-sink=xvimagesink name=hailo_display sync=false text-overlay=false v4l2src device=/dev/video0 name=src_0 ! video/x-raw, width=640, height=480, framerate=30/1 ! queue name=queue_scale max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! videoscale n-threads=2 ! queue name=queue_src_convert max-size-buffers=3 max-size-bytes=0 max-size-time=0 ! videoconvert n-threads=3 name=src_convert qos=false ! video/x-raw, format=RGB, width=640, height=640, pixel-aspect-ratio=1/1 ! ${additional_parameters}

But, unfortunately, I’ve encountered an error as follows:
(Hailo Detection App:28802): GStreamer-CRITICAL **: 17:38:50.534: gst_element_link_pads_filtered: assertion ‘GST_IS_BIN (parent)’ failed
gst_parse_error: unexpected reference “gst-launch-1” - ignoring (0)
If there are any members who know the solution to these types of errors,

please help me as I am a beginner with Hailo-GStreamer.

Thank you for reading.

I hope happiness comes to you all.

JSKang

2

Hi @happistday,

You can check also this example as a base for your pipeline. Let me know if it helps.

4

Thank you for your comments.

I have reviewed the examples you recommended (URL1) and the cascading networks example (URL2).

The examples work as expected when I run them directly. However, when I try to modify them for my specific problem, both examples produce the same error.

I suspect that the error messages from ‘gst-launch-1’ are related to a version mismatch or a library path issue. Interestingly, the pipeline runs fine without the starting command, so it may not be a major problem.

The more pressing issue is the GST_IS_BIN error messages. I am unsure of the exact cause of these errors. It might be something I can resolve after further studying the GStreamer modules. Currently, I suspect the issue might be related to the data queue system, but I’m not certain.

If you have any other potential explanations, your insights would be incredibly helpful in resolving these issues.

If I find any other areas for improvement, I will share them in this thread.

Thank you for your attention.

JS Kang