Replies: 1 comment 3 replies
-
this is an issue with go2rtc, it is not related to hwaccel args. There is also minimal ways for frigate to know that this is happening - and that it is not on purpose (some users have audio only cameras doing audio detection, for example) |
Beta Was this translation helpful? Give feedback.
-
|
That didn't seem to be the case for me. In my previous config I had never even bothered to set go2rtc so that was the first thing I did when troubleshooting this. Once I got go2rtc set as documented camera feeds began working correctly their individual pages, but the black screen problem was still occurring on the overview/main page and was affecting the detection and recording as well still. I can recreate that situation and provide logging if this is not something that can be duplicated. |
Beta Was this translation helpful? Give feedback.
-
|
Most users who have seen this have seen it in recordings, not in the detect stream. Either way, I'm not sure there's a way to detect this on frigates side as there is a lot of data validation and this means ffmpeg is just outputting black |
Beta Was this translation helpful? Give feedback.
-
|
Note I'm on a thin client hand me down so maybe it's something with my environment. I have no experience running docker on a system like this and it was kind of set at and forget it before this so no idea if there are any issues. |
Beta Was this translation helpful? Give feedback.
-
I recently had an issue where all my feeds went black causing the complete loss of video and recording in the system. After a bunch of searching it appears my previously valid config with:
hwaccel_args: preset-vaapibecame invalid and needed to be replaced with:
hwaccel_args: []Since the logs were clean it took me quite awhile longer than I would have liked to track down the issue. It would be helpful if some kind of logging warning or error could be triggered if that situation occurs for other users.
Beta Was this translation helpful? Give feedback.
All reactions