Tapo c120 cameras all experiencing choppy/laggy RTSP streams after 1.3.1 firmware
I have 8 of these cameras, all purchased and set up about 1.5-2 months ago. I have them all recording to sd, and also using my synology nas / surveillance station to record/stream them via RTSP (tcp).
Before the 1.3.1 firmware, they were working perfectly. Nice, smooth real-time views, however, after the 1.3.1 update they are showing a frame every 2-4 seconds, and randomly lagging behind for hours.
Changing hardware acceleration did not help with the quality.
Within synology ss, it 'found' them with onvif and I do have them set up as Tapo c120 cameras in there. I've also removed, then tried adding as generic onvif.
The c110s and c210s I have are still running smoothly in synology ss in 'live-view'.
Viewing the c120s from the tapo app in live-view seems fine. For me, it's something with the RTSP.
I've seen others (on reddit) with similar issues when trying to view with RTSP.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hey @kprojects,
We have seen reports on our subreddit and are following up with the development team. I actually just provided an update over there to the main threads (I really appreciate you calling out readding to ONVIF, as that was one of their specific questions).
Do you know if its particular to RTSP, and affects ONVIF as a result? Or is it a result of ONVIF itself? Do VLC Streams show the problem?
https://www.reddit.com/r/Tapo/comments/1jlylqg/tapo_c121_firmware_updated_to_131_and_now_they/
Most recently:
Hey Everybody,
So that nobody is left in the dark: our teams are taking a look at the reported behaviors introduced in the latest firmware update to the C120 and C121. While these appear to largely relate to the RTSP and ONVIF streams, we are seeing a few reports that the Tapo Apps behavior is also impacted.
I will provide an update from as soon as I can with more information, and we may end up reaching out to a few of you for additional information. I have given links to these threads, and I've summarized what we are seeing – but these are the questions that were also asked:
General
-
What is the Connection Quality of Your Camera (Device Info > Tap on the Wireless Signal Icon)
-
If your RTSP and ONVIF Performance is Affected, What Does Your Tapo App Performance Look Like?
-
Have you observed any other significant changes, such as with the accuracy of pet detection?
Networked Stream Performance
-
What RTSP/ONVIF Client Are You Using?
-
Does your client report a reduced frame rate, dropped frames, or does it appear as a stable network stream with lagging video?
-
Have you attempted to remove and re-add the device to your ONVIF or NVR?
-
Are you able to verify if the behavior exists on both the Low and High Quality RTSP Streams?
Tapo App Performance
-
If your Camera’s Performance in the Tapo is Affected, What is Your OS and App Version?
-
Have You Tried to Toggle the Hardware Acceleration Feature in the Tapo App?
-
Since the last update, is the time to load/view the stream from the Tapo App higher or lower?
- Copy Link
- Report Inappropriate Content
@Riley_S Thanks for the reply.
I just tried with vlc and not really getting anywhere.
Media -> open network stream
url: rtsp://192.168.86.250:554/stream1
Errors in log (pulled out what i thought was important):
satip error: Failed to setup RTSP session
access_realrtsp warning: only real/helix rtsp servers supported for now
main debug: no access modules matched
main debug: dead input
I'm seeing the same error(s) in /stream2 .. but also my c110. i'm not sure my vlc is doing this correctly.
Not sure how synology is able to grab a frame every 3-4 seconds. Maybe it's just hammering at 2020/554 and eventually gets one?
I also tried rtsp://user:pass@<ip address>:554/stream1 with same results.
Edit: here's some interesting stuff using ffprobe on a c120. I'm not getting these errors on my c110 that is working fine:
$ ffprobe 'rtsp://[username]:[password]@192.168.86.250:554/stream1'
[h264 @ 0x55b8f2443140] SEI type 764 size 272 truncated at 256
Last message repeated 3 times
[rtsp @ 0x55b8f2438a00] max delay reached. need to consume packet
[rtsp @ 0x55b8f2438a00] RTP: missed 3 packets
[h264 @ 0x55b8f2443140] SEI type 115 size 1648 truncated at 376
Input #0, rtsp, from 'rtsp://[username]:[password]@192.168.86.250:554/stream1':
Metadata:
title : Session streamed by "TP-LINK RTSP Server"
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: h264 (High), yuv420p(progressive), 2560x1440, 20 fps, 20 tbr, 90k tbn, 40 tbc
Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
vs. the c110:
$ ffprobe 'rtsp://[username]:[password]@192.168.86.26:554/stream1'
Input #0, rtsp, from 'rtsp://[username]:[password]@192.168.86.26:554/stream1':
Metadata:
title : Session streamed by "TP-LINK RTSP Server"
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Video: h264 (High), yuv420p(progressive), 1920x1080, 15 fps, 19.92 tbr, 90k tbn, 30 tbc
Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s
- Copy Link
- Report Inappropriate Content
Playing with ffprobe (above) I realized that only /stream1 was having issues. I just removed the camera from synology and added it as a generic rtsp camera. I pointed it at /stream2 and it's working fine, though in 640x360.
- Copy Link
- Report Inappropriate Content
More info .. i polled each of my 8 c120s that got the 1.3.1 update:
ffprobe 'rtsp://username:password@CAMERA_IP:554/stream1'
ffprobe 'rtsp://username:password@CAMERA_IP:554/stream2'
192.168.86.46 - Stream1: ❌ Stream2: ✅
192.168.86.57 - Stream1: ❌ Stream2: ✅
192.168.86.33 - Stream1: ❌ Stream2: ✅
192.168.86.50 - Stream1: ❌ Stream2: ✅
192.168.86.44 - Stream1: ❌ Stream2: ✅
192.168.86.43 - Stream1: ❌ Stream2: ✅
192.168.86.250 - Stream1: ❌ Stream2: ✅
192.168.86.34 - Stream1: ❌ Stream2: ✅
Detailed Errors:
192.168.86.46 - Stream1:
[h264 @ 0x62e4998595c0] SEI type 764 size 272 truncated at 256
192.168.86.57 - Stream1:
[h264 @ 0x63132e2fb5c0] SEI type 764 size 272 truncated at 256
192.168.86.33 - Stream1:
[h264 @ 0x5628e91885c0] SEI type 764 size 272 truncated at 256
192.168.86.50 - Stream1:
[h264 @ 0x5873d320f5c0] SEI type 764 size 272 truncated at 256
192.168.86.44 - Stream1:
[h264 @ 0x5dfb9add85c0] SEI type 764 size 272 truncated at 256
192.168.86.43 - Stream1:
[h264 @ 0x590276cd65c0] SEI type 764 size 272 truncated at 256
[h264 @ 0x590276cd65c0] SEI type 764 size 400 truncated at 384
[h264 @ 0x590276cd65c0] SEI type 764 size 272 truncated at 256
[h264 @ 0x590276cd65c0] SEI type 764 size 400 truncated at 384
192.168.86.250 - Stream1:
[h264 @ 0x559076312540] SEI type 764 size 272 truncated at 256
192.168.86.34 - Stream1:
[h264 @ 0x5c875b2be5c0] SEI type 764 size 528 truncated at 512
- Copy Link
- Report Inappropriate Content
@Riley_S - any updates on this?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 89
Replies: 5
Voters 0
No one has voted for it yet.