The reason why you wouldn’t have seen any activity on the intel card while playing a video on your pc is that it didnt require any transcoding and could play directly on your pc. in the screen i was showing was a video being transcoded to mobile phone over 5G. if you direct play over your lan there is no need for the card to do any work.
also you need to restart jellyfin from the jellyfin dashboard when you make changes so they are applied.
also enable these intel hardware encoders and restart the jellfyfin server from jellyfin dashboard
also enabling hardware acceleration in trickplay settings could speed up the image generation during scans
Another small note is I haven’t encountered a browser I can use yet that will let me passthrough dolby atmos or dts audio and I require the jellyfin client apps for those features to work, so if you’re looking for dolby/dts audio playback stick to using the jellyfin client apps rather than any web browsers.
Ok . Thanks a lot .
Going to do this.
For instance , il am going to my work.
I Will see this tonight. This evening .
I looked a little closer and noticed you have another few changes in the transcoding settings. you need to enable intel quicksync QSV rather than the VAAPI and leave the box below blank. it should autodetect QSV device when you restart the jellfyfin server.
Thanks for your invaluable help, James.
Isn’t Vaapi more stable than QuickSync?
I’ve yet to encounter a stability issues with qsv, intel qsv is quicker and better optimised for intel hardware so generally preferred on intel based media servers for encoding tasks.
Isn’t Vaapi more stable than Quicksync?
By the way, your settings are for the A380 you own.
Are they exactly the same for the A310?
I’ll send you my details this evening.
vaapi can be more stable on older hardware, For newer Intel hardware (such as Arc GPUs), Quicksync is now recommended because Intel has deprecated the old media SDK in favor of OneVPL, making VA-API less efficient on these specific platforms.
if you encounter any artifacting or other issues you could try falling back to vaapi.
and you can just copy those settings for your intel a310
I’m leaving work.
I’m heading home.
I’m on my way.
hi james , i’m back .
here are some photos :
my vaapi :
my hardware presets :
like you see , after restarting jellyfin , the quicksync device do not appear .
do i have to go back to vaapi ?
what have i to do ?
Yeah, this thread actually highlights a bigger issue right now with ZimaOS, there’s a difference between “Linux technically supports the GPU” and “ZimaOS fully supports and integrates it properly.”
The AMD user is correct in saying Linux has AMD drivers (amdgpu), so AMD cards can work. But for Jellyfin transcoding specifically, Intel Arc is still the safer and more recommended option at the moment.
Even Jellyfin’s own documentation tends to favor Intel Arc on Linux because:
Also important: the RX 6400 mentioned in the thread is actually not a great Jellyfin card because those lower-end AMD cards have limited hardware encoding support.
What many users are seeing right now on ZimaOS is:
So the backend support may work while the frontend/UI side still feels unfinished.
Honestly, the thread also shows something else, a lot of the real compatibility testing is currently being done by community users rather than having a very clear official compatibility list from IceWhale yet.
For someone building a Jellyfin box today on ZimaOS, I’d probably still lean:
I don’t think you need to do anything, I have always left the box blank by default during installs, it seems regardless of the box saying qsv device like mine that it appears to have detected the arc card and is functioning correctly, so its just cosmetic really. are you having any issues with transcoding?
Most times you will find that apps from app store require very little configuration unless they are from a different repo like the big bear casa os or linux server repositories, where you found the version of btop that gave you hassle rather than using the built in version ZimaOS has. then they fall out of the official or approved/certified category. and you can find problems installing and using them out the box without some extra user input and tinkering.
Hello James. And thanks for your support.
Yes, I found it odd that there was no mention of ‘QSV Device’ as there is on your system, but the transcoding seems to be working perfectly.
Still having issues with the same old series (‘Les Brigades du Tigre’), but overall, it’s working quite well.
Tell me, do you have an extension in Jellyfin Stable (10.10.7) to display the specifications (MPEG-2/4, AAC/AC3/DTS, HDR/SDR, 720p/1080p, etc.) in the video listings?
do you mean like that? I’m not sure i understand. I cant remember if 10.10.7 does that. I updated to the latest version (10.11.8) after setting up my libraries etc a little while ago now.
A good start, but that’s not what I had in mind…
I was thinking more along the lines of small thumbnails here.
(for example)
yes , thats what i mean .
nearly .
I think i get what you mean I think the movies category displays the media info by default but shows category does not, there may be an option somewhere for it in library settings. I haven’t looked to be honest.
In any case, James, thank you once again for your support and help.
I’ve been a bit of a nuisance; I hope you haven’t held it against me.
The hard part is over.
All that’s left are the minor details.
Sometimes quite pleasant, but minor nonetheless.
Thanks again.
