[Config Support]: ffmpeg section retry_interval #16678
Unanswered
hh-TDA
asked this question in
Config Support
Replies: 3 comments 15 replies
-
|
Frigate log output |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
What is your full frigate config? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Sorry, this is my config.yml |
Beta Was this translation helpful? Give feedback.
-
|
Right now, I’m very happy that setting the |
Beta Was this translation helpful? Give feedback.
14 replies
-
|
Thank you. I have around 40 cameras, but only one or two of them occasionally experience timeouts. When this issue occurs, the other cameras and the server remain unaffected. Previously, AlexxIT mentioned, "Maybe your camera really stops sending data. Looks like you are using some cheap Chinese noname." This made me wonder if cheap cameras are more likely to experience timeouts. The main purpose of this discussion is to check if other users who are using inexpensive cameras are experiencing the same issue. |
Beta Was this translation helpful? Give feedback.
-
|
For the configuration, is it enough to set it in config.yml like this? Previously, I had set it like this: I used this configuration to distribute ffmpeg processing across two GPUs. For detection, can I assume that it will be automatically distributed without needing to configure it this way? Also, considering the model, would it be better to use the same GPU instead of different GPUs? |
Beta Was this translation helpful? Give feedback.
-
|
From the docs:
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you. When a problem occurs, the same camera always experiences repeated timeouts. Additionally, the video appears distorted, similar to a broken TV with incorrect colors. Ultimately, the issue that needs to be resolved is the camera's timeout, and it doesn't seem like this is a problem that can be avoided through Frigate NVR's configuration, right? |
Beta Was this translation helpful? Give feedback.
-
|
Correct. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
I am currently using the "HV-500EA" from H.view.
I am experiencing frequent issues where access to the camera is lost, or I am unable to log in to the camera's GUI. I'm unsure whether this is due to a network problem or a limitation of the camera itself.
Since I have multiple cameras connected, this issue occurs frequently, and when it happens simultaneously on multiple cameras, the system crashes.
Do you think adjusting the
retry_intervalcould help mitigate or resolve this issue?How do you usually avoid such problems with low-cost cameras?
Version
0.15.0-cea210d
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
Frigate stats
No response
Operating system
Other Linux
Install method
Docker Compose
docker-compose file or Docker CLI command
NothingObject Detector
TensorRT
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions