| 13 Jan 2025 |
 @hexa:lossy.network | navidrome playback really needs to bridge the gap until the machine is rebooted | 14:06:31 |
| @hexa:lossy.network | so cache like 120-180s of playback time, maybe 🤔 | 14:06:48 |
| 14 Jan 2025 |
 Samsonite | ok, i have a dedicated beelink device now that i just got nixos installed on and got frigate running | 01:17:21 |
| Samsonite | trying to get the usb coral to work, i know that people have gotten it to work on nixos | 01:17:42 |
| @hexa:lossy.network | configuring a detector with type edgetpu and a device starting with usb/pci will get coral support enabled | 01:18:09 |
| Samsonite | booom | 01:18:43 |
| Samsonite | awesome, only error i see now is "did not detect hwacce, using a gpu for accelerated video decoding is highly recommended" | 01:29:46 |
| @hexa:lossy.network | hrm, yeah | 01:30:13 |
| Samsonite | im using a beelink with a AMD/ATI Cezanne Radeon Vega Mobile series | 01:30:21 |
| Samsonite | any way to make that little thing help out | 01:30:33 |
| @hexa:lossy.network | did you configure settings.ffmpeg.hwaccel_args? | 01:31:34 |
| @hexa:lossy.network | set it to preset-vaapi | 01:31:55 |
| Samsonite | nah sorry i asked before checking into this really, bad etiquette | 01:32:06 |
| Samsonite | thanks! | 01:32:08 |
| Samsonite | i see this nowhttps://docs.frigate.video/configuration/hardware_acceleration/ which says the same thing | 01:32:29 |
| @hexa:lossy.network | some day someone should write a wiki article | 01:32:39 |
| @hexa:lossy.network | yeah, or https://docs.frigate.video/configuration/ffmpeg_presets/#hwaccel-presets | 01:32:55 |
| @hexa:lossy.network | also linked from the module under the vaapiDriver option | 01:33:08 |
| @hexa:lossy.network | both links actually | 01:33:13 |
