| 16 Feb 2025 |
 motiejus | * configured go2rtc, same high cpu usage. What is the resolution you are feeding to the detect stream? | 19:53:43 |
 @hexa:lossy.network | api:
listen: :1984
ffmpeg:
bin: /nix/store/a4ha6dhk6xlrkpybnh5d8dnqq6c9mlph-ffmpeg-headless-7.1-bin/bin/ffmpeg
rtsp:
listen: :8554
streams:
g3:
- rtsp://192.168.110.231:554/s0
g3-flex:
- rtsp://192.168.110.230:554/s0
webrtc:
listen: :8555
| 20:35:47 |
| @hexa:lossy.network | I would think the native resolution? 😄 | 20:35:54 |
| @hexa:lossy.network | neither frigate nor go2rtc has any resolution configured | 20:36:14 |
| motiejus | 
Download image.png | 20:39:07 |
| motiejus | no matter what I try :D | 20:39:11 |
| motiejus | it's transcoding h.265 -> h.264 (to conserve bandwidth) using 7-8% of core per stream, and "detecting" with a full core + coral. :) | 20:40:08 |
| @hexa:lossy.network | pretty sure my cameras are send h.264 | 20:47:20 |
