#arca380 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #arca380, aggregated by home.social.
-
Done this with the #AMD 5600G's iGPU, now testing #Jellyfin hardware transcoding with my #Intel #ArcA380 GPU - one question though, is it normal for CPU usage to be rather high at least in the early parts of streaming (while transcoding), even with hardware transcoding?
I'm just trying to figure out if it is actually hardware transcoding - I'm assuming it is, bcos on the admin dashboard I'm seeing that it's transcoding as AV1 and I'm sure my Ryzen 7 1700 would not be able to do/handle that, esp considering that I'm testing with 4 streams playing concurrently? but the CPU usage is rather high the first minute or two or more from when the stream starts, it does lower down afterwards - the video playback is perfectly fine, no stuttering or anything like that.
My method of passthrough is the same as I did with the 5600G, that is a simple passthrough to the #LXC container, then to the #Docker container running Jellyfin. I don't think I noticed this high CPU usage when testing the 5600G, and the only minor configuration difference between the two was I'd used #VAAPI with the 5600G and disabled #AV1 encoding (since idt it supports it), while on the Arc A380 GPU I'm using Intel's #QSV and have enabled AV1 encoding.
Am I correct to assume that hardware transcoding is indeed working? Cos again, I'm quite certain my Ryzen 7 1700 would definitely NOT be able to handle this lol esp since I only give the LXC container 2 cores. -
I have finally caved in and dove into the rabbit hole of #Linux Container (#LXC) on #Proxmox during my exploration on how to split a GPU across multiple servers and... I totally understand now seeing people's Proxmox setups that are made up exclusively of LXCs rather than VMs lol - it's just so pleasant to setup and use, and superficially at least, very efficient.
I now have a #Jellyfin and #ErsatzTV setup running on LXCs with working iGPU passthrough of my server's #AMD Ryzen 5600G APU. My #Intel #ArcA380 GPU has also arrived, but I'm prolly gonna hold off on adding that until I decide on which node should I add it to and schedule the shutdown, etc. In the future, I might even consider exploring (re)building a #Kubernetes, #RKE2 cluster on LXC nodes instead of VMs - and if that's viable or perhaps better.
Anyway, I've updated my #Homelab Wiki with guides pertaining LXCs, including creating one, passing through a GPU to multiple unprivileged LXCs, and adding an #SMB share for the entire cluster and mounting them, also, on unprivileged LXC containers.
🔗 https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/proxmox.md#linux-containers-lxc -
I... actually managed to do this and it was somewhat messy to get through with it, but I did it. My 'stoppers' initially were simply needing to update some of the #Jellyfin's
xmlconfigs for any wrong/old paths/values, and lastly, the #SQLite DBs themselves which had old paths as well - most of which were easy to fix as they'retextvalues, but some were (JSON)blobs, using the same extension on #VSCode, this wasn't that hard to do either by simply exporting the blob, editing the blob's JSON text value, and reimporting the blob to the column. Oh, I also had to updatemeta.jsonfiles of all plugins I've installed to point to the new path to their logos.
Now my Jellyfin #LinuxServer.io container sitting in an unprivileged (#Debian #Linux) #LXC container on #Proxmox is set up with hardware transcoding using the #AMD Ryzen 5 5600G onboard iGPU (cos I'm getting impatient in waiting for my #Intel #ArcA380 to arrive). I'll update my #ErsatzTV container to do the same. Everything's perfect now, 'cept, I still wouldn't recommend users to stream Jellyfin on the web or a web-based client using transcoding, cos while the transcoding itself is perfect, Jellyfin seems to have an issue (that I never got on #Plex) whereby the subtitle would desync pretty consistently if not direct playing - with external or embedded subs, regardless. Dk if that can ever be fixed though, considering the issue has been up since 2023 with no fix whatsoever.
There's also a separate issue I'm having where Jellyfin does not seem to support discovering/serving media files that are contained in a symlink directory (even though there were some people on their forums reporting in the past that it should) - I've reported it last week, but it's not going anywhere for now. Regardless though, I'm absolutely loving Jellyfin despite some of its rough edges, and my users are loving it too. I think I've considered myself 'migrated' from Plex to Jellyfin, but I'll still keep Plex around as backup for these 2 cases/issues I've mentioned, for now.
🔗 https://github.com/jellyfin/jellyfin-web/issues/4346
🔗 https://github.com/jellyfin/jellyfin/issues/13858
RE: https://sakurajima.social/notes/a6j9bhrbtq