| 16 Oct 2024 |
 Mackeveli | In reply to @k900:0upti.me
Just get anything Rockchip or Meson or Allwinner and it'll be miles better Gotcha, I'll look into some SBCs with those SoCs | 15:53:33 |
| Mackeveli | In reply to @hexa:lossy.network
that or a low power x86 board I've never done research on low-power x86 boards since most people's recommendations are ARM boards. Do you know of any particularly good low power x86 boards? | 15:55:19 |
 @hexa:lossy.network | nothing conrete | 16:00:38 |
| @hexa:lossy.network | but there are n100 cores, or pentium cores | 16:00:48 |
| @hexa:lossy.network | and people have been putting them onto the sbc form factor | 16:00:58 |
| @hexa:lossy.network | and ideally they have a better bring-up and hardware support story | 16:01:10 |
 mattleon | In reply to @mackeveli:matrix.org
Gotcha, I'll look into some SBCs with those SoCs I've been happy with the orangepi5 (and the 5b, I have both). The 5 supports NVMe, which is miles ahead of SD card. I run frigate on the NPU with hardware decoding and encoding of the video streams, which allows me to run object detection with ~0% cpu usage. | 16:02:09 |
 K900 | Note that neither the NPU nor the video stuff works well on mainline yet | 16:02:34 |
| K900 | So you will have to deal with vendor kernel nonsense, at least for the time being | 16:02:47 |
| mattleon | Vendor kernels are pretty annoying to work with, but the orangepi5 can compile the joshua-riek kernels in about 25 minutes, so it's not too bad. | 16:03:27 |
| mattleon | The rk3588 was faster in several real world situations than my laptop with an i7-8565U at 1/8th the power draw at peak, which was mindboggling to me. Storage is quite a bit slower due to older (and fewer) PCIe lanes to the NVMe than on modern x86 | 16:06:06 |
| @hexa:lossy.network | sus 😄 | 16:08:25 |
| @hexa:lossy.network | but yeah, laptop cores are often potatoes | 16:08:35 |
| mattleon | In reply to @hexa:lossy.network
but yeah, laptop cores are often potatoes It was fanless, so it throttled down to < 2Ghz after 2 minutes of load | 16:19:18 |
| Mackeveli | What I'll likely do is have one board for services that require constant uptime bc my household will use them, like Jellyfin, HASS, and Immich (no ML stuff), then save the other board for less important services that I'll mainly be using. If an Orange Pi 16GB can handle those 3 services (very light usage of Jellyfin) and can run NixOS fairly easily, then I may go with it. mattleon Have you got an example NixOS configuration for your Orange Pi? | 16:20:27 |
| K900 | It can handle that fine, as long as you don't want hardware encoding for Jellyfin | 16:21:49 |
| mattleon | In reply to @mackeveli:matrix.org
What I'll likely do is have one board for services that require constant uptime bc my household will use them, like Jellyfin, HASS, and Immich (no ML stuff), then save the other board for less important services that I'll mainly be using. If an Orange Pi 16GB can handle those 3 services (very light usage of Jellyfin) and can run NixOS fairly easily, then I may go with it. mattleon Have you got an example NixOS configuration for your Orange Pi? This flake is a good starting point, my config is forked from an older version and switched over to the joshua-riek kernel: github.com/ryan4yin/nixos-rk3588
The joshua-riek kernel should support hardware encoding and decoding, though it's a good idea to have someone with an rk3588 board check before you buy (if you give me a source and dest format / ffmpeg line you want to use, happy to give it a shot) | 16:28:48 |
| Mackeveli | In reply to @mattleon:matrix.org
This flake is a good starting point, my config is forked from an older version and switched over to the joshua-riek kernel: github.com/ryan4yin/nixos-rk3588
The joshua-riek kernel should support hardware encoding and decoding, though it's a good idea to have someone with an rk3588 board check before you buy (if you give me a source and dest format / ffmpeg line you want to use, happy to give it a shot) Thanks, I'll take a look at that flake and do some more research on the Orange Pi to see if I'll pick it up. As for encoding/decoding, I'm not super familiar with the process as I don't tend to use Jellyfin very often or do video editing, but either H264 or AV1 encoding MP4 files seems like a solid start ffmpeg -i input. mp4 -c:v libaom-av1 -strict -2 output.mp4 / ffmpeg -i input.mp4 -c:v libx264 -tune film output.mp4 | 16:57:09 |
