+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: N100 Transcoding issue (/t-n100-transcoding-issue)
N100 Transcoding issue - puwaha - 2025-07-24
Hello everyone,
I've been using Jellyfin for quite some time, and never have run into this issue before. I have both an N100 and N150 based mini PC, and neither of them will do transcoding properly. I have tried multiple iterations of builds on both using VMs on Proxmox, LXCs on Proxmox, Docker versions on LDXs, Docker on full VMs, and even direct installs of Debian, Ubuntu, and even Windows on the mini pcs... (i.e. directly installing the OS on the mini pcs rather than going through a VM layer).
Every single instance I can get transcoding to work fine with these platforms... but it only works for about 30 seconds before the playback goes into a loop and eventually craps out. Direct play is fine. I've never had this issue previously when I had a docker of Jellyfin running on my Unraid server. That server died, so I went the sensible route and got an N150 based mini pc and ran into this issue. Thinking maybe it might be too new of a CPU/iGPU, I drug out my N100 based mini pc and am running into the same issue.
So, I'm looking for some help here to diagnose the logs to see what could possibly be going on.
Jellyfin version: 10.10.7
Current installation method: Ubuntu server VM (24..04.2) running on Proxmox 8.4.5, full iGPU passthrough of the Alder-Lake N iGPU to the VM, can see and interact with the /dev/dri/renderD128 device, intel_gpu_top shows that it's going through the iGPU
Using a web client to initiate transcoding to test the pipeline, playback starts fine for about 30 seconds and then goes into a loop where it seems to be restarting transcoding over and over until Jellyfin finally gives up.
Here are the logs: https://pastebin.com/u/puwaha/1/Z7ah8y6v
I greatly appreciate any help here, as this has been frustrating me for about 3 weeks now.
RE: N100 Transcoding issue - Fate - 2025-07-24
Whatever your issue is, it's not transcoding. Do you have disk space where jellyfin puts the transcode files?
Also don't use the web client, depending on your browser its very hit and miss.
Use the jellyfin client and lower the quality/bandwidth until transcoding is forced.
RE: N100 Transcoding issue - Dagnet - 2025-07-25
I have the exact same issue except its 15-17s then it loops, running jellyfin in a docker container, ubuntu 24.04, i5-12500 (hardware transcoding). I have storage for sure and the webclient loops every time, I went and tried the windows client as suggested and no loops, hardware encoding works perfectly. Seems like the issue is the web client, did try with edge too but also didnt work (my main is Vivaldi). Is there a way to fix this?
RE: N100 Transcoding issue - gizmomelb - 2025-07-25
did you opt-in/enable the updated 6.14 kernel which is needed to support Intel N100/n150 iGPU?
https://forum.proxmox.com/threads/opt-in-linux-6-14-kernel-for-proxmox-ve-8-available-on-test-no-subscription.164497/
RE: N100 Transcoding issue - nyanmisaka - 2025-07-25
https://github.com/jellyfin/jellyfin-web/pull/6985
RE: N100 Transcoding issue - Dagnet - 2025-07-25
(2025-07-25, 04:02 AM)nyanmisaka Wrote: https://github.com/jellyfin/jellyfin-web/pull/6985
I can't believe I spent 3-4 hrs today trying to make hardware encoding work (just finished setting up my jellyfin container) and it was not an issue on my side lol
Thanks for the info!