fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.8K
active users

#ersatztv

0 posts0 participants0 posts today
Mika<p>I'm so puzzled by this error that I receive from time to time when attempting to stream from my <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a> container running on <a href="https://sakurajima.social/tags/Docker" rel="nofollow noopener" target="_blank">#Docker</a>/<a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a>'s <a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener" target="_blank">#LXC</a> container, which I've passed through my <a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener" target="_blank">#AMD</a><span> Ryzen 5 5600G iGPU for hardware transcoding:<br></span></p><pre><code>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!</code></pre><span><br>I've seen it on </span><a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a><span> too before during my testing, albeit very rarely. I've googled it many times before trying to find the cause or what it meant, but never really got an actual answer for it (that I understood anyway). Is it perhaps obvious to anyone here?<br><br></span>🔗 <a href="https://github.com/ErsatzTV/ErsatzTV/issues/1997" rel="nofollow noopener" target="_blank">https://github.com/ErsatzTV/ErsatzTV/issues/1997</a><span><br><br></span>🔗 <a href="https://github.com/ErsatzTV/ErsatzTV/issues/1350" rel="nofollow noopener" target="_blank">https://github.com/ErsatzTV/ErsatzTV/issues/1350</a><p></p>
Mika<p>I have finally caved in and dove into the rabbit hole of <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a> Container (<a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener" target="_blank">#LXC</a>) on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a><span> 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.<br><br>I now have a </span><a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a> and <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a> setup running on LXCs with working iGPU passthrough of my server's <a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener" target="_blank">#AMD</a> Ryzen 5600G APU. My <a href="https://sakurajima.social/tags/Intel" rel="nofollow noopener" target="_blank">#Intel</a> <a href="https://sakurajima.social/tags/ArcA380" rel="nofollow noopener" target="_blank">#ArcA380</a> 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 <a href="https://sakurajima.social/tags/Kubernetes" rel="nofollow noopener" target="_blank">#Kubernetes</a>, <a href="https://sakurajima.social/tags/RKE2" rel="nofollow noopener" target="_blank">#RKE2</a><span> cluster on LXC nodes instead of VMs - and if that's viable or perhaps better.<br><br>Anyway, I've updated my </span><a href="https://sakurajima.social/tags/Homelab" rel="nofollow noopener" target="_blank">#Homelab</a> Wiki with guides pertaining LXCs, including creating one, passing through a GPU to multiple unprivileged LXCs, and adding an <a href="https://sakurajima.social/tags/SMB" rel="nofollow noopener" target="_blank">#SMB</a><span> share for the entire cluster and mounting them, also, on unprivileged LXC containers.<br><br></span>🔗 <a href="https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/proxmox.md#linux-containers-lxc" rel="nofollow noopener" target="_blank">https://github.com/irfanhakim-as/homelab-wiki/blob/master/topics/proxmox.md#linux-containers-lxc</a></p>
Mika<p>Anybody know the cause to this error on <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a> when tuning into a hardware-accelerated stream from <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a> using an <a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener" target="_blank">#AMD</a><span> iGPU?<br></span></p><pre><code>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.</code></pre><span><br></span>🔗 <a href="https://github.com/ErsatzTV/ErsatzTV/issues/1350" rel="nofollow noopener" target="_blank">https://github.com/ErsatzTV/ErsatzTV/issues/1350</a><p></p>
Mika<p>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 <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a>'s <code>xml</code> configs for any wrong/old paths/values, and lastly, the <a href="https://sakurajima.social/tags/SQLite" rel="nofollow noopener" target="_blank">#SQLite</a> DBs themselves which had old paths as well - most of which were easy to fix as they're <code>text</code> values, but some were (JSON) <code>blob</code>s, using the same extension on <a href="https://sakurajima.social/tags/VSCode" rel="nofollow noopener" target="_blank">#VSCode</a>, 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 <code>meta.json</code><span> files of all plugins I've installed to point to the new path to their logos.<br><br>Now my Jellyfin </span><a href="https://sakurajima.social/tags/LinuxServer" rel="nofollow noopener" target="_blank">#LinuxServer</a>.io container sitting in an unprivileged (<a href="https://sakurajima.social/tags/Debian" rel="nofollow noopener" target="_blank">#Debian</a> <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a>) <a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener" target="_blank">#LXC</a> container on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a> is set up with hardware transcoding using the <a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener" target="_blank">#AMD</a> Ryzen 5 5600G onboard iGPU (cos I'm getting impatient in waiting for my <a href="https://sakurajima.social/tags/Intel" rel="nofollow noopener" target="_blank">#Intel</a> <a href="https://sakurajima.social/tags/ArcA380" rel="nofollow noopener" target="_blank">#ArcA380</a> to arrive). I'll update my <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a> 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 <a href="https://sakurajima.social/tags/Plex" rel="nofollow noopener" target="_blank">#Plex</a><span>) 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.<br><br>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.<br><br></span>🔗 <a href="https://github.com/jellyfin/jellyfin-web/issues/4346" rel="nofollow noopener" target="_blank">https://github.com/jellyfin/jellyfin-web/issues/4346</a><span><br><br></span>🔗 <a href="https://github.com/jellyfin/jellyfin/issues/13858" rel="nofollow noopener" target="_blank">https://github.com/jellyfin/jellyfin/issues/13858</a><span><br><br>RE: </span><a href="https://sakurajima.social/notes/a6j9bhrbtq" rel="nofollow noopener" target="_blank">https://sakurajima.social/notes/a6j9bhrbtq</a></p>
Mika<p>Bruh, I might've wasted my time learning how to passthrough a GPU to an <a href="https://sakurajima.social/tags/LXC" rel="nofollow noopener" target="_blank">#LXC</a> container on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a> (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 <i>magic</i> <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a> <i>fu</i><span> 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.<br><br>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 </span><a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener" target="_blank">#AMD</a> iGPU (until my <a href="https://sakurajima.social/tags/Intel" rel="nofollow noopener" target="_blank">#Intel</a> <a href="https://sakurajima.social/tags/ArcA380" rel="nofollow noopener" target="_blank">#ArcA380</a> GPU arrives) and see if the root user + service user on the container could access it/use it for transcoding on <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a>/<a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a>, and 2) Add a SMB/CIFS storage on the Proxmox Datacenter, tho my <a href="https://sakurajima.social/tags/NAS" rel="nofollow noopener" target="_blank">#NAS</a><span> 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.<br><br></span><a href="https://sakurajima.social/tags/Homelab" rel="nofollow noopener" target="_blank">#Homelab</a> folks who have done this, feel free to give some tips or wtv if you've done this before!</p>
Mika<p>Update 0.2.1 for Flex 🎉<span><br><br>Added </span><a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a> support - a platform where you could create "TV" channels that broadcast your own media to your streaming platform i.e. <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a> or <a href="https://sakurajima.social/tags/Plex" rel="nofollow noopener" target="_blank">#Plex</a><span> in a "traditional" TV format, with programme scheduling, guides, and all.<br><br>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.<br><br></span>🔗 <a href="https://github.com/irfanhakim-as/charts/pull/141" rel="nofollow noopener" target="_blank">https://github.com/irfanhakim-as/charts/pull/141</a><span><br><br>RE: </span><a href="https://sakurajima.social/notes/a69b2hb04o" rel="nofollow noopener" target="_blank">https://sakurajima.social/notes/a69b2hb04o</a></p>
Mika<p>Figuring out how to passthrough an <a href="https://sakurajima.social/tags/AMD" rel="nofollow noopener" target="_blank">#AMD</a> iGPU to a <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a> VM on <a href="https://sakurajima.social/tags/Proxmox" rel="nofollow noopener" target="_blank">#Proxmox</a> 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 <a href="https://sakurajima.social/tags/homelab" rel="nofollow noopener" target="_blank">#homelab</a> wiki on how to do it. For now though, I think I can live without transcoding on <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a> or <a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a> :))</p>
Mika<p><a href="https://sakurajima.social/tags/ErsatzTV" rel="nofollow noopener" target="_blank">#ErsatzTV</a> is super cool and something I've always been eyeing on, and I managed to get it working on my <a href="https://sakurajima.social/tags/Kubernetes" rel="nofollow noopener" target="_blank">#Kubernetes</a> cluster, and hooked it up to <a href="https://sakurajima.social/tags/Jellyfin" rel="nofollow noopener" target="_blank">#Jellyfin</a> - 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.</p>
Brian Enigma<p>I made some TV stations! <a href="https://xoxo.zone/tags/iptv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iptv</span></a> <a href="https://xoxo.zone/tags/ersatztv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ersatztv</span></a><br>(The music video channel even plays old <a href="https://xoxo.zone/tags/mtv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mtv</span></a> bumpers between songs.)</p>
So, taking some time tonight to give #Jellyfin a try over #Plex. Still waiting on my libraries to populate. If it's good enough for my needs, I'll be happy to drop the monthly Plex Pass charge. Already seems to work quite well with my fake cable TV setup with #ErsatzTV, so I'm hopeful the rest of it goes well.

Interesting to see Jellyfin also supports books. Hoping we can see the podcast support eventually that Plex dropped last year.

#media #selfhosted #linux
social.zerojay.comAkkoma