How to start test video with Gstreamer on user mode Yocto Operating System

Technical Support
, ,
1

verdin-imx8mp-15034062:~$ gst-launch-1.0 videotestsrc ! videoconvert ! autovideosink
Setting pipeline to PAUSED …
Pipeline is PREROLLING …

(gst-launch-1.0:713): GStreamer-CRITICAL **: 08:10:32.006: gst_buffer_pool_config_set_allocator: assertion ‘allocator != NULL || params != NULL’ failed

(gst-launch-1.0:713): GStreamer-CRITICAL **: 08:10:32.012: gst_buffer_pool_config_set_allocator: assertion ‘allocator != NULL || params != NULL’ failed

(gst-launch-1.0:713): GStreamer-CRITICAL **: 08:10:32.012: gst_object_unref: assertion ‘object != NULL’ failed

(gst-launch-1.0:713): GStreamer-Allocators-CRITICAL **: 08:10:32.012: gst_dmabuf_memory_get_fd: assertion ‘gst_is_dmabuf_memory (mem)’ failed
error marshalling arguments for add: dup failed: Bad file descriptor
Error marshalling request: Bad file descriptor
Pipeline is PREROLLED …
Setting pipeline to PLAYING …
Redistribute latency…
New clock: GstSystemClock
^Chandling interrupt.
Interrupt: Stopping pipeline …
Execution ended after 0:00:03.401037078
Setting pipeline to NULL …

2

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello! It looks like you’re encountering some issues with your GStreamer pipeline on the Verdin iMX8M Plus module. Let’s go through some steps to help you troubleshoot and resolve these errors:

  1. Verify Plugins: Ensure all necessary GStreamer plugins are installed. Use gst-inspect-1.0 to check for videotestsrc, videoconvert, and autovideosink. Missing plugins can lead to critical errors.

  2. Utilize Hardware Acceleration: The Verdin iMX8M Plus supports hardware acceleration, which is beneficial for video tasks. Check for plugins that leverage this, such as those with ‘imx’ or ‘vpu’ in their names, using gst-inspect-1.0.

  3. Check Pipeline Configuration: Double-check your pipeline setup to ensure elements are correctly linked and compatible. Use gst-inspect-1.0 to verify the capabilities of each element.

  4. Increase Debugging Level: Set GST_DEBUG=3 to get more detailed error messages, which can help identify the issue.

  5. File Descriptor Limits: The file descriptor error might indicate a system resource issue. Check your limits with ulimit -n and increase them if needed.

  6. Try Different Video Sinks: If autovideosink is problematic, try alternatives like xvimagesink or waylandsink to see if the issue persists.

By following these steps, you should be able to identify and resolve the issues with your GStreamer pipeline. If the problem continues, consider testing with a simpler pipeline to further isolate the issue.

Best regards, Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

https://community.nxp.com/t5/i-MX-Processors/videotestsrc-with-yocto/td-p/226564

First Steps with CSI Camera Set 5MP AR0521 Color (Linux).

3

Hello Abdullah,

I assume you are trying to test a Gstreamer pipeline using one Image built using Yocto. Are you using a custom image, or one of our reference images, such as the Reference Multimedia Image?

Besides, are you using a camera to capture video? In this case, you might want to check our article about Gstreamer. It contains some pipeline examples that you might want to use to test video streaming.

If you are not using any camera and want to test the video output, you can try to use the following Gstreamer pipeline:

gst-launch-1.0 videotestsrc ! waylandsink

It will generate a test video pattern to validate if you are getting a video output on your monitor/display.

Best Regards,

Marcio