Sps/pps not being passed by atomcams h264 1080p stream, causes SDP video fmtp to not be populated #461
baudneo
started this conversation in
Development
Replies: 1 comment
-
Found the v4lrtspserver init script -> https://github.com/gtxaspec/wz_mini_hacks/blob/master/SD_ROOT/wz_mini/etc/network.d/S15v4l2rtspserver |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have started 2 issues about this on this repo and 1 more on atomcams and v4lrtspserver each.
The answer I got from the v4lrtspserver maintainer is that the video stream for 1080p is not passing SPS/PPS. This causes the main 1080p stream to not have a profile-level-id.
This in turn causes janus webrtc gateway to error out. As it requires a profile-level-id to parse codec requirements.
VLC and other rtsp players can parse the stream without an explicit profile-level-id. I do not know if it is strictly required but for the case of janus webrtc gateway, it is.
The v4lrtspserver maintainer has asked me to look into v4lrtspserver debug logs but I can't seem to locate where v4lrtspserver command is called from to edit the arguments.
Can anyone point me towards where that is?
Example of mainstream RTSP DESCRIBE response
The part that causes the error is on the video media definitions
That is the whole video media block, the
a=fmtp:96
is the line where profile-level-id sprop, and packetization attributes should be.The substream is parsed correctly and has the needed attributes but the 1080p mainstream does not. This is technically a broken rtsp implementation according to the janus webrtc gateway maintainers.
Beta Was this translation helpful? Give feedback.
All reactions