Jump to content
MisterAngelus

new nvidia drivers issue

Recommended Posts

MisterAngelus
Posted (edited)

I convert all my content to hevc using Emby and my Geforce 1650.

 

So today nvidia came out with new drivers 445.75- so I upgraded the drivers.... After doing so the GPU  encoding in Emby stopped working. 

So I went back to previous driver 442.74 and  the GPU encoding started working

 

So something messed up with the drivers

 

Anybody else seeing anything similar

Edited by MisterAngelus

Share this post


Link to post
Share on other sites
Luke

Hi, what does "stopped working" mean?

Share this post


Link to post
Share on other sites
MisterAngelus

would no longer use GPU  for conversion  just  used CPU... But going back to previous drivers  made it use GPU  again  so it's not an emby issue something with the new driver

Share this post


Link to post
Share on other sites
MisterAngelus

Apparently there's an issue with the new driver that effects FPS  would that also effect converting video?

Share this post


Link to post
Share on other sites
Luke

Can we look at an example? Thanks.

Share this post


Link to post
Share on other sites
MisterAngelus

I no longer have the driver installed so i can't  run a currant test but i can attach the log you'll have to look through where it starts using cpu for conversion

embyserver.txt

Share this post


Link to post
Share on other sites
softworkz

@@MisterAngelus - Do you still have the ffmpeg logs?

 

@@Luke - Quite a number of unrelated errors in that log.

Share this post


Link to post
Share on other sites
MisterAngelus
Posted (edited)

No but if you want you can download the nvidia drivers that were causing the issue 445.75-desktop-win10-64bit-international-dch-whql-g

 

issue went away once i uninstalled those drivers tho

Edited by MisterAngelus

Share this post


Link to post
Share on other sites
softworkz

I can't. My current Nvidia GPU has different latest drivers.

 

I think we'll just wait and see whether the issue persists in subsequent updates.

Share this post


Link to post
Share on other sites
MisterAngelus

So  a new version of the drivers came out today - 445.87-desktop-win10-64bit-international-dch-whql-g so I installed it

 

has the same issue I mentioned above  still does not use the GPU to convert still not an Emby issue but mentioning it for others

 

but still uses CPU to convert

 

I had to revert to previous drivers 442.74-desktop-win10-64bit-international-dch-whql-g and it started using the GPU again

 

 

however during my test with the new drivers   445.87-desktop-win10-64bit-international-dch-whql-g  before uninstalled them and went back 

 

I did  grab the ffmpeg-transcode which @@softworkz wanted to look at

 

attached below 

ffmpeg-transcode-f60ef298-c8b1-4556-96ba-d6cfe4c92320_1.txt

Share this post


Link to post
Share on other sites
Luke

Has there been a driver update to resolve this?

Share this post


Link to post
Share on other sites
MisterAngelus
Posted (edited)

the transcode log above was taken with the latest drivers before i uninstalled them and put back the previous drivers 

 

it was using CPU so i put back the old drivers and  it went  back to using GPU

 

 

So to my knowledge it's not fixed

Edited by MisterAngelus

Share this post


Link to post
Share on other sites
MisterAngelus

update

 

the new driver came out today 446.14-desktop-win10-64bit-international-dch-whql-g

 

Same issue though

 

I have not downgraded yet

 

it still uses CPU and not gpu

 

can't figure out if there's a setting I need to change

 

I just know it works fine if i downgrade the driver

embyserver.txt

ffmpeg-transcode-adb6bfe3-2b95-445e-82bd-239699e2a884_1.txt

Share this post


Link to post
Share on other sites
softworkz

@@MisterAngelus - This is all about conversion, not playback, right?

I wouldn't recommend using Emby for doing full conversion of a library. It's just not tuned well enough to do this, no matter whether using software or hardware encoding.

Share this post


Link to post
Share on other sites
MisterAngelus

playback is fine and and i'm not using it for a full library just the occasional episodes worked fine before when i had the old driver

 

do the logs tell you anything?

Share this post


Link to post
Share on other sites
softworkz

There seems to be a problem with the detection of supported HEVC encoding levels:

Encoder NVENC GeForce GTX 1650 - H.265 (HEVC)
        Adapter #0: 'GeForce GTX 1650' ComputeCapability: 7.5
        Frame Sizes: max 8192x8192 - Width Alignment: 2 - Height Alignment: 2
        Color Formats: NV12, P010, CUDA, YUV420P
        Profiles: Main Profile (Level 2 (Main)), Main 10 Profile (Level 2 (Main)), Range Extension (REXT) (Level 2 (Main))

Level 2 is detected incorrectly.

 

And that's why it doesn't get used:

NoMatch Encoder does not support the minimum required encoding level (HevcMainTierLevel41)
NoMatch Encoder does not match

What would be a great help would be the hw detection logs: one from where it's working and the other one from where it's not working.

Share this post


Link to post
Share on other sites
softworkz

did you want me to downgrade the driver back to the one that will encode now?

 

That would be great. You might want to do that anyway to get it working until we'll be able to provide a fix.

Share this post


Link to post
Share on other sites
MisterAngelus

so I'm curious is it an emby issue or an issue with the NVIDIA driver?

Share this post


Link to post
Share on other sites
softworkz

Thanks a lot, there's in fact a difference in the supported levels that Nvidia reports:

 

5ecee533136cd_nvidia_reported_levels.jpg

 

 

The right side is correct (Level 6.2), the left side doesn't make sense.

 

I'll think we'll have to report that to Nvidia as a bug..

Share this post


Link to post
Share on other sites
MisterAngelus

I'm not experienced enough to know how to word that email  is that something emby would report to nvidia  or me?

Share this post


Link to post
Share on other sites
softworkz

No, I'll do this. We'll wait a bit though, because often, those bugs get fixed anyway, and getting heard by them takes a bit of effort and requires to ring certain bells..

Share this post


Link to post
Share on other sites
softworkz

Please feel free to remind me in a while!

Share this post


Link to post
Share on other sites
MisterAngelus

Good luck its been in the last 3 drivers  how ever old this thread is...

 

Anyway thanks so much for your help

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...