I'm so puzzled by this error that I receive from time to time when attempting to stream from my #ErsatzTV container running on #Docker/#Proxmox's #LXC container, which I've passed through my #AMD Ryzen 5 5600G iGPU for hardware transcoding:

HLS process for channel 101 has terminated unsuccessfully with exit code 137: amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.
If they do, bad things may happen!

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

Anybody know the cause to this error on #ErsatzTV when tuning into a hardware-accelerated stream from #Jellyfin using an #AMD iGPU?

HLS process for channel 101 has terminated unsuccessfully with exit code 137: amdgpu: os_same_file_description couldn't determine if two DRM fds reference the same file description.

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 xml configs 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're text values, 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 update meta.json files 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

Bruh, I might've wasted my time learning how to passthrough a GPU to an #LXC container on #Proxmox (as well as mount a SMB/CIFS share) and write up a guide (haven't been able to test yet, cept with the latter) - all by doing some seemingly magic #Linux fu with some user/group mappings and custom configs, if it turns out that you could actually achieve the same result just as easily graphically using a standard wizard on PVE.

It's 4am, I'll prolly try to find time later during the day, or rather evening (open house to attend at noon), and try using the wizard to 1) Add a device passthrough on an LXC container for my #AMD iGPU (until my #Intel #ArcA380 GPU arrives) and see if the root user + service user on the container could access it/use it for transcoding on #Jellyfin/#ErsatzTV, and 2) Add a SMB/CIFS storage on the Proxmox Datacenter, tho my #NAS is also just a Proxmox VM in the same cluster (not sure if this is a bad idea?) and see if I could mount that storage to the LXC container that way.

#Homelab folks who have done this, feel free to give some tips or wtv if you've done this before!

Update 0.2.1 for Flex

Added #ErsatzTV support - a platform where you could create "TV" channels that broadcast your own media to your streaming platform i.e. #Jellyfin or #Plex in a "traditional" TV format, with programme scheduling, guides, and all.

I've been wanting to have this for a really long time and it's good to finally have it - eventho I've to rely on CPU transcoding for now, which surprisingly works pretty well with no buffering etc. tho I suspect I couldn't get more than 1 client streaming concurrently lol.

https://github.com/irfanhakim-as/charts/pull/141

RE: https://sakurajima.social/notes/a69b2hb04o

Figuring out how to passthrough an #AMD iGPU to a #Linux VM on #Proxmox is just..... something not within my capacity atm lol. Maybe someday if I happen to have an additional test hardware I could potentially fuck with without screwing my main environment, and if I manage that then I could update my #homelab wiki on how to do it. For now though, I think I can live without transcoding on #Jellyfin or #ErsatzTV :))

#ErsatzTV is super cool and something I've always been eyeing on, and I managed to get it working on my #Kubernetes cluster, and hooked it up to #Jellyfin - but now kinda wondering if it's possible to "avoid" transcoding and have it running like it would on Jellyfin, through Direct Play, if you'd used the appropriate client cos rn, even tho it's hooked to Jellyfin, it's certainly transcoding - when the same media file would play directly just fine if I'd just consume it from the Jellyfin media library directly.

I made some TV stations! #iptv #ersatztv
(The music video channel even plays old #mtv bumpers between songs.)

Anyway, what I was trying to post is that I started tinkering with #ErsatzTV, which allows you to #selfhost IPTV. I made a channel with old anime and game openings.

Some really hit in the kokoro. I mean, just look how gorgeous this 16mm film recording is. Love that shot at 01:18.
https://www.youtube.com/watch?v=322WvZ3e2zs

Finally got all the channels I wanted configured on #ersatztv.

Now to plan for rotations.

@teamtuck I really like the idea of #ersatztv, but found I just never used the channels and always went to the library anyway.

My amazing sexy Friday night is configuring #ErsatzTV on my #ubuntu server to add "live" TV channels to my #Plex server.

It's fun.

Really.