| 12 Feb 2025 |
 @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 |
| motiejus | I can't get the detect process to read from go2rtc, always weirdly get the same ffmpeg error Error opening input files: Invalid data found when processing input when the detect role comes not directly from camera, but from go2rtc (record is fine).
I will put this on hold for some time (a few days?). I disabled detect process, will be recording only for now (no cpu use).
| 20:37:02 |
| @hexa:lossy.network | ERROR : The following ffmpeg logs include the last 100 lines prior to exit.
ERROR : [AVHWFramesContext @ 0x7fd4c0078880] Failed to sync surface 0x9: 1 (operation failed).
ERROR : [hwdownload @ 0x7fd4cc0025c0] Failed to download frame: -5.
ERROR : [vf#1:0 @ 0x1b6ef480] Error while filtering: Input/output error
ERROR : [vf#1:0 @ 0x1b6ef480] Task finished with error code: -5 (Input/output error)
ERROR : [vf#1:0 @ 0x1b6ef480] Terminating thread with return code -5 (Input/output error)
| 20:37:59 |
| @hexa:lossy.network | this is what I'm seeing every few minutes | 20:38:03 |
| motiejus | also, I can't understand the relationship of go2rtc config in frigate, and its own. I guess I shouldn't use go2rtc top-level in frigate config, and just use the rtsp endpoints. But then the docs don't help understand this too:
After adding this to the config, restart Frigate and try to watch the live stream for a single camera by clicking on it from the dashboard. It should look much clearer and more fluent than the original jsmpeg stream.
| 20:39:05 |
| @hexa:lossy.network | frigate can run its own go2rtc process and configure it | 20:39:46 |
| motiejus | if I run ffmpeg command myself, I logs lots of lost packets (the router behind the camera is under stress). I think it makes sense to restart in higher-bandwidth situation | 20:39:53 |
| @hexa:lossy.network | in nixos I just configure go2rtc myself | 20:39:54 |
| motiejus | ok, so that's what its for. Ditto, I just did it myself. | 20:40:05 |
| motiejus | tailscale0:
TX packets:316154987 errors:0 dropped:51176 overruns:0 carrier:0
that's not too bad.
| 20:42:16 |
