help on ubiquity uvc-g3 + RTSP

[kovaga]

Hi forum,

i have several uvc-g3 that i feed to ZM via FFMPEG and speciyfing the RTSP URL like that rtsp://192.168.222.31:554/s0

OS: Ubuntu 22.04
1.36.19-jammy1

All works fine, but I wanted to try feeding it via the RTSP and I get a segfault from the zmc process.

If I set it up with
Remote
RTSP
RTP/Unicast
192.168.222.31
554
s0
Use RTSP Response Media URL (tick)

I get the following in the zmc_m6.log
07/13/22 10:59:31.022814 zmc_m6[2400667].WAR-zm_rtp_source.cpp/341 [Discarding frame 148]
07/13/22 10:59:31.022863 zmc_m6[2400667].WAR-zm_rtp_source.cpp/333 [Discarding incomplete frame 148, 0 bytes]
07/13/22 10:59:31.852849 zmc_m6[2400664].ERR-zmc.cpp/305 [Failed to capture image from monitor 6 Cam1 - Entrace (LowRes) (1/1)]
07/13/22 10:59:41.843588 zmc_m6[2400668].ERR-zm_signal.cpp/50 [Got signal 11 (Segmentation fault), crashing]
07/13/22 10:59:41.843607 zmc_m6[2400668].ERR-zm_signal.cpp/80 [Signal address is (nil), from 0x7fc4c2a209c0]
07/13/22 10:59:41.843870 zmc_m6[2400668].ERR-zm_signal.cpp/101 [Backtrace 0: /usr/bin/zmc(+0x4f803) [0x55a1d7ee8803]]
07/13/22 10:59:41.843877 zmc_m6[2400668].ERR-zm_signal.cpp/101 [Backtrace 1: /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7fc4c28c2520]]
07/13/22 10:59:41.843880 zmc_m6[2400668].ERR-zm_signal.cpp/101 [Backtrace 2: /lib/x86_64-linux-gnu/libc.so.6(+0x1a09c0) [0x7fc4c2a209c0]]
07/13/22 10:59:41.844427 zmc_m6[2400668].ERR-zm_signal.cpp/101 [Backtrace 3: /usr/bin/zmc(+0x751cf) [0x55a1d7f0e1cf]]
07/13/22 10:59:41.844433 zmc_m6[2400668].ERR-zm_signal.cpp/101 [Backtrace 4: /usr/bin/zmc(+0x75ff9) [0x55a1d7f0eff9]]
07/13/22 10:59:41.844436 zmc_m6[2400668].ERR-zm_signal.cpp/101 [Backtrace 5: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xdc2c3) [0x7fc4c2c8d2c3]]
07/13/22 10:59:41.844443 zmc_m6[2400668].ERR-zm_signal.cpp/101 [Backtrace 6: /lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7fc4c2914b43]]
07/13/22 10:59:41.844446 zmc_m6[2400668].ERR-zm_signal.cpp/101 [Backtrace 7: /lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7fc4c29a6a00]]
07/13/22 10:59:41.844450 zmc_m6[2400668].INF-zm_signal.cpp/108 [Backtrace complete, please execute the following command for more information: addr2line -e /usr/bin/zmc 0x55a1d7ee8803 0x7fc4c28c2520 0x7fc4c2a209c0 0x55a1d7f0e1cf 0x55a1d7f0eff9 0x7fc4c2c8d2c3 0x7fc4c2914b43 0x7fc4c29a6a00]

I can see the initial RTSP negotiation between Zm and the camera, the stream is being sent via UDP
and after several seconds it crashes.

Here is the relevant part of the tcpdump

11:05:25.069351 IP 192.168.222.13.48012 > 192.168.222.31.554: Flags [F.], seq 567, ack 2025, win 83, length 0
11:05:25.069550 IP 192.168.222.31.554 > 192.168.222.13.48012: Flags [.], ack 568, win 3918, length 0
11:05:26.120157 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [S], seq 2997338362, win 42340, options [mss 1460,nop,nop,sackOK,nop,wscale 9], length 0
11:05:26.120342 IP 192.168.222.31.554 > 192.168.222.13.48014: Flags [S.], seq 172420352, ack 2997338363, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 2], length 0
11:05:26.120362 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [.], ack 1, win 83, length 0
11:05:26.120401 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [P.], seq 1:91, ack 1, win 83, length 90: RTSP: OPTIONS rtsp://192.168.222.31:554/s0 RTSP/1.0
11:05:26.120542 IP 192.168.222.31.554 > 192.168.222.13.48014: Flags [.], ack 91, win 3650, length 0
11:05:26.121924 IP 192.168.222.31.554 > 192.168.222.13.48014: Flags [P.], seq 1:276, ack 91, win 3650, length 275: RTSP: RTSP/1.0 200 OK
11:05:26.121929 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [.], ack 276, win 83, length 0
11:05:26.121955 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [P.], seq 91:182, ack 276, win 83, length 91: RTSP: DESCRIBE rtsp://192.168.222.31:554/s0 RTSP/1.0
11:05:26.123532 IP 192.168.222.31.554 > 192.168.222.13.48014: Flags [P.], seq 276:1160, ack 182, win 3650, length 884: RTSP: RTSP/1.0 200 OK
11:05:26.123536 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [.], ack 1160, win 83, length 0
11:05:26.132714 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [P.], seq 182:332, ack 1160, win 83, length 150: RTSP: SETUP rtsp://192.168.222.31:554/s0/trackID=2 RTSP/1.0
11:05:26.135749 IP 192.168.222.31.554 > 192.168.222.13.48014: Flags [P.], seq 1160:1495, ack 332, win 3918, length 335: RTSP: RTSP/1.0 200 OK
11:05:26.135768 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [.], ack 1495, win 83, length 0
11:05:26.136754 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [P.], seq 332:457, ack 1495, win 83, length 125: RTSP: PLAY rtsp://192.168.222.31:554/s0 RTSP/1.0
11:05:26.138437 IP 192.168.222.31.554 > 192.168.222.13.48014: Flags [P.], seq 1495:1804, ack 457, win 3918, length 309: RTSP: RTSP/1.0 200 OK
11:05:26.138443 IP 192.168.222.13.48014 > 192.168.222.31.554: Flags [.], ack 1804, win 83, length 0
11:05:26.221610 IP 192.168.222.31.37005 > 192.168.222.13.40201: UDP, length 28
11:05:26.221610 IP 192.168.222.31.37004 > 192.168.222.13.40200: UDP, length 42
11:05:26.221697 IP 192.168.222.13.40201 > 192.168.222.31.37005: UDP, length 52
11:05:26.221712 IP 192.168.222.31.37004 > 192.168.222.13.40200: UDP, length 16





Does anyone have those camers setup via RTSP?
any advice appreciated thanks

[Magic919]

Use ffmpeg source type.

[kovaga]

Use ffmpeg source type.

Well, I do already, but was wondering whether RTSP is also possible, as I have seen some people mention on this forum RTSP combination.

[Ralphred]

How does ffmpeg behave if you try to connect to the RTSP stream directly:

Code: Select all

ffplay rtsp://192.168.222.31:554/s0

[kovaga]

How does ffmpeg behave if you try to connect to the RTSP stream directly:

Code: Select all

ffplay rtsp://192.168.222.31:554/s0

Behaves good, starts playing fine. here is the output

Input #0, rtsp, from 'rtsp://192.168.222.31:554/s0':= 0B f=0/0
Metadata:
title : s0
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Audio: aac (LC), 11025 Hz, mono, fltp
Stream #0:1: Video: h264 (Main), yuvj420p(pc, bt709, progressive), 1920x1080 [SAR 189:190 DAR 168:95], 15 fps, 15 tbr, 90k tbn, 30 tbc
[swscaler @ 0x7fb0a0676a00] deprecated pixel format used, make sure you did set range correctly
15.57 A-V: -0.018 fd= 0 aq= 5KB vq= 123KB sq= 0B f=0/0

[iconnor]

The remote/rtsp is not being actively maintained. It used to exist because ffmpeg had issues, which I think mostly had to do with us not knowing how to use it. Use the ffmpeg type.

[kovaga]

ok, would do. thanks