public/gpu-screen-recorder
1
0
Fork 0
mirror of https://repo.dec05eba.com/gpu-screen-recorder synced 2026-03-31 09:07:13 +09:00
Code Issues Actions Packages Projects Releases Wiki Activity

FAQ: glitched video

Browse Source
This commit is contained in:
dec05eba
2024-02-10 15:45:20 +01:00
parent c4ba5672b7
commit aabd64aabb
4 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.gitignore vendored
View File

@@ -17,3 +17,5 @@ gsr-kms-server
*.mp4 *.mp4
*.flv *.flv
*.mkv
*.mov

6
README.md
View File

@@ -116,8 +116,8 @@ You can use the `scripts/save-replay.sh` script to save a replay and by default
If you are using a NVIDIA GPU then it's recommended to set PreserveVideoMemoryAllocations=1 as mentioned in the section below. If you are using a NVIDIA GPU then it's recommended to set PreserveVideoMemoryAllocations=1 as mentioned in the section below.
## Examples ## Examples
Look at the [scripts](https://git.dec05eba.com/gpu-screen-recorder/tree/scripts) directory for script examples. For example if you want to automatically save a recording/replay into a folder with the same name as the game you are recording. Look at the [scripts](https://git.dec05eba.com/gpu-screen-recorder/tree/scripts) directory for script examples. For example if you want to automatically save a recording/replay into a folder with the same name as the game you are recording.
## Issues # Issues
### NVIDIA ## NVIDIA
Nvidia drivers have an issue where CUDA breaks if CUDA is running when suspend/hibernation happens, and it remains broken until you reload the nvidia driver. To fix this, either disable suspend or tell the NVIDIA driver to preserve video memory on suspend/hibernate by using the `NVreg_PreserveVideoMemoryAllocations=1` option. You can run `sudo extra/install_preserve_video_memory.sh` to automatically add that option to your system. Nvidia drivers have an issue where CUDA breaks if CUDA is running when suspend/hibernation happens, and it remains broken until you reload the nvidia driver. To fix this, either disable suspend or tell the NVIDIA driver to preserve video memory on suspend/hibernate by using the `NVreg_PreserveVideoMemoryAllocations=1` option. You can run `sudo extra/install_preserve_video_memory.sh` to automatically add that option to your system.
# Reporting bugs/contributing patches # Reporting bugs/contributing patches
@@ -147,6 +147,8 @@ edit the video with a video editor. Hevc allows for better video quality (especi
## I get a black bar on the right/bottom in the video ## I get a black bar on the right/bottom in the video
This is mostly an issue on AMD and it's a hardware issue/ffmpeg issue. If you use HEVC video codec then it's an issue in ffmpeg and if you use AV1 then it's an issue in the video encoding unit on certain AMD gpus, see: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9185. This is mostly an issue on AMD and it's a hardware issue/ffmpeg issue. If you use HEVC video codec then it's an issue in ffmpeg and if you use AV1 then it's an issue in the video encoding unit on certain AMD gpus, see: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9185.
If you get black bars then the workaround is to record with h264 video codec instead (using the -k h264 option). If you get black bars then the workaround is to record with h264 video codec instead (using the -k h264 option).
## The video is glitched, looks like checkerboard pattern
This is an issue on some intel integrated gpus on wayland caused by power saving option. Right now the only way to fix this is to record on X11 instead.
# Donations # Donations
If you want to donate you can donate via bitcoin or monero. If you want to donate you can donate via bitcoin or monero.

6
TODO
View File

@@ -122,4 +122,8 @@ Mention known issue, capture on intel wayland compressed data glitch.
Add 10 bit record option, h264_10bit, hevc_10bit and av1_10bit. Add 10 bit record option, h264_10bit, hevc_10bit and av1_10bit.
Rotate cursor texture properly (around top left origin) Rotate cursor texture properly (around top left origin).
Color range doesn't seem to work on nvidia, why?
Setup hardware video context so we can query constraints and capabilities for better default and better error messages.

2
src/main.cpp
View File

@@ -2025,7 +2025,7 @@ int main(int argc, char **argv) {
const AVCodec *h265_codec = find_h265_encoder(gpu_inf.vendor, egl.card_path); const AVCodec *h265_codec = find_h265_encoder(gpu_inf.vendor, egl.card_path);
if(h265_codec && fps > 60) { if(h265_codec && fps > 60) {
fprintf(stderr, "Warning: recording at higher fps than 60 with hevc might result in recording at a very low fps. If this happens, switch to h264\n"); fprintf(stderr, "Warning: recording at higher fps than 60 with hevc might result in recording at a very low fps. If this happens, switch to h264 or av1\n");
} }
// hevc generally allows recording at a higher resolution than h264 on nvidia cards. On a gtx 1080 4k is the max resolution for h264 but for hevc it's 8k. // hevc generally allows recording at a higher resolution than h264 on nvidia cards. On a gtx 1080 4k is the max resolution for h264 but for hevc it's 8k.