MoonFin Source Error on Google TV for AV1 anime release - Jellyfin hardware transcoding not enabled?

Posted by noliver2761

Hello! I'm running SparkBox v1.6.110 on a UGREEN NAS. I originally started investigating because MoonFin on Google TV is unable to play a specific anime series. Most of my library works fine (Conan, Ghibli movies, etc.), but one particular series consistently throws a "Source Error" in MoonFin. Heres the details summarize by chatgpt so apologies for the robotic tone The release is: text [AV1 10bit][Opus 2.0] The same file plays correctly: in Jellyfin web browser on desktop but fails on MoonFin for Google TV. This made me suspect a transcoding issue. What I found The NAS itself has GPU devices available: bash ls /dev/dri Output: text by-path card0 renderD128 My .env contains: env JELLYFINHWACCEL=auto SparkBox appears to support automatic hardware transcoding overrides when /dev/dri exists: bash grep -n -A 40 -B 10 "docker-compose.hw.yml" /opt/sparkbox/sparkbox Relevant code: bash if [[ "${hwaccel}" != "" && "${hwaccel}" != "none" && -d /dev/dri ]]; then The override file exists: text /opt/sparkbox/modules/media/docker-compose.hw.yml and contains: yaml jellyfin-media: devices: - /dev/dri:/dev/dri groupadd: - "${JELLYFINVIDEOGID:-44}" - "${JELLYFINRENDERGID:-105}" However Inside the running Jellyfin container: bash sudo docker exec sb-jellyfin-media ls /dev/dri returns: text ls: cannot access '/dev/dri': No such file or directory And Docker inspect shows: json "Devices": null, "GroupAdd": null What I've tried bash sudo docker rm -f sb-jellyfin-media sudo sparkbox up media The container is recreated successfully, but still does not receive /dev/dri. Question Is this a known issue in v1.6.110? Should JELLYFINHWACCEL=auto automatically apply docker-compose.hw.yml on a UGREEN NAS with /dev/dri present? Or is there an additional step required to enable Jellyfin hardware transcoding?

3 replies

tomspark wrote:

Nice detective work — and yes, this is a known one. On v1.6.110 the hardware-transcoding override didn't actually get applied when the container came up, so /dev/dri never made it in even with JELLYFINHWACCEL set. That got fixed in v1.6.166, and you're a long way behind it (latest is 1.6.315). Update and it'll wire the GPU in automatically: sudo sparkbox update After it finishes, check with: sudo docker exec sb-jellyfin-media ls /dev/dri — you should see renderD128 listed. Then switch Hardware acceleration on in Jellyfin's own playback settings (that's the other half), and transcoding will actually use the GPU.

noliver2761 wrote:

Sorry for the late reply (I forgot my password lol) I ran sudo sparkbox update, but after recreating sb-jellyfin-media, SparkBox still reports v1.6.110 in the banner. So it looks like update only pulled container images and did not update the SparkBox CLI/scripts to v1.6.315. Is there a separate command to update the SparkBox core/installer itself? EDIT: i had been working in the terminal all this time and never noticed the big updated button on the ui lol. its fixed now!

tomspark wrote:

Ha — no worries, that button hides in plain sight, and you landed on the right answer: the dashboard's Update button is the one that upgrades SparkBox itself. You also spotted a real gap. On the old version you were running, the terminal command only refreshed your apps, never SparkBox itself — that's why the banner stayed stuck. Current versions now tell you that in the terminal and offer sudo sparkbox upgrade for the full upgrade, so you're covered either way. One last piece for your AV1 show: in Jellyfin's own settings, open Playback and switch hardware acceleration on — that's the second half of the fix. If that series still throws a Source Error on Google TV after that, come tell me.