Mirrored_Repos/nvidia-patch
1
0
Fork 0
mirror of https://github.com/keylase/nvidia-patch.git synced 2024-11-12 20:58:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #69 from keylase/issue_53

Browse Source 
addresses issue #53
This commit is contained in:
Vladislav Yarmak 2019-03-02 16:43:00 +02:00 committed by GitHub
commit 8456c477b2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 17 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
win/README.md
View File

@ -37,6 +37,19 @@ E.g, for 64bit Windows 10 running driver version 417.35 use `win10_x64/417.35/nv
## See also ## See also
* Genesis in [related issue](https://github.com/keylase/nvidia-patch/issues/9) * Genesis in [related issue](https://github.com/keylase/nvidia-patch/issues/9)
* Plex Media Server:
* [How to make Plex work with new limits](https://github.com/keylase/nvidia-patch/issues/9#issuecomment-452096166) ### D3D encoding sessions
* [GH Issue about Plex, FFmpeg and NVDEC-enabling wrappers](https://github.com/keylase/nvidia-patch/issues/51)
[Related issue](https://github.com/keylase/nvidia-patch/issues/53). Summary: this patch permanently removes limit only for CUDA NVENC sessions in 64bit apps. But once usage limit was exceeded, it persists for all apps until system reboot. So, for example, you may once open 10 sessions with 64bit version of `ffmpeg` and limit will get raised to 10 for all rest types of apps until reboot. You may follow these steps to achieve this automatically and have all limits raised (assuming patch above already applied):
1. Download 64bit FFmpeg for Windows: https://ffmpeg.zeranoe.com/builds/
2. Unpack it somewhere.
3. Get [`ffmpeg_null_10streams.cmd`](ffmpeg_null_10streams.cmd) from this repo.
4. Edit `ffmpeg_null_10streams.cmd` and set executable path to real location of your unpacked ffmpeg.
5. (Optional) Add `ffmpeg_null_10streams.cmd` to autostart programs.
Also this script is useful to check if patch applied correctly and limit was raised. Use it when nothing works and you are in doubt.
### Plex Media Server
PMS for Windows currently uses dxva2 and MF for decoding and encoding, so it uses NVENC indirectly and patch probably will not work with it immediately. It is possible [D3D recipe](#d3d-encoding-sessions) will work, but it wasn't tested at this moment.

1
win/ffmpeg_null_10streams.cmd Normal file
View File

@ -0,0 +1 @@
C:\Users\user\ffmpeg\bin\ffmpeg -y -f lavfi -i nullsrc=s=256x256:d=5 -c:v h264_nvenc -f null - -c:v h264_nvenc -f null - -c:v h264_nvenc -f null - -c:v h264_nvenc -f null - -c:v h264_nvenc -f null - -c:v h264_nvenc -f null - -c:v h264_nvenc -f null - -c:v h264_nvenc -f null - -c:v h264_nvenc -f null - -c:v h264_nvenc -f null -