Jump to content


Photo

new nvidia drivers issue


  • Please log in to reply
24 replies to this topic

#1 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted 23 March 2020 - 03:27 PM

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, 23 March 2020 - 03:43 PM.


#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156809 posts
  • Local time: 05:09 PM

Posted 23 March 2020 - 03:45 PM

Hi, what does "stopped working" mean?



#3 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted 23 March 2020 - 04:02 PM

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



#4 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted 23 March 2020 - 05:12 PM

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



#5 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156809 posts
  • Local time: 05:09 PM

Posted 23 March 2020 - 05:28 PM

Can we look at an example? Thanks.



#6 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted 23 March 2020 - 05:59 PM

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

Attached Files



#7 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 2704 posts
  • Local time: 11:09 PM

Posted 24 March 2020 - 04:02 PM

@MisterAngelus - Do you still have the ffmpeg logs?

 

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



#8 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted 24 March 2020 - 07:37 PM

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, 24 March 2020 - 07:42 PM.


#9 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 2704 posts
  • Local time: 11:09 PM

Posted 24 March 2020 - 09:37 PM

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.



#10 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted 15 April 2020 - 02:51 PM

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 

Attached Files



#11 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 156809 posts
  • Local time: 05:09 PM

Posted 10 May 2020 - 02:35 PM

Has there been a driver update to resolve this?



#12 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted 11 May 2020 - 01:24 PM

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, 11 May 2020 - 01:26 PM.


#13 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted Yesterday, 03:27 PM

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

Attached Files



#14 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 2704 posts
  • Local time: 11:09 PM

Posted Yesterday, 03:39 PM

@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.



#15 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted Yesterday, 03:51 PM

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?



#16 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 2704 posts
  • Local time: 11:09 PM

Posted Yesterday, 03:59 PM

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.



#17 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted Yesterday, 04:16 PM

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

Attached Files



#18 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 2704 posts
  • Local time: 11:09 PM

Posted Yesterday, 04:24 PM

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.



#19 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted Yesterday, 04:55 PM

ok here is the logs with it working

Attached Files



#20 MisterAngelus OFFLINE  

MisterAngelus

    Advanced Member

  • Members
  • 137 posts
  • Local time: 04:09 PM

Posted Yesterday, 06:11 PM

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






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users