frigate: [Support]: Side_Camera exceeded fps limit. Exiting ffmpeg
Describe the problem you are having
I am receiving a lot of “Side_Camera exceeded fps limit. Exiting ffmpeg”
I am wondering what this means and how to solve it. It is accompanied by a crash and restart of the ffmpeg process. Occurring on Reolink cameras configured NOT with the new RTSP restream set up. I had issues with that so I am using the direct config under ffmpeg and using all the arguments normal for frigate 11.0 but in 12.0 beta.
Version
12.0 beta 10
Frigate config file
Side_Camera:
ffmpeg:
input_args:
- -avoid_negative_ts
- make_zero
- -fflags
- +genpts+discardcorrupt
- -flags
- low_delay
- -strict
- experimental
- -analyzeduration
- 1000M
- -probesize
- 1000M
- -rw_timeout
- "5000000"
inputs:
- path: http://192.168.2.41/flv?port=1935&app=bcs&stream=channel2_main.bcs&user=user&password=password
roles:
- record
- detect
detect:
width: 2560
height: 1920
# objects:
# track:
# - person
mqtt:
enabled: True
timestamp: false
bounding_box: False
height: 1000
crop: True
quality: 100
ui:
order: 6
rtmp:
enabled: false
Relevant log output
2023-03-25 19:58:18.911908087 [2023-03-25 19:58:18] watchdog.Side_Camera INFO : Side_Camera exceeded fps limit. Exiting ffmpeg...
2023-03-25 19:58:18.912040066 [2023-03-25 19:58:18] watchdog.Side_Camera INFO : Waiting for ffmpeg to exit gracefully...
2023-03-25 19:58:19.723681334 [2023-03-25 19:58:19] frigate.video ERROR : Side_Camera: Unable to read frames from ffmpeg process.
2023-03-25 19:58:19.725254280 [2023-03-25 19:58:19] frigate.video ERROR : Side_Camera: ffmpeg process is not running. exiting capture thread...
FFprobe output from your camera
Since returning to the old way of loading camera in config, ffprobe in the system tab never loads
Frigate stats
No response
Operating system
UNRAID
Install method
Docker Compose
Coral version
USB
Network connection
Wireless
Camera make and model
Reolink RLN8-410
Any other information that may be helpful
No response
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 30
No I just had the date wrong that is it.