With server 4.3.0.26 there are no "preferred hardware-encoders" listed

[mholin 23]

I've to report the same issue.

with server 4.2.xx I was able to use my GTX1050 for both decoding and encoding (h264).

now with server 4.3.0.26 there are no "preferred hardware-encoders" listed.

 

 

 

With 4.3 I had the hope that now even h265 encoding would be offered.

 

do you need some more information?

 

bye Michael

[Luke 42078]

Hi, yes please attach the emby server log and hardware detection log. thanks.

[softworkz 5066]

@@mholin - I've separated your post into a separate topic as your problem is totally different from the one in the topic where you posted.

 

Could you please post the hw detection log?

Edited November 23, 2019 by softworkz

[mholin 23]

I found this:

 

 

            "Level": 16,

            "Category": 0,

            "Message": "Driver does not support the required nvenc API version. Required: 9.0 Found: 8.1"

        },

        {

            "Level": 16,

            "Category": 0,

            "Message": "The minimum required Nvidia driver for nvenc is 390.77 or newer"

        },

 

I will check this. anyway here is my hardware dection log from today.

 

https://drive.google.com/open?id=1gvwtmtHL1YwLWzJogBlu_nFLjYrOdVM2

 

this is 170 KB, cannot insert this as plain text here.

[softworkz 5066]

Please zip it and attach the zip.

 

We have a tool that automatically downloads, unzips, formats and displays logs from forum attachments. This doesn't work with files stored elsewhere.

[Senna 368]

There is an extra delay apparently in Emby server 4.3.0.26, of approx. 30s, for the hardware encoders and decoders to appear, after Emby Server restart:

 

 

In 4.2.1.0 they appear in approx. 10s.

[softworkz 5066]

That's correct. It has changed because previously we hadn't been testing for support of 10bit color formats - which takes a little longer.

 

I think we should display a message there that detection is still in progress. @@Luke

[mholin 23]

I've got this issue fixed.

 

My latest geforce drivers where v417. 

Strangely they offered hardware encoding with the 4.2.0.21 server.

I installed today geforce DCH drivers v441.

 

maybe it's worth a hint, that beside logfile notice: "v390 is required", even V417 is not sufficient for server 4.3

 

with v441 now I got hardware encoding offered again in the servers transcoding section.

 

with a quick test, video is currently always encoded to h264 to android client app. h265 is not possible to force.

maybe this is an issue for later.

 

today I'm happy.

thanks

 

Michael

[softworkz 5066]

@@mholin - Thanks for the hint! I've just seen that our Windows builds of ffmpeg have accidentally been compiled for CUDA 9.0 instead of 8.1.

 

We'll fix this in a future update.