[Beta Support]: lot of dropped/lost frames in the recorded clips #21651
Extreme79
started this conversation in
Beta Support
Replies: 2 comments 2 replies
-
|
Your logs are indicative of network issues typical of wifi cameras. It's possible that the combination of changes between 0.16 and 0.17 could cause network behavior changes, but there's no way to know for sure, especially without a consistent way to reproduce it. See this note about wifi cameras and why we don't recommend them: https://ipcamtalk.com/threads/multiple-cameras-high-bandwidth.77100/#post-861110 |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I had the same issue after updating to Frigate 17. For me, changing hwaccel_args to preset-intel-qsv-h264 fixed the problem. |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
I was on 0.16.3 before upgrade, running on an Intel N150 16gb ram based minipc (beelink Eq14), in docker.
After the upgrade, directly to 17b2 I noticed a big amount of lost frames in the recorded clips, never happened before.
This with the same configuration, large amount of cameras (unfortunately all by wifi, some of these with low signal): 11 ip cameras (reolink, imou, flureon, yi with yihack fw, crap Chinese...) with active object detection (Yolo model).
Cpu stay normally between 20 and 45% with peaks of 60-70 (but rare).
Detectors inference 25-35ms.
Detectors cpu usage is around 5%, memory lower than 1%.
Cpu usage for recording lower than 5% (most of the time lower than 2%).
Recorded clips and db located in the secondary disk, not the system one.
Live streaming works flawlessy with no significant drops or lag. Sometime signal lost in some cameras, but this ever happened.
Host os Debian trixie headless.
Large amount of errors in logs due to the signal stability (and yihack fw in some cases), anyway the same as with 0.16.x
Beta Version
0.17.0b2
Issue Category
Recordings / Storage
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output (if applicable)
Install method
Docker CLI
docker-compose file or Docker CLI command
No manual command, container managed with portainer, shm elevated to 512mb running privilegedOperating system
Debian
CPU / GPU / Hardware
Intel n150 (beelink Eq14) with secondary NVMe "disk"
Screenshots
No response
Steps to reproduce
Unfortunately I don't know if it's something that can be reproduced.
Any other information that may be helpful
As I said, issue started with 0.17b2 (I installed directly the b2 from 0.16.3)
Beta Was this translation helpful? Give feedback.
All reactions