Transcoding sections show decoders but no encoders

[DrivenByDemons 2]

Using a skylake CPU w/ quicksync and Debian 11. I installed the i965-ca-driver-shaders.deb per the Debian wiki to support encoding but no luck. I am pegging this CPU at times and it's frustrating me. I'm moving my setup from a windows machine to a proxmox linux VM and the i3 in the windows system worked great. This i5 not so much. Any help? I've read and searched and checked the charts and I know this skylake supports some encoding. I am ruling out my pci passthrough settings since emby can see the HD530 graphics for decodes.

Edited February 14, 2022 by DrivenByDemons

[Luke 42077]

Hi there, can you please attach the emby server log and hardware detection log file? Thanks.

[DrivenByDemons 2]

5 hours ago, Luke said:

Hi there, can you please attach the emby server log and hardware detection log file? Thanks.

Attached below...

hardware_detection-63780455023.txt embyserver.txt ffmpeg-transcode-cd56bc9d-a4b5-47d6-8c55-ac1ffe2990d8_1.txt

[Luke 42077]

Hi, did you check out our hardware acceleration setup guide?

https://support.emby.media/support/solutions/articles/44001160148-hardware-acceleration-overview

[DrivenByDemons 2]

I have read that guide, plus others, multiple times. It seems emby sees the hardware but just doesn't use it. 

[Luke 42077]

OK, there has been a lot of QuickSync related development in the 4.7 beta channel, so there's a good chance you'll see improvement once that is released.

[DrivenByDemons 2]

I've been experimenting and instead of running in a Debian VM I went ahead and installed Debian bare metal then emby on that. Everything in transcoding looks perfect now. I am going to experiment more with the VM setup as I have some time and am curious. Will post any solutions here. 

[Luke 42077]

Let us know how you get on. Thanks.

[DrivenByDemons 2]

So I came across another machine and tried setting up Emby under a proxmox VM and HW transcoding works fine. I set everything up exactly like before so it had to be something proxmox didn't like with the hardware. Keep in mind - on the old machine decoding worked fine in the VM but encoding didn't. When I installed Emby to that same machine bare metal with no VM everything worked. On this new machine everything works either way. IDK.

[Luke 42077]

On 2/20/2022 at 5:54 PM, DrivenByDemons said:

I've been experimenting and instead of running in a Debian VM I went ahead and installed Debian bare metal then emby on that. Everything in transcoding looks perfect now. I am going to experiment more with the VM setup as I have some time and am curious. Will post any solutions here. 

That would suggest to me that proxmox needs to be configured to allow emby access to the GPU , which you wouldn't have to deal with outside of the vm.

[DrivenByDemons 2]

On 4/8/2022 at 8:32 PM, Luke said:

That would suggest to me that proxmox needs to be configured to allow emby access to the GPU , which you wouldn't have to deal with outside of the vm.

Well, I set up the new machine exactly the same way as the old one so IDK. Also, if emby didn't have GPU access on the old machine, why would it see HW decoding but not HW encoding? Doesn't make sense. 

[Luke 42077]

Are you still intending to use the old one?

[DrivenByDemons 2]

On 4/17/2022 at 4:20 PM, Luke said:

Are you still intending to use the old one?

No. I'll set it up for something else.