Emby server as Proxmox LXC AMD 5600g iGPU cannot do hardware encode

[ZogTheDragon 0]

I setup LXC Emby server and followed other guides to successfully passthrough iGPU from AMD 5600g's to the LXC.

Emby server can detect all the encoder/decoder without a problem so I don't think it is permission issue or similar. However, when it transcodes the videos I took from my iPhone, it can only do hardware decoding, but cannot do encoding, which results in choppy playback.

Although I can see some other videos taken by the same phone (but in "ProRes" format) can be somehow decoded/encoded using HW.

I looked at the log where it fails to do hardware encoding, and it looks like the following is the reason;

NoMatch Encoder does not support the minimum requied encoding level (AvcLevel52)

I attached logs for both cases - can you please help?

ffmpeg-transcode-d50f009e-1fd2-400f-b142-8fecc86e320c_1.txt ffmpeg-transcode-979b196e-b38c-4331-99a4-090d4d764cad_1.txt

[ZogTheDragon 0]

Also attaching hardware detection log..

hardware_detection-63865495965.txt

[ZogTheDragon 0]

Please anyone can help...?

[ZogTheDragon 0]

I have this post: 

, but didn't get any response, so re-posting here just in case.

I setup LXC Emby server and followed other guides to successfully passthrough iGPU from AMD 5600g's to the LXC.

Emby server can detect all the encoder/decoder without a problem so I don't think it is permission issue or similar. However, when it transcodes the videos I took from my iPhone, it can only do hardware decoding, but cannot do encoding, which results in choppy playback.

Although I can see some other videos taken by the same phone (but in "ProRes" format) can be somehow decoded/encoded using HW.

I looked at the log where it fails to do hardware encoding, and it looks like the following is the reason;

NoMatch Encoder does not support the minimum requied encoding level (AvcLevel52)

I attached logs for both cases - can you please help?

ffmpeg-transcode-d50f009e-1fd2-400f-b142-8fecc86e320c_1.txt ffmpeg-transcode-979b196e-b38c-4331-99a4-090d4d764cad_1.txt hardware_detection-63865495965.txt

[Luke 42077]

HI, I would try resetting your customizations back to defaults and see how things compare:

Warning EncoderParametersH264Vaapi.CompressionLevel: Original:  Actual: 4
Warning EncoderParametersH264Vaapi.BitrateMode: Original: Classic Actual: Vbr
Warning EncoderParametersH264Vaapi.ProfileLimit: Original:  Actual: AvcProfileMain

 

[ZogTheDragon 0]

Hi,

Thanks for your reply.

I've restored default setting as far as I can see but getting the same software encoding (attached log)

While I'd love to see hardware transcoding working as I intended, I also stumbled upon this post:

, which seems to fit my situation as well (seeing this issue with macOS Safari and Chrome) - is there a fix for this macOS issue?

 

ffmpeg-transcode-39457486-169a-47c2-88a8-246c632fcf2f_1.txt

[hoonlight 18]

 

 

FYI I provided logs again yesterday for a related issue.

Edited October 30, 2024 by hoonlight

[ZogTheDragon 0]

@Luke  have you had any chances to take a look?

I also saw the other thread @hoonlightshared which is relevant and would solve my issue of laggy playback without utilising HW, but I would also like HW en/decoding to work as intended or at least want to know if it isn’t a supported scenario.

Thanks.

 

[hoonlight 18]

14 hours ago, ZogTheDragon said:

@Luke  have you had any chances to take a look?

I also saw the other thread @hoonlightshared which is relevant and would solve my issue of laggy playback without utilising HW, but I would also like HW en/decoding to work as intended or at least want to know if it isn’t a supported scenario.

Thanks.

 

Thankfully, my issue with the transcoding seems to have finally been resolved in the 4.9.0.31 beta. I can't speak for your issue, of course, but you might want to try the new beta.