Gst-stream-error-quark

Hello Hailo Community,
I have trained a custom model for the rpi5 and hailo8l and compiled with no problem. After that ı run the model with the example videos that hailo provided to see if the model is compiled correctly. Model runs with no problem with the example videos.
So I recored a video with usb cam with the rpi5 and run the model with rpi5 and hailo8l. I get this error. Can you help me?

Error: gst-stream-error-quark: Internal data stream error. (1), ../libs/gst/base/gstbasesrc.c(3132): gst_base_src_loop (): /GstPipeline:pipeline0/GstFileSrc:source:
streaming stopped, reason not-linked (-1)
Shutting down... Hit Ctrl-C again to force quit.

I don’t think the problem is caused by the model or hailo configurations. I think it is caused by the video fomats etc. İs there a documentation which gives which video formats or configurations that hailo8l can run. Am I only able to run my model with the rpi camera?

Hello @omria @Nadav Do you have a solution?

Hey @yurdakul21

The “not-linked” error you’re experiencing is related to GStreamer pipeline configuration rather than Hailo model issues. This typically happens when pipeline elements aren’t properly connected due to format incompatibilities.

Main Issues:

  • Video format/codec incompatibility
  • Incorrect GStreamer pipeline configuration
  • Potential USB camera format mismatches

Solutions:

  1. Verify video properties using ffprobe or gst-discoverer-1.0
  2. Test video playback with basic GStreamer pipeline
  3. Convert video to compatible format using ffmpeg
  4. Ensure proper pipeline setup for USB camera input
  5. Verify required GStreamer plugins are installed
  6. Try using v4l2src for direct camera capture
  7. Check Hailo documentation for supported formats
  8. Test with RPi camera to isolate the issue source

The issue likely stems from a mismatch between the video format or codec of your recorded video and the GStreamer pipeline expectations. By ensuring the video format is compatible and the GStreamer pipeline is correctly configured, you should be able to resolve the error. Let me know if you need further help!