blu commented on issue starred/frigate-blakeblackshear-2#4462 2026-02-06 12:44:00 -08:00
[Camera Support]: Different CPU usage across camera models with same encode settings

@bob454522 commented on GitHub (Jan 2, 2024):

If you're referring to the 7% CPU usage of ffmpeg versus the 14% CPU usage, I would not worry or focus on this. (you can mask out motion areas over…

blu commented on issue starred/frigate-blakeblackshear-2#4462 2026-02-06 12:44:00 -08:00
[Camera Support]: Different CPU usage across camera models with same encode settings

@binarybucks commented on GitHub (Jan 3, 2024):

Thank you @bob454522 the hint to CBR and checking the stream information with VLC was very insightful.

The firmware on both camera models indeed…

blu commented on issue starred/frigate-blakeblackshear-2#4462 2026-02-06 12:43:58 -08:00
[Camera Support]: Different CPU usage across camera models with same encode settings

@binarybucks commented on GitHub (Dec 29, 2023):

I tried different firmwares but they all seem to be using yuvj420p unfortunately.

Using 640x480 for detection drops CPU to 7% but I'd like to…

blu closed issue starred/frigate-blakeblackshear-2#4461 2026-02-06 12:43:55 -08:00
[Support]: Send to Frigate+ fails
blu closed issue starred/frigate-blakeblackshear-2#4462 2026-02-06 12:43:55 -08:00
[Camera Support]: Different CPU usage across camera models with same encode settings
blu commented on issue starred/frigate-blakeblackshear-2#4460 2026-02-06 12:43:55 -08:00
[Config Support]: storing go2rtc config in /dev/shm causes it to lose homekit pairings

@NickM-27 commented on GitHub (Dec 29, 2023):

Is there a reason why go2rtc.yaml needs to be in /dev/shm? Is it possible to update the code to persist go2rtc.yaml in /config? Thanks!

because…

blu commented on issue starred/frigate-blakeblackshear-2#4461 2026-02-06 12:43:55 -08:00
[Support]: Send to Frigate+ fails

@blakeblackshear commented on GitHub (Dec 29, 2023):

Does this always happen or just occasionally?

blu commented on issue starred/frigate-blakeblackshear-2#4461 2026-02-06 12:43:55 -08:00
[Support]: Send to Frigate+ fails

@jasonjgeiger commented on GitHub (Dec 29, 2023):

Every time. Woke this morning with the thought that the only thing I didn't try was regenerating my API key in Frigate+. Regenerated a new key,…

blu commented on issue starred/frigate-blakeblackshear-2#4462 2026-02-06 12:43:55 -08:00
[Camera Support]: Different CPU usage across camera models with same encode settings

@NickM-27 commented on GitHub (Dec 29, 2023):

There can be a number of differences that increase CPU usage. The pixel format difference you noticed is one, yuvj420p is deprecated. Also it can…

blu commented on issue starred/frigate-blakeblackshear-2#4457 2026-02-06 12:43:54 -08:00
Add option to fall back to CPU when timelapse encode fails

@spattinson commented on GitHub (Oct 19, 2025):

nvenc/dec is not influenced by the GPU compute. It's another dedicated part on the die, and its the same as consumer ones of a similar generation

blu opened issue starred/frigate-blakeblackshear-2#4460 2026-02-06 12:43:54 -08:00
[Config Support]: storing go2rtc config in /dev/shm causes it to lose homekit pairings
blu opened issue starred/frigate-blakeblackshear-2#4461 2026-02-06 12:43:54 -08:00
[Support]: Send to Frigate+ fails
blu opened issue starred/frigate-blakeblackshear-2#4462 2026-02-06 12:43:54 -08:00
[Camera Support]: Different CPU usage across camera models with same encode settings
blu closed issue starred/frigate-blakeblackshear-2#4460 2026-02-06 12:43:54 -08:00
[Config Support]: storing go2rtc config in /dev/shm causes it to lose homekit pairings
blu commented on issue starred/frigate-blakeblackshear-2#4457 2026-02-06 12:43:51 -08:00
Add option to fall back to CPU when timelapse encode fails

@NickM-27 commented on GitHub (Mar 1, 2024):

It's also possible that the new preview video (low res low fps) feature coming in 0.14 will suffice and timelapse reendodes will not need to be done…

blu commented on issue starred/frigate-blakeblackshear-2#4457 2026-02-06 12:43:49 -08:00
Add option to fall back to CPU when timelapse encode fails

@ehn commented on GitHub (Mar 1, 2024):

Would the problem of falling back on the CPU be worse than not working at all?

blu commented on issue starred/frigate-blakeblackshear-2#4457 2026-02-06 12:43:49 -08:00
Add option to fall back to CPU when timelapse encode fails

@NickM-27 commented on GitHub (Mar 1, 2024):

Well it depends, if a user doesn't have an adequate CPU for that type of load then it could do the export at the expense of causing issues for other…

blu commented on issue starred/frigate-blakeblackshear-2#4457 2026-02-06 12:43:48 -08:00
Add option to fall back to CPU when timelapse encode fails

@blakeblackshear commented on GitHub (Feb 29, 2024):

Not sure why you are hitting the 32 limit, but you will still have hwaccel if you move it down and define it for each camera instead of…

blu commented on issue starred/frigate-blakeblackshear-2#4457 2026-02-06 12:43:48 -08:00
Add option to fall back to CPU when timelapse encode fails

@ehn commented on GitHub (Feb 29, 2024):

Not sure why you are hitting the 32 limit, but you will still have hwaccel if you move it down and define it for each camera instead of globally.…

blu commented on issue starred/frigate-blakeblackshear-2#4457 2026-02-06 12:43:48 -08:00
Add option to fall back to CPU when timelapse encode fails

@NickM-27 commented on GitHub (Feb 29, 2024):

we could have some sort of config option that enables trying to use cpu when gpu fails, would probably need to be optional because using a CPU for…