New driver support (version 555.85)
Favorass opened this issue · comments
- Nvidia driver version: 555.85
- GPU Model: GTX 1650 Mobile
- OS: Windows 11
bump
Patching fails, NV*DIA changed something again.
patch_555.85.zip
I tried patching it and it failed too, but somehow when I test using [FFmpeg to verify that NVENC session limit has been removed] (https://github.com/keylase/nvidia-patch/wiki/Verify-NVENC-patch), it doesn't show any error and works normally.
I think nvdia finally removed the session limit to the new driver as default?
The patch bytestring seems to be correctly found by the autopatch script.
@reloxx13 Is somehow 1337 tool is failing to apply it? Do you see the error for both 64 and 32-bit DLLs or only one?
The patch bytestring seems to be correctly found by the autopatch script.
@reloxx13 Is somehow 1337 tool is failing to apply it? Do you see the error for both 64 and 32-bit DLLs or only one?
Yes, both are failing with the tool
@Jaybonaut it might still be possible to remove limit from 8 to max hw supported streams.. but someone has to reverse engineer the new drivers, or debug why the patch application is failing (see #794 )
I will try to do it when I get time. If your workflow depends so strongly on this, please feel free to contribute by sending patches :)
Absolutely, when would it be best for you to train a non-coder/programmer? Very willing to help after your training. :)
New driver 555.99
New driver 555.99
The new driver (555.99) also does not require any patches as the NVENC session limit is still up to 8 by default.
New driver 555.99
The new driver (555.99) also does not require any patches as the NVENC session limit is still up to 8 by default.
It's a step in the right direction. I appreciate those of you helping to raise the limit up higher.
New driver 555.99
The new driver (555.99) also does not require any patches as the NVENC session limit is still up to 8 by default.
Are you saying that the unpatched 555.99 (and 555.85) do not require patching to increase session limit past 3, and drivers now natively support 8 NVENC sessions?
New driver 555.99
The new driver (555.99) also does not require any patches as the NVENC session limit is still up to 8 by default.
Are you saying that the unpatched 555.99 (and 555.85) do not require patching to increase session limit past 3, and drivers now natively support 8 NVENC sessions?
We need it for raising it above 8. Nvidia bumped it up to 8 themselves and it is listed on their site. They have been raising it slowly for awhile. For years it was at 2, then 3, then 5, and now 8... but many cards are capable of going way beyond 8.
New driver 555.99
The new driver (555.99) also does not require any patches as the NVENC session limit is still up to 8 by default.
Are you saying that the unpatched 555.99 (and 555.85) do not require patching to increase session limit past 3, and drivers now natively support 8 NVENC sessions?
We need it for raising it above 8. Nvidia bumped it up to 8 themselves and it is listed on their site. They have been raising it slowly for awhile. For years it was at 2, then 3, then 5, and now 8... but many cards are capable of going way beyond 8.
You learn something new every day. Thanks for the info!
556.12 just hit
@Jaybonaut can you test if the patches in #813 apply for you?
@Jaybonaut can you test if the patches in #813 apply for you?
Using Win 1337 Apply Patch File v1.9 by DFox gives me the above
Hmm.. looks like something is wrong with either the patch file formatting (nothing really changed on our side) or the 1337 tool.
Looking for that error in 1337 tool, it only throws that if the first character was not ">" in the .1337 file
https://github.com/Deltafox79/Win_1337_Apply_Patch/blob/9566cbc4824e1e93892d11260ad02133eafca011/Win_1337_Patch/1337.cs#L105
But that is not the case..
Hmm.. looks like something is wrong with either the patch file formatting (nothing really changed on our side) or the 1337 tool.
Looking for that error in 1337 tool, it only throws that if the first character was not ">" in the .1337 file https://github.com/Deltafox79/Win_1337_Apply_Patch/blob/9566cbc4824e1e93892d11260ad02133eafca011/Win_1337_Patch/1337.cs#L105
But that is not the case..
Alright I hope I figured out that I was supposed to copy the text and edit it into a .1337 file using notepad. I got the above error instead (I've edited the pic.) Apologies for my noobishness. I have zero knowledge of any of this outside of downloading prior confirmed-working patches with that tool. I used the driver link at the end of that commit.
Hmm.. looks like something is wrong with either the patch file formatting (nothing really changed on our side) or the 1337 tool.
Looking for that error in 1337 tool, it only throws that if the first character was not ">" in the .1337 file https://github.com/Deltafox79/Win_1337_Apply_Patch/blob/9566cbc4824e1e93892d11260ad02133eafca011/Win_1337_Patch/1337.cs#L105
But that is not the case..
I assume this is correct?
nvencodeapi.dll
0000000000042767:89->33
0000000000042768:45->C0
0000000000042769:08->89
000000000004276A:85->45
000000000004276B:C0->08
and
nvencodeapi64.dll
000000000004A551:8B->33
000000000004A552:F0->C0
000000000004A553:85->8B
000000000004A554:C0->F0
Yes?
Hey @jailuthra. I just wanted to test if the patch for 556.12 is working for me (Regardless of the newly increased transcoding limit), but trying to download the libraries is giving me 404 errors/not found. Can you re-up the patch? Or is it now disbandoned?
Thank you @dartraiden. Patch fails for me as well with the same error message as for @Jaybonaut