proxmox 7.1, unable to access render128 in lxc with vainfo

Jul 28, 2017
135
2
38
so you’re using an image of the full distro with Xorg? Or using the base OS image and then jellyfin via container or running ffmpeg directly?

What is your CPU?

Have you tried the latest mesa from here? These don’t work for me but they also don’t crash the system or cause errors in dmesg.
Sorry, I've not been anywhere near clear with my posts, due to only having a few hours in the evenings to test (stealing my wife's monitor and keyboard)

First i tried a lxc container in proxmox,
then on the proxmox host its self.
New install of Ubuntu 21.10 on bare metal and install jellyfin.

The CPU is 5700G on a ASUS MB

I'll try and give the link a guide Friday (gotta migrate my Home assistant from Ubuntu 18.04, python 3.7, mariadb 10.1 tonight)
 

paulmorabi

Member
Mar 30, 2019
74
8
13
42
Sorry, I've not been anywhere near clear with my posts, due to only having a few hours in the evenings to test (stealing my wife's monitor and keyboard)

First i tried a lxc container in proxmox,
then on the proxmox host its self.
New install of Ubuntu 21.10 on bare metal and install jellyfin.

The CPU is 5700G on a ASUS MB

I'll try and give the link a guide Friday (gotta migrate my Home assistant from Ubuntu 18.04, python 3.7, mariadb 10.1 tonight)

No worries, I know what it's like to debug this.

So, first thing is I'm using Proxmox 7.1 with a 4650G so the generation and models of our AMD processors are different. I do get stable video stream decoding running Frigate in LXC. With Jellyfin, using the latest mesa libraries, I get an error (as per my previous link to issue) but not a hardware crash/dmesg error. I'd expect you'll have a better chance of getting this working with your 5700G as its a much more popular and available processor.

When you ran Jellyfin on the proxmox host did you use docker? And did you use docker also when you used Ubuntu 21.10?

And as far as container images go, I've been using the Linuxserver.io container image with the AMD mod. When I last debugged this (end November) the official Jellyfin image was using an Ubuntu based image with an older mesa library version. You could try the linuxserver.io image or upgrade the official image to kisak's repo mesa version in the container. If you try the latter, this is the steps I used to get decoding working in Frigate (and thankfully the author added updated libraries to the default container image).

I spent an inordinate amount of time trying to get Jellyfin working, raised issues in mesa and in Jellyfin but didn't get very far. Eventually I resolved to test it every few months to see if anything changes. There are as lot of avenues you could go down in terms of kernel, mesa library and ffmpeg. From what I understand, the 5.8+ kernels support amdgpu well so the problem likely resides in mesa and/or ffmpeg and will probably improve over time as support for these mature. In the meantime, on the occasion I do need transcoding, the CPU is strong enough to handle it. The other lesson I took from this is if you really need video encoding/decoding, it's just easier to get an intel CPU. Outside of other factors, their CPU's with integrated graphics are awesome for this.
 
Jul 28, 2017
135
2
38
Fresh install of proxmox, all updates and amd-microcode installed.
Fresh container of ubuntu 20.04 (from the normal proxmox container location)
Installed the latest stable jellyfin using the normal ubuntu guide they have.

installed these mesa drivers, from testing
https://itsfoss.com/install-mesa-ubuntu/
Code:
sudo add-apt-repository ppa:oibaf/graphics-drivers

and so far it has worked fine SO FAR (with 6 cores being passed through, for the 10-bit hardware decode being off)
Tested different videos, SDR HDR 10bit, HDR 8bit, 30FPS 60FPS

VAAPI is being used with these options
Screenshot at 2022-01-14 22-00-44.png


I will keep testing and if i get brave i'll enable 10-bit hardware decoding
 

paulmorabi

Member
Mar 30, 2019
74
8
13
42
Fresh install of proxmox, all updates and amd-microcode installed.
Fresh container of ubuntu 20.04 (from the normal proxmox container location)
Installed the latest stable jellyfin using the normal ubuntu guide they have.

installed these mesa drivers, from testing
https://itsfoss.com/install-mesa-ubuntu/
Code:
sudo add-apt-repository ppa:oibaf/graphics-drivers

and so far it has worked fine SO FAR (with 6 cores being passed through, for the 10-bit hardware decode being off)
Tested different videos, SDR HDR 10bit, HDR 8bit, 30FPS 60FPS

VAAPI is being used with these options
View attachment 33274


I will keep testing and if i get brave i'll enable 10-bit hardware decoding

Awesome! Congratulations!

So, just to confirm, what packages did you install from the ppa:eek:ibaf/graphics-drivers repo? And you did this with an lxc/d container? I will give this a try also!
 
Jul 28, 2017
135
2
38
Thats correct. Just that PPA on the lxc container, nothing more than microcode on the host
https://wiki.debian.org/Microcode#Debian_11_.22Bullseye.22_.28stable.29
Code:
# CPU Microcode
deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free


I also just install the smu power stuff as well and did some more testing and it's stable. Tho again i've not enabled the 10 bit option in jellyfin yet.
 

paulmorabi

Member
Mar 30, 2019
74
8
13
42
Thats correct. Just that PPA on the lxc container, nothing more than microcode on the host
https://wiki.debian.org/Microcode#Debian_11_.22Bullseye.22_.28stable.29
Code:
# CPU Microcode
deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free


I also just install the smu power stuff as well and did some more testing and it's stable. Tho again i've not enabled the 10 bit option in jellyfin yet.

What is the SMU stuff? Did you add this to the host or to the container?
 

paulmorabi

Member
Mar 30, 2019
74
8
13
42
What is the SMU stuff? Did you add this to the host or to the container?

I tried the mesa libraries from the repo you listed above and transcoding worked for a while before crashing:

Code:
[4264928.290153] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.290448] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3f4000 from IH client 0x12 (VMC)
[4264928.290704] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00343851
[4264928.291020] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: VCN (0x1c)
[4264928.291308] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x1
[4264928.291590] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.291855] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x5
[4264928.292156] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.292462] amdgpu 0000:03:00.0: amdgpu:    RW: 0x1
[4264928.292782] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.293139] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3f5000 from IH client 0x12 (VMC)
[4264928.293521] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[4264928.293930] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: MP1 (0x0)
[4264928.294302] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264928.294696] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.295192] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x0
[4264928.295570] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.295960] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264928.296395] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.296843] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3f6000 from IH client 0x12 (VMC)
[4264928.297298] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[4264928.297772] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: MP1 (0x0)
[4264928.298247] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264928.298721] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.299209] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x0
[4264928.299673] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.300137] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264928.300640] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.301196] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3f7000 from IH client 0x12 (VMC)
[4264928.301755] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[4264928.302312] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: MP1 (0x0)
[4264928.302926] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264928.303505] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.304070] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x0
[4264928.304646] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.305256] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264928.305890] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.306542] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3f8000 from IH client 0x12 (VMC)
[4264928.307316] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[4264928.308026] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: MP1 (0x0)
[4264928.308686] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264928.309339] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.310024] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x0
[4264928.310754] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.311520] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264928.312273] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.313072] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3f9000 from IH client 0x12 (VMC)
[4264928.313889] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[4264928.314698] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: MP1 (0x0)
[4264928.315538] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264928.316367] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.317200] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x0
[4264928.318058] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.318901] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264928.319748] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.320664] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3fa000 from IH client 0x12 (VMC)
[4264928.321541] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[4264928.322450] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: MP1 (0x0)
[4264928.323379] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264928.324279] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.325184] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x0
[4264928.326089] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.327062] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264928.328014] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.329005] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3fb000 from IH client 0x12 (VMC)
[4264928.330016] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[4264928.331315] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: MP1 (0x0)
[4264928.332371] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264928.333424] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.334487] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x0
[4264928.335599] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.336619] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264928.337676] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.338881] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3fc000 from IH client 0x12 (VMC)
[4264928.340033] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00303831
[4264928.340977] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: VCN (0x1c)
[4264928.341875] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x1
[4264928.342793] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.343684] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x3
[4264928.344555] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.345430] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264928.346313] amdgpu 0000:03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32770, for process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356)
[4264928.347241] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000080010a3fd000 from IH client 0x12 (VMC)
[4264928.348133] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00000000
[4264928.349028] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: MP1 (0x0)
[4264928.350039] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264928.350893] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264928.351656] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x0
[4264928.352379] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264928.353118] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264938.529388] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=54934, emitted seq=54935
[4264938.530556] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356
[4264938.531370] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
[4264938.734501] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x00000001 != 0x00000002
[4264938.914929] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 0x00000140 != 0x00000100
[4264939.091071] [drm] Register(0) [mmUVD_RBC_RB_RPTR] failed to reach value 0x00000320 != 0x00000260
[4264939.267847] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x00000001 != 0x00000002
[4264939.277201] [drm] free PSP TMR buffer
[4264939.305147] amdgpu 0000:03:00.0: amdgpu: MODE2 reset
[4264939.305578] amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
[4264939.305696] [drm] PCIE GART of 1024M enabled.
[4264939.305697] [drm] PTB located at 0x000000F400900000
[4264939.305833] [drm] PSP is resuming...
[4264939.325571] [drm] reserve 0x400000 from 0xf4ff800000 for PSP TMR
[4264939.408615] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
[4264939.417248] amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
[4264939.417253] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[4264939.417256] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
[4264939.418140] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
[4264939.582808] [drm] kiq ring mec 2 pipe 1 q 0
[4264939.583544] [drm] DMUB hardware initialized: version=0x01010019
[4264939.661475] gmc_v9_0_process_interrupt: 2 callbacks suppressed
[4264939.661480] amdgpu 0000:03:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:16 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[4264939.661490] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000000000000000 from IH client 0x12 (VMC)
[4264939.661495] amdgpu 0000:03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00003A20
[4264939.661497] amdgpu 0000:03:00.0: amdgpu:    Faulty UTCL2 client ID: VCNU (0x1d)
[4264939.661500] amdgpu 0000:03:00.0: amdgpu:    MORE_FAULTS: 0x0
[4264939.661502] amdgpu 0000:03:00.0: amdgpu:    WALKER_ERROR: 0x0
[4264939.661504] amdgpu 0000:03:00.0: amdgpu:    PERMISSION_FAULTS: 0x2
[4264939.661506] amdgpu 0000:03:00.0: amdgpu:    MAPPING_ERROR: 0x0
[4264939.661508] amdgpu 0000:03:00.0: amdgpu:    RW: 0x0
[4264939.838533] amdgpu 0000:03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring vcn_enc0 test failed (-110)
[4264939.838640] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <vcn_v2_0> failed -110
[4264939.838733] amdgpu 0000:03:00.0: amdgpu: GPU reset(1) failed
[4264939.838905] amdgpu 0000:03:00.0: amdgpu: GPU reset end with ret = -110
[4264949.995202] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=54934, emitted seq=54935
[4264949.995368] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process ffmpeg pid 2319355 thread ffmpeg:cs0 pid 2319356
[4264949.995502] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!

I didn't get to trying 10 bit. Great to see it works but also its unstable still.
 

paulmorabi

Member
Mar 30, 2019
74
8
13
42

Thanks for this. I installed both and you are correct, this makes the transcoding much more stable. I got one "retry page fault" in dmesg that recovered itself whereas previously a reboot would have been required.

I enabled 10bit and it throws an ffmpeg error on a 4k file.

Thanks so much for finding this and sharing.
 
Last edited:
Jul 28, 2017
135
2
38
Thanks for this. I installed both and you are correct, this makes the transcoding much more stable. I got one "retry page fault" in dmesg that recovered itself whereas previously a reboot would have been required.

I enabled 10bit and it throws an ffmpeg error on a 4k file.

Thanks so much for finding this and sharing.
You gave me the idea to try the beta/bleeding edge drivers.

with HEVC Main 10 60fps i have to allow the container 15 threads through to get it to transcode to 1080 10Mbps, and even then it can out play the transcode buffer.

Hopefully it will just get better from here as mesa gets updated.
 

paulmorabi

Member
Mar 30, 2019
74
8
13
42
You gave me the idea to try the beta/bleeding edge drivers.

with HEVC Main 10 60fps i have to allow the container 15 threads through to get it to transcode to 1080 10Mbps, and even then it can out play the transcode buffer.

Hopefully it will just get better from here as mesa gets updated.

Yeah, fingers crossed it gets better over time. I've done quite a bit more testing and I've noticed a few things:

* The SMU driver is really important. Without this, the iGPU crashes regardless of mesa versions. I've seen the odd page fault in dmesg but no crashing. Hopefully this makes it into the kernel eventually.
* With the SMU driver, mesa 21.3+ (such as from kisak) works but with errors transcoding some files.
* With the latest build from the oibaf ppa (looks like a nightly build from git, pre-release of mesa 22) everything seems to transcode fine.
* enabling 10bit transcoding leads to ffmpeg errors for me.

When mesa 22 is released and makes it through to the different repos, the experience of getting this up and running should be much easier.
 
  • Like
Reactions: James Crook
Jul 28, 2017
135
2
38
Just done updates to the container no change, still get this error with hardware HDR 10-bit enabled

Code:
[Parsed_tonemap_vaapi_1 @ 0x557553e70640] VAAPI driver doesn't support HDR
[Parsed_tonemap_vaapi_1 @ 0x557553e70640] Failed to configure output pad on Parsed_tonemap_vaapi_1

If i disable "VPP tone mapping" and "tone mapping" it will use hardware for transcoding, tho it looks very washed out (makes sense as it's not remapping the HDR to SDR)


Just found this on Reddit about the upcoming release
https://www.reddit.com/r/jellyfin/comments/rwb4h1/the_fourth_alpha_for_1080_is_up_please_read_and/

Note that this release includes our Tonemapping HWA improvements. To take full advantage of this, you will need to upgrade Jellyfin FFMPEG to version 4.4.1
tho i'm already running 4.4.1 jellyfin FFmpeg, so maybe they changed some options that are being passed through, rather than changes to FFMPEG it's self.
 
Last edited:
Jul 28, 2017
135
2
38
Tested last night with a RX560 and then Ryzen 5 5700G on POP_OS 21.10
installed Kodi (19.1 was in the pop repo) and both worked fine showing hw decode h265 10bit HDR content and playing it back on a 1080 display. Tho the 5700G got very sutterey/jumpy (didn't say it was dropping of skipping frames) when trying to play back the 400Mbps Jellyfish h265 10bit file.

Think it's just a waiting game now till the new jellyfin comes out, as they have new options in the hardware playbackup section that might help.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!