--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/8c8321db-2c88-4390-b209-d0385d634b55n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/018beff3-57b5-4a97-9ca6-cfed21a80082n%40googlegroups.com.
0:01:00.050848151 20737 0x707092f0 WARN rtph264depay gstrtph264depay.c:899:gst_rtp_h264_depay_handle_nal: SPS
0:01:00.051000703 20737 0x707092f0 WARN rtph264depay gstrtph264depay.c:903:gst_rtp_h264_depay_handle_nal: PPS
0:01:00.131786525 20737 0x27afb50 INFO webrtcbin gstwebrtcbin.c:5596:on_rtpbin_ssrc_active:<webrtcbin> session 0 ssrc 1 active
0:01:00.333446184 20737 0x27afb50 INFO webrtcbin gstwebrtcbin.c:5596:on_rtpbin_ssrc_active:<webrtcbin> session 0 ssrc 1 active
0:01:00.533416996 20737 0x27afb50 INFO webrtcbin gstwebrtcbin.c:5596:on_rtpbin_ssrc_active:<webrtcbin> session 0 ssrc 1 active
0:01:00.732810571 20737 0x27afb50 INFO webrtcbin gstwebrtcbin.c:5596:on_rtpbin_ssrc_active:<webrtcbin> session 0 ssrc 1 active
0:01:00.950763602 20737 0x707092f0 WARN rtph264depay gstrtph264depay.c:899:gst_rtp_h264_depay_handle_nal: SPS
0:01:00.950883080 20737 0x707092f0 WARN rtph264depay gstrtph264depay.c:903:gst_rtp_h264_depay_handle_nal: PPS
0:01:01.134798019 20737 0x27afb50 INFO webrtcbin gstwebrtcbin.c:5596:on_rtpbin_ssrc_active:<webrtcbin> session 0 ssrc 1 active
0:01:01.333826698 20737 0x27afb50 INFO webrtcbin gstwebrtcbin.c:5596:on_rtpbin_ssrc_active:<webrtcbin> session 0 ssrc 1 active
0:01:01.534764433 20737 0x27afb50 INFO webrtcbin gstwebrtcbin.c:5596:on_rtpbin_ssrc_active:<webrtcbin> session 0 ssrc 1 active
0:01:01.742393807 20737 0x27afb50 INFO webrtcbin gstwebrtcbin.c:5596:on_rtpbin_ssrc_active:<webrtcbin> session 0 ssrc 1 active
0:01:01.854877261 20737 0x707092f0 WARN rtph264depay gstrtph264depay.c:899:gst_rtp_h264_depay_handle_nal: SPS
0:01:01.855516581 20737 0x707092f0 WARN rtph264depay gstrtph264depay.c:903:gst_rtp_h264_depay_handle_nal: PPS
I'm now going to create a longer tcpdump in order to extract the H.264 and let a stream analyzer run over it.
But the most important question is: Is it true, that WebRTC video decoding in browsers does not start, before at least one IDR has been received? If this would be true, I could try to go to Parrot and complain :)
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/9d6fab89-b662-43f0-93aa-a935d786e717n%40googlegroups.com.
ffmpeg -framerate 30 -i dump.h264 -c copy output.mp4
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/48efd303-9c3e-4dbe-aab5-e94f6904c11cn%40googlegroups.com.
ffmpeg -i rtsp://192.168.42.1/live -f h264 -vcodec copy udp://127.0.0.1:1234
2) Another process
gst-launch-1.0 -v udpsrc port=1234 ! h264parse ! avdec_h264 ! videoconvert ! autovideosink
This works.
BTW: This is what FFMPEG tells about the H.264 internals:
Input #0, rtsp, from 'rtsp://192.168.42.1/live':
Metadata:
title : live
comment : ANAFI-G134295
Duration: N/A, start: 1.101100, bitrate: N/A
Stream #0:0: Video: h264 (Main), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], 29.97 fps, 29.97 tbr, 90k tbn
Output #0, h264, to 'udp://127.0.0.1:1234':
Metadata:
title : live
comment : ANAFI-G134295
encoder : Lavf59.16.100
Stream #0:0: Video: h264 (Main), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 29.97 fps, 29.97 tbr, 29.97 tbn
Stream mapping:
Stream #0:0 -> #0:0 (copy)
Am 06.04.2022 um 19:30 schrieb Chema Gonzalez <che...@gmail.com>:
> Just that the initial scene kind of "unfolds", from inside to outside for one or two seconds, as tried to explain like a 70th Western intro.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/702aebcd-1c57-46bf-bfff-c22745d5d5b7n%40googlegroups.com.
[15032:48131:0406/202231.110771:WARNING:video_receive_stream2.cc(951)] No decodable frame in 200 ms, requesting keyframe.