May 29, 2024 22:27:56.658 [131183162260280] DEBUG - [Req#20190/Transcode/89a1f57c911d4332-com-plexapp-android] TPU: hardware transcoding: enabled, but no hardware decode accelerator found
as long as mine is working (or not) the same way yours is, I’m comfy.
also decided to consider a bare metal plex server to get rid of all these headaches. i3-14100 is pretty darn cheap right now and so are the mobos that support it.
Starting to drift well beyond the original issues, but I can’t resist asking.
Do you not think an i3-14100 and an ASRock B760M mobo would be sufficient for replacing my current i7-8700 and Asrock H370M mobo?
The i7 will always outrun the i3 . That’s important for audio transcode. it’s also important for basic server software operation (ingest media, etc)
Unless you have AV1 media, you don’t gain anything by upgrading beyond the CoffeeLake.
It comes down to
a. What types of media do you have / curate
b. What types of media do you plan on for the future.
Returning to the thread topic, I have your case and that of another.
The other user has a Shield Pro 2019 which stutters.
It defies explanation. “Speedtest” results show one thing but every bone in my body is screaming “Network” because I can sit here and not have a problem with DirectPlay of 187 Mbps video files to the Shield. (GeminiMan BluRay direct fro the disc)
Ok. So maybe I should just put PMS back on the metal and leave everything else in their containers.
Regarding the network, if it helps…I’m on an all TP-Link network running the Omada controller software. I have 2 TP-Link EAP610 Access Points (Wi-Fi 6 AX1800), an OC200 hardware controller, and a few Omada enabled managed switches. I’m not running any QoS. My router is a Firewalla Gold SE.
I use LXC instead of docker (virtualizes the distro instead of just the app). This allows me to create a ‘Media’ container which runs all my media services with their native app installations which auto update at the OS level versus docker image level… all in a single host namespace.
LXC also allows me to develop and test packaging for the different distros without needing a full-up VM
And this is from my TV, which is where the trouble started and “inspired” me to go out and get an onn 4K pro to play with. Connected via ethernet adapter to USB3.
Now that makes more sense. 400 Mbps from the server → player.
Given things we’ve learned today,
The Intel i915 driver is the root of the problem. It will be fixed in the 6.9 kernel. We don’t know if Ubuntu and other distros will include those kernel patches / update the kernel before Ubuntu 24.10 is due to release (hope it gets the kernel update / patches)
Intel Compute Runtime made an internal change. We just updated our software to work with their update. I’m waiting for another Engineering build to see what the impact of our changes is. So far, things look promising. I was reliably getting HW transcoding from file to file.
I know we’re close here.
I also know the Android folks have a release coming to address other issues (Collections / Playlists) but am not briefed on those details.
Makes sense. I have no problem sticking with 22.04.4 LTS for a while. I just had hoped the LTS would have avoided some of these probs with the kernels.
Funny thing re: Android. I’m an all Android house and nobody has mentioned any issues with the collections or playlists. 3 android tablets, 2 android TV, 3 android phones, and a bunch of Chromecasts. Not a peep.
Any thoughts on migrating to plain ol’ Debian? It uses an older kernel that worked and gets much less frequent updates. Seems less likely that things will break for no reason.
Migrating from distro to distro depends on two things:
Did you partition the installation drive to isolate the boot and root partitions
(saving /home)
Where’s the current Plex installation living? on /var/lib or have you customized it.
If you’ve paritioned the installation/boot drive appropriately,
you can save the critical info (your override.conf, hosts file, installed packages list, etc) and then reinstall and recustomize.
If not, a little bit of tar and chown work can restore PMS pretty easily on any new distro.
I can change from distro/version to anything else within about 30 minutes and have it both customized and PMS running in that time.
If you want to change, I’ll help you.
Re Android:
I can’t replicate the problems either.
Our Engineering team does have a change coming for Playlists & Collections.
I’ll learn more as it gets released
The current instance of PMS is in a Docker container, but I do have the pre-docker instance files sitting in /var/lib if they were handy.
I’ve never had much success restoring my server. Always running into claiming issues and other nonsense (aka user error). And if I were to switch disros for more stability, I’d probably be inclined to just rebuild from scratch with everything fresh and clean and no baggage. Was more just curious about the stability of Debian’s packages and kernel and whether or not it would actually address/solve any of the issues I’ve been running into.
