Closed troykelly closed 2 years ago
Do you see messages in your logs about ffmpeg stopping and/or "Discarding a corrupt recording segment" around the time of the original event?
I believe that you can still use pre_capture and post_capture to set up the events.
@blakeblackshear would increasing the logging level reveal those? Everything I have (from the log) is above.
@goulaobangzi I'm not sure what you are referring to - the events are being captured, they are just corrupt video files.
There are a couple places to look for more information:
/usr/local/nginx/logs/error.log
Blake,
I do not see that specific error message, but my Recordings are being cut short after I upgraded to 0.9.1-800f33e. I have also updated to the v2.1.0 of the integration.
Example:
This recording is the perfect example. Event lasts 30 seconds, snapshot is taken 10 seconds in. That's perfect and expected behavior. Recording lasts 2 seconds and it's the last part of the video where the delivery guy has already left
Same issue... Not always but it happens several times a day.
Seeing the same thing here as well. I have the pre-capture and post-capture both set to 10. Happens several times a day as well since updating to the latest version.
Snapshot is perfect image of the person.
Event start time: 11:45:08 Event end time: 11:45:57 Total length of recorded clip: 13s (I would expect an absolute minimum of 20s based on pre/post-capture settings) Clip doesn't even show the person there.
The only logs around that time are managing websocket and terminating websocket messages. Not sure what these are or if it's related.
[2021-10-12 10:28:45] ws4py INFO : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49522] [2021-10-12 10:57:13] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:53272] [2021-10-12 11:52:23] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:34328] [2021-10-12 11:53:11] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:34328]
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I got this exact type of error once I tried to add sound by changing the global ffmpeg parameters to remove the "-an"
ffmpeg:
output_args:
record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy
Once I moved these lines to the camera section, I got sound in my recordings and the "playback aborted due to corruption" error disappeared.
Describe the problem you are having
Many (80%+) clips don't run for their full time and stop short with an error message of
Version
0.9.1-800F33E
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
No response
Operating system
HassOS
Install method
HassOS Addon
Coral version
USB
Network connection
Wired
Camera make and model
Univision NVR
Any other information that may be helpful
No response