diff options
| author | dec05eba <dec05eba@protonmail.com> | 2021-10-30 10:13:59 +0200 |
|---|---|---|
| committer | dec05eba <dec05eba@protonmail.com> | 2021-10-30 10:13:59 +0200 |
| commit | f20253fce9406a983ef0c9012dcbc953ded5a071 (patch) | |
| tree | 5913b4c651879d1f756597dcd2051499ac35c986 | |
| parent | a6e0e16f574a8c13593356675862c27f4387758e (diff) | |
Update readme with info about nvfbc
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -16,7 +16,7 @@ the fps remains at 30. # Installation gpu screen recorder can be built using [sibs](https://git.dec05eba.com/sibs) or if you are running Arch Linux, then you can find it on aur under the name gpu-screen-recorder-git (`yay -S gpu-screen-recorder-git`).\ -Recording displays requires a gpu with NvFBC support. Normally only tesla and quadro gpus support this, but by using https://github.com/keylase/nvidia-patch you can do this on all gpus that support nvenc as well (gpus as old as the nvidia 600 series), provided you are not using outdated gpu drivers. +Recording monitors requires a gpu with NvFBC support (note: this is not required when recording a single window!). Normally only tesla and quadro gpus support this, but by using https://github.com/keylase/nvidia-patch you can do this on all gpus that support nvenc as well (gpus as old as the nvidia 600 series), provided you are not using outdated gpu drivers. # How to use Run `interactive.sh` or run gpu-screen-recorder directly, for example: `gpu-screen-recorder -w 0x1c00001 -c mp4 -f 60 -a bluez_sink.00_18_09_8A_07_93.a2dp_sink.monitor > test_video.mp4`\ |