So just a quick TL;DR of the events going on, HW transcoding is broken atm on 24.04 and the latest Server release? Cause I’ve been getting Error 4294967283 consistently on the Desktop app for manually setting 4K down to 1080p or even 1080p down to 720p with a P2000. Not sure if my issue is related I’m just hoping this will shed some light on my confusion
Does that mean PMS will gain support for VVC video too (since that’s an addition in the 7.0 branch I believe)?
ffmpeg 7.0 is currently very unstable due to the multithreading support breaking quite a few things. Out current plan is to upgrade to 6.X but do it in such a way that it makes updating the transcoding MUCH easier in the future. This should make it easier to update to 7.0 when its in a better spot.
2 Likes
I think with that will come HW acceleration for raspberry pi which will be nice as well.
Will these changes also improve the functionality and consistency of the PLEX downloads feature? Since a updated version of FFMPEG will be used?
1 Like
An update was pushed to 22.04.4 LTS using the HWE stack that upgrades the kernel from 6.5.0.45.45~22.04.1 to 6.8.0-40.40~22.04.3
Using an N100 my system has been stable so far, is it safe to update?
I got the 6.8 HEADERS last night.
At this moment, it wants to clean up the older 6.5 kernels.
I would not be surprised to get the 6.8 kernel in 1-2 days (it’s due)
If you don’t mind, I recommend holding off on that 6.8 update until I’ve had a chance to check it.
It’s easy for me to downgrade (be the test-dummy 
)
This is what it offers me. I am waiting.
[chuck@lizum ~.2004]$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
linux-headers-6.5.0-44-generic linux-hwe-6.5-headers-6.5.0-44 linux-image-6.5.0-44-generic linux-modules-6.5.0-44-generic
linux-modules-extra-6.5.0-44-generic
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
busybox-initramfs busybox-static
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 standard LTS security updates
Need to get 1,196 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] ^Z
[1]+ Stopped sudo apt upgrade
[chuck@lizum ~.2005]$ uname -a
Linux lizum 6.5.0-45-generic #45~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 15 16:40:02 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
[chuck@lizum ~.2006]$
2 Likes
Sure, thanks for the swift reply and keep us posted.
I updated using sudo apt install --install-recommends linux-generic-hwe-22.04 and got 6.8. A quick test seemed to work.
Ah, they’re moving the pointers and phasing the rollout.
Yep, we’ll get 6.8 officially tomorrow.
I actually need 6.8.1 for DisplayPort over USB-C/USB4
My Ubuntu 22.04 upgraded from kenerl 6.5 to 6.8 yesterday as well. HW transcoding is still working with the iGPU on my i7-7700K. I’m running Plex within a docker container in a Ubuntu 22.04 VM on a Proxmox 8.2 host.
Curiosity if I may?
Why have a container (Docker) inside a VM?
You’ve got the abstraction from the VM.
You’ve added the next layer of abstraction by changing the runtime libraries which are inside the container.
Why not use the appropriate VM and run PMS internally as the native app?
I’m not challenging. I’m trying to understand why this is a common practice.
I run multiple VMs as I need to run Windows Server, Ubuntu and Xpenology on the one host machine.
I find docker containers much easier to manage for my apps with respect to ease of updating, resolving conflicting library dependencies, etc.
Having the containers all within the same VM is easier for me to manage and less resource intensive than running separate VMs for each app. Also, keeping Plex in the same VM as my file server means that I don’t need to set up network shares for library access.
It’s recommended practice for VM hosts just to do that, and run applications within the VM guests.
If I didn’t need to run Windows Server and Xpenology on the same machine I would just run Ubuntu baremetal and retain Plex in a docker container.
My homelab structure is:
Proxmox Server 1
- Windows Sever 2022 VM - Primary Domain Controller
- Xpenology VM - CCTV NVR
- Ubuntu 22.04 VM - File server and docker (Plex, Unifi, Deluge, sabNZBd, Sonarr, Radarr, etc.)
Proxmox Server 2
- pfSense firewall VM
- Windows Sever 2022 VM - Backup Domain Controller
24.04.1 pushed back to end of the month.
Yup.
Just tested on my testbed.
SVR1 on 22.04.4, k6.5 and plex1.40.2 all HW transcode on 8100 cpu good to go.
SVR3 backup updated 22.04.4, k6.5 to k6.8 on plex1.40.2 on 7400 cpu. All hw transcode broken.
Reverting backup to 6.5 and locking it there.
Followup, gathered my notes for reverting to 6.5 kernel and setup a plan… but since it’s easy fish to fry with docker…, updated the docker just to see and success.
Ubuntu Desktop 22.04.4LTS with HWE Kernel 6.5 and earlier. Needs to be frozen at plex 1.40.2.
22.04 updates to HWE Kernel 6.8! Plex 1.40.5 is working great on all systems across 3 gpu variety. All 3 doing HW transcode and HW tonemap.
SVR1 8100 igpu and ARC gpu.
SVR3 7400 igpu and ARC gpu.
SVR3 will continue with weekly updates and compose set to
image: plexinc/pms-docker:latest
SVR1 will continue with delayed updates and plex compose set to
image: plexinc/pms-docker:1.40.5.8854-f36c552fd
@ChuckPa did you verify this at the end?
My server with Ubuntu 22.04 with kernel 6.8 and PMS version 1.40.5.8854 also works great including HW transcode and HW tonemap.
4 Likes
Good to know. I wanted to update as well and now it doesn’t list anymore kernel 6.8 as available update, very weird
