@XtremeOwnageDotCom commented on GitHub (Jan 9, 2024):
Personally, I think this would be a lot simpler to implement as a global option only where all cameras share the pool and the cameras with…
@daernsinstantfortress commented on GitHub (Jan 9, 2024):
Thanks. Is there any updates docs or examples to follow, specifically when trying to avoid lots of duplicates for the same event?
Check…
@NickM-27 commented on GitHub (Jan 9, 2024):
I'd suggest using presets, check the logs to understand what isn't working. No, hwaccel_args don't apply to go2rtc
@NickM-27 commented on GitHub (Jan 9, 2024):
I personally have it setup so when the object first enters the zone is when I get the notification (since that is what most people care about…
@NickM-27 commented on GitHub (Jan 9, 2024):
Makes sense, I think time based retention will still be the primary metric but that may change over time.
Any details on this? I literally just…
@DustyArmstrong commented on GitHub (Jan 9, 2024):
Thanks, none of the presets work for me but I'll keep tinkering with it! Clarification, when I say "don't work", I mean they do not enable…
@NickM-27 commented on GitHub (Jan 9, 2024):
/events sends many updates for a single event. It can not be depended on that the new MQTT message will have the zones populated yet, you'll need to…
@DustyArmstrong commented on GitHub (Jan 9, 2024):
Thanks Nick, I tried preset-vaapi initially and that did not work for me, the only thing I've been able to get confirmed working is -c:v and…
@mabed-fr commented on GitHub (Jan 9, 2024):
A global option with a shared pool for all cameras seems more useful and understandable
@NickM-27 commented on GitHub (Jan 9, 2024):
How would you expect it to work on the camera level?
Imagine a scenario where you have:
- camera 1 has 10GB specified
- camera 2 has 20GB…
@NickM-27 commented on GitHub (Jan 9, 2024):
I would suggest using the recommended reolink config https://docs.frigate.video/configuration/camera_specific#reolink-cameras
also definitely don't…
@LordNex commented on GitHub (Jan 23, 2024):
Oh and technically there on the same physical server. We're just talking about different VMs it's only processing the vSwitch traffic which is all…
@github-actions[bot] commented on GitHub (Feb 23, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@NickM-27 commented on GitHub (Jan 23, 2024):
Oh and technically there on the same physical server. We're just talking about different VMs it's only processing the vSwitch traffic which is all…
@LordNex commented on GitHub (Jan 23, 2024):
Oh and technically there on the same physical server. We're just talking about different VMs it's only processing the vSwitch traffic which is all CPU…