Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GStreamer client command from tutorial doesn't work #62

Open
2 tasks done
jkaniuka opened this issue Dec 20, 2024 · 5 comments
Open
2 tasks done

GStreamer client command from tutorial doesn't work #62

jkaniuka opened this issue Dec 20, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@jkaniuka
Copy link

jkaniuka commented Dec 20, 2024

Preliminary Checks

  • This issue is not a duplicate. Before opening a new issue, please search existing issues.
  • This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description

I was trying to use RTSP stream from ZED X Camera, but I encountered error following this manual: GStreamer - ZED RTSP Server.

Steps to Reproduce

  1. gst-zed-rtsp-launch zedsrc ! videoconvert ! 'video/x-raw, format=(string)I420' ! x264enc ! rtph264pay pt=96 name=pay0
  2. gst-launch-1.0 rtspsrc location=rtsp://127.0.0.1:8554/zed-stream latency=0 ! decodebin ! fpsdisplaysink

Expected Result

I expected RTSP stream to be displayed on the client side.

Actual Result

Error on client's side:

Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Pipeline is PREROLLED ...
Prerolled, waiting for progress to finish...
Progress: (connect) Connecting to rtsp://127.0.0.1:8554/zed-stream
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Progress: (request) Sending PLAY request
Redistribute latency...
Progress: (request) Sending PLAY request
Redistribute latency...
Progress: (request) Sent PLAY request
Redistribute latency...
Opening in BLOCKING MODE 
NvMMLiteOpen : Block : BlockType = 261 
NvMMLiteBlockCreate : Block : BlockType = 261 
WARNING: from element /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstCapsFilter:capsfilter0: not negotiated
Additional debug info:
../libs/gst/base/gstbasetransform.c(1431): gst_base_transform_reconfigure_unlocked (): /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstCapsFilter:capsfilter0:
not negotiated
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc0: Internal data stream error.
Additional debug info:
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc0:
streaming stopped, reason not-negotiated (-4)
Execution ended after 0:00:00.258948988
Setting pipeline to NULL ...
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not write to resource.
Additional debug info:
../gst/rtsp/gstrtspsrc.c(6607): gst_rtspsrc_try_send (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not send message. (Received end-of-file)
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not write to resource.
Additional debug info:
../gst/rtsp/gstrtspsrc.c(9034): gst_rtspsrc_pause (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not send message. (Received end-of-file)
Freeing pipeline ...

ZED Camera model

ZED

Environment

ZED Box Orin NX 16 GB with GMSL2
ZED SDK for JetPack 6.0 GA (L4T 36.3) 4.2 (Jetson Orin, CUDA 12.2)

Anything else?

No response

@jkaniuka jkaniuka added the bug Something isn't working label Dec 20, 2024
@Myzhar
Copy link
Member

Myzhar commented Dec 20, 2024

Hi @jkaniuka
Connecting to rtsp://:8554/zed-stream
did you set a value for ${SERVER_IP}?
You must use the IP of the camera that is streaming

@jkaniuka
Copy link
Author

@Myzhar Yes, I changed it to 127.0.0.1 😉

@jkaniuka
Copy link
Author

Hi @Myzhar, I've updated my issue. Now there's also an error on server's side 😞

@Myzhar
Copy link
Member

Myzhar commented Jan 13, 2025

Are you using Docker?
If that's the case then the warning
[ZED-X][Warning] Failed to connect to zed_x_daemon.
is expected and you can ignore it. The zed_x_daemon runs on the host side.

@jkaniuka
Copy link
Author

I realized that I had another stream running in the background and that probably caused [ZED-X][Warning] Failed to connect to zed_x_daemon. error. I checked once again and now there's only an error on client's side. I've updated the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants