[Camera Support]: Stuttering in live/playback; Via Reolink app no issues #14743
Replies: 1 comment 4 replies
-
|
You might try using the ffmpeg module with go2rtc, eg: |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I actually had that enabled for some time, but I will give it another shot and see if it makes any difference with the rest of the current settings. Thanks for the suggestion, I guess I need to look more into go2rtc troubleshooting. On that note, is there a way to easily see how settings end up being translated into raw ffmpeg parameters? I looked into the presets and it appears they are dynamically generated via several python scripts, but the only place I know of to look for the result is with |
Beta Was this translation helpful? Give feedback.
-
|
You shouldn't have to tweak any of the ffmpeg parameters on Frigate's side as it's just pulling the stream from go2rtc. You'll want to keep an eye on the go2rtc logs for any clues. You could enable |
Beta Was this translation helpful? Give feedback.
-
|
I am definitely going to do that, but after 5 hours of messing with this I think I may have found something that works - tell me if this makes any sense. This uses a lot more cpu (and virtually no gpu) so I think that it is re-encoding the h265 down to h264 before consumption by Frigate. This particular camera there is no way to force the main stream to be h264 or reduce the resolution, which I refuse to do anyways. This is the only settings I have found that displays the video without stuttering, which I was not able to do via VLC either. In hindsight I would not have bought these cameras, and for the rest of them they will either not be Reolink or I will test them and return if they have this limitation. I need to ensure that go2rtc is using hardware accel and not cpu, if you have any suggestions there. Thanks again. go2rtc:
streams:
reolinkbackyardtrackmix:
- rtsp://[email protected]:554/h264Preview_01_main
- ffmpeg:reolinkbackyardtrackmix#video=h264#audio=opus#hardware
reolinkbackyardtrackmix_sub:
- rtsp://[email protected]:554/h264Preview_01_sub
reolinkfronttrackmix:
- rtsp://[email protected]:554/h264Preview_01_main
- ffmpeg:reolinkfronttrackmix#video=h264#audio=opus#hardware
reolinkfronttrackmix_sub:
- rtsp://[email protected]:554/h264Preview_01_sub |
Beta Was this translation helpful? Give feedback.
-
|
Re-encoding to h264 would have been my next recommendation. It's a bummer you can't switch the codec in the camera itself. You can test hardware acceleration just by removing |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
I have an issue with my video stuttering, both live and recorded. I have searched and read through every single issue and post on every site that could even be remotely related, tried every suggestion and configuration, and gotten nowhere. I built this as a dedicated system specifically for security cameras, I'm not running it on proxmox or raspberry pi - it's a 20 core Intel i5 with 64GB of memory, GTX 1650 GPU, 2 coral TPU's and NVME hdd. The OS is Ubuntu 22.04 and running docker compose
I have several 4k Reolink Trackmix Wifi cameras connected via ethernet cable, only one is currently connected because I have not yet mounted the others outside. Viewing the video via the web interface or from the Reolink desktop app the video looks fine, no stuttering at all. This includes if I copy the saved video files off the SD card in the cameras. I'm pretty much ruling out issues with the camera itself due to that (I sniffed the reolink app, but it must use some proprietary protocol on port 9000).
In addition, I am getting frequent crashes of ffmpeg for various reasons, probably related to all the settings changes I have been continually making. I have not included those logs. The crashes are mostly related to detect errors and "unable to read frames from ffmpeg process"
I have to admit I'm pretty frustrated at this point, I can't proceed with adding additional cameras until I get this resolved. I am not going to tolerate stuttering video. Everyone has been very helpful in other posts here, hopefully I am just doing something dumb. Thanks in advance.
Version
System 0.14.1-f4f3cfa
What browser(s) are you using?
Thorium Version 124.0.6367.218 (Official Build) (64-bit)
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
Operating system
Other Linux
Install method
Docker Compose
Object Detector
Coral
Network connection
Wired
Camera make and model
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Frigate Docker Image
ghcr.io/blakeblackshear/frigate stable d1502760b3b1 2 months ago 1.92GB
Docker Version
Client: Docker Engine - Community
Version: 27.3.1
API version: 1.47
Go version: go1.22.7
Git commit: ce12230
Built: Fri Sep 20 11:41:00 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 27.3.1
API version: 1.47 (minimum version 1.24)
Go version: go1.22.7
Git commit: 41ca978
Built: Fri Sep 20 11:41:00 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.22
GitCommit: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc:
Version: 1.1.14
GitCommit: v1.1.14-0-g2c9f560
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Beta Was this translation helpful? Give feedback.
All reactions