| 12 Feb 2025 |
 @hexa:lossy.network | ok, my config is really simple at this point | 21:22:33 |
| @hexa:lossy.network | cameras:
Foo:
detect:
enabled: true
ffmpeg:
inputs:
- input_args: preset-rtsp-restream
path: rtsp://127.0.0.1:8554/g3-flex?mp4
roles:
- record
motion:
mask:
- 0,0,223,0,224,27,0,27
Bar:
detect:
enabled: false
ffmpeg:
inputs:
- input_args: preset-rtsp-restream
path: rtsp://127.0.0.1:8554/g3?mp4
roles: []
motion:
mask:
- 0,0,223,0,224,27,0,27
database:
path: /var/lib/frigate/frigate.db
detectors:
coral:
device: pci
enabled: true
type: edgetpu
ffmpeg:
hwaccel_args: preset-vaapi
mqtt:
enabled: false
host: localhost
record:
enabled: false
retain:
days: 2
mode: all
| 21:22:47 |
| @hexa:lossy.network | video encode/decode using vaapi with intel quicksync video | 21:23:22 |
| @hexa:lossy.network | detection with a coral edgetpu pcie device | 21:23:32 |
| @hexa:lossy.network | and I don't see any process that is particular busy all the time | 21:24:11 |
| @hexa:lossy.network | load15 is 0.7 | 21:24:18 |
| @hexa:lossy.network | motiejus: anything in particular I should add to my setup? | 21:24:32 |
| @hexa:lossy.network | I now enabled recordings | 21:32:01 |
| @hexa:lossy.network | the frigate.process processes are still only consuming like 3-5%CPU | 21:33:10 |
| @hexa:lossy.network | fwiw: I terminate all streams in go2rtc first | 21:35:08 |
| @hexa:lossy.network | that is the central point that handles multiplexing of camera access | 21:35:39 |
| @hexa:lossy.network | hm, the ffmpeg capture processes seem to be crashing all the time | 22:21:36 |
| @hexa:lossy.network | that's not good | 22:21:44 |
| 13 Feb 2025 |
 motiejus | You don't seem to have detect role in either cameras (according to your setup). | 06:59:27 |
| motiejus | the other difference is sound detection which I have and you don't, and I don't believe it should be an issue (I can disable it on my end just to be sure). I am also not using go2rtc, but perhaps it's different "enough" that I should | 07:00:40 |
| motiejus | * You don't seem to have detect role in either cameras (according to the config you've pasted). | 07:01:42 |
| @hexa:lossy.network | ah … roles | 10:06:18 |
| motiejus | I disabled sound, no avail. Wasn't able to get go2rtc to work in 30 minutes, dropped it for now, I'll get back to it during the evening or so. | 10:07:05 |
| motiejus | * I disabled sound, as expected, didn't resolve it. Wasn't able to get go2rtc to work in 30 minutes, dropped it for now, I'll get back to it during the evening or so.e | 10:07:14 |
| motiejus | * I disabled sound, as expected, didn't resolve it. Wasn't able to get go2rtc to work in 30 minutes, dropped it for now, I'll get back to it during the evening or so. | 10:07:19 |
| @hexa:lossy.network | added the detect role to one camera | 10:11:44 |
| @hexa:lossy.network | and now the frigate.process process uses like 7-11%CPU | 10:12:06 |
| motiejus | ok, so looks like go2rtc needs to be configured separately; which is not obvious from frigate docs | 15:03:36 |
| @hexa:lossy.network | yeah, we can't have frigate set up a system service in nixos 😄 | 15:27:46 |
| @hexa:lossy.network | i think they automatically integrate with it fwiw | 15:27:57 |
| @hexa:lossy.network |
configuration is now done via UI. Yaml is no longer needed
| 20:21:31 |
| @hexa:lossy.network | sigh | 20:21:36 |
| @hexa:lossy.network | https://github.com/evcc-io/evcc/releases/tag/0.200.0 | 20:21:42 |
| @hexa:lossy.network | this release is full of surprises at the 1 minute mark alread | 20:22:12 |
| @hexa:lossy.network | * this release is full of surprises at the 1 minute mark already | 20:22:13 |
