2024-07-11, 09:24 AM
Yes, I had started from scratch with the official Jellyfin docker container.
I think I may have found the culprit. As I thought, it was a permission issues. I had restored the uid & gid for the config folder after running the container as root but forgot to do the same for the cache folder. That is why some preview pictures could not be open and transcoding could not start. Now it seems fine.
Do you know how can I be sure I am using hardware acceleration (QuickSync in my case) to its full potential? I can see that when Jellyfin is transcoding on the fly and I run "sudo intel_gpu_top" the video activity goes to almost 100%.
![[Image: 3C3cVoz.png]](https://i.imgur.com/3C3cVoz.png)
This is how I setup the initial part of the "Playback" settings:
![[Image: 4vLkLpp.png]](https://i.imgur.com/4vLkLpp.png)
I think I may have found the culprit. As I thought, it was a permission issues. I had restored the uid & gid for the config folder after running the container as root but forgot to do the same for the cache folder. That is why some preview pictures could not be open and transcoding could not start. Now it seems fine.
Do you know how can I be sure I am using hardware acceleration (QuickSync in my case) to its full potential? I can see that when Jellyfin is transcoding on the fly and I run "sudo intel_gpu_top" the video activity goes to almost 100%.
This is how I setup the initial part of the "Playback" settings: