Closed nanosonde closed 2 years ago
Hello, it's the publisher responsibility to fill sprop-parameter-sets. If it's empty, it means that ffmpeg didn't fill it.
Unfortunately it's quite common to deal with H264 tracks that have an empty sprop-parameter-sets (see #787 #715) for various reasons - it may be caused be a defective software/firmware or by choice since parameters may change during time.
In the near future the server will fill sprop-parameter-sets according to the last received SPS and PPS, but anyway, your client (RTSP2WEBRTC) should be edited to get SPS and PPS from the H264 NALUs, not from sprop-parameters-set.
I can confirm that your command line makes ffmpeg send to the server an SDP without sprop-parameters-set:
v=0
o=- 0 0 IN IP4 127.0.0.1
s=No Name
c=IN IP4 127.0.0.1
t=0 0
a=tool:libavformat 58.76.100
m=video 0 RTP/AVP 96
b=AS:600
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1
a=control:streamid=0
Thanks for the explanation.
I have added "-flags +global_header
" as output option and now the SDP contains the sprop-parameter-sets
.
However, I had to remove the option "-tune zerolatency
" to get a proper video. With the mentioned option approx,. 2/3 of the video frame was distorted.
Now it works with both VLC and RTSP2WebRTC.
This issue is being locked automatically because it has been closed for more than 6 months. Please open a new issue in case you encounter a similar problem.
Which version are you using?
v0.17.17
Which operating system are you using?
Describe the issue
SDP parameter "sprop-parameter-sets=" is empty.
Describe how to replicate the issue
Convert an MJPEG IP cam stream to RTSP with H264. Run ffmpeg to connect to this server:
VLC is able to stream via the provided RTSP URL. Home assisstant however with the RTSP2WEBRTC addon is not able to cope with this reply.
Did you attach the server logs?
Nothing special from the server. No error message.
Did you attach a network dump?
Wireshark with RTSP filter: