@DEC05EBA I've been testing constant framerate recording using '-fm cfr' as you suggested and it's working flawlessly on my system (5600X/6800XT). Another question: Is there a way to record at a fractioned fps? For example, 59.94 instead of 60 to match YouTube's enconding. I tried '-f 59.94' but it records at 59.00.
Search Criteria
Package Details: gpu-screen-recorder r1064.1f3d28f-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/gpu-screen-recorder.git (read-only, click to copy) |
---|---|
Package Base: | gpu-screen-recorder |
Description: | A shadowplay-like screen recorder for Linux. The fastest screen recorder for Linux |
Upstream URL: | https://git.dec05eba.com/gpu-screen-recorder |
Licenses: | GPL-3.0-only |
Submitter: | DEC05EBA |
Maintainer: | DEC05EBA |
Last Packager: | DEC05EBA |
Votes: | 52 |
Popularity: | 3.05 |
First Submitted: | 2024-11-15 18:38 (UTC) |
Last Updated: | 2025-04-15 01:35 (UTC) |
Dependencies (23)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-cudaAUR, ffmpeg-ffplayoutAUR, ffmpeg-headlessAUR, ffmpeg-fullAUR, ffmpeg-decklinkAUR, ffmpeg-amd-fullAUR, ffmpeg-gitAUR, ffmpeg-full-gitAUR, ffmpeg-amd-full-gitAUR, ffmpeg-obsAUR, ffmpeg-libfdk_aacAUR)
- libcap
- libdrm (libdrm-gitAUR)
- libglvnd (libglvnd-gitAUR)
- libpipewire (libpipewire-full-gitAUR, libpipewire-gitAUR)
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libva (libva-gitAUR, intel-media-stack-binAUR, libva-headlessAUR)
- libx11 (libx11-gitAUR)
- libxcomposite
- libxdamage
- libxfixes
- libxrandr (libxrandr-gitAUR)
- wayland (wayland-gitAUR, wayland-asan-gitAUR, wayland-chromiumAUR)
- meson (meson-gitAUR) (make)
- vulkan-headers (vulkan-headers-gitAUR) (make)
- intel-media-driver (intel-media-stack-binAUR, intel-media-driver-gitAUR) (optional) – Required to record your screen on Intel Broadwell or later iGPUs or Intel Arc
- libva-intel-driver (libva-intel-driver-gitAUR, libva-intel-driver-hybridAUR, libva-intel-driver-g45-h264AUR, libva-intel-driver-hybrid-gitAUR, libva-intel-driver-irqlAUR) (optional) – Required to record your screen on Intel G45 and HD Graphics family
- libva-mesa-driver (mesa-wsl2-gitAUR, amdonly-gaming-mesa-gitAUR, mesa-gitAUR, mesa-minimal-gitAUR, mesa) (optional) – Required to record your screen on AMD
- libxnvctrl (libxnvctrl-430xxAUR, libxnvctrl-340xxAUR, libxnvctrl-390xxAUR, libxnvctrl-525xxAUR, libxnvctrl-510xxAUR, libxnvctrl-470xxAUR, libxnvctrl-535xxAUR) (optional) – Required when using the -oc option to overclock the NVIDIA GPU to workaround NVIDIA p2 state bug
- linux-firmware (linux-libre-firmwareAUR, linux-firmware-uncompressedAUR, linux-firmware-gitAUR) (optional) – Required to record your screen on Intel Skylake or later iGPUs
- mesa (mesa-wsl2-gitAUR, mesa-amd-bc250AUR, amdonly-gaming-mesa-gitAUR, mesa-gitAUR, mesa-minimal-gitAUR, mesa-amber) (optional) – Required to record your screen on AMD/Intel
- nvidia-utils (nvidia-410xx-utilsAUR, nvidia-440xx-utilsAUR, nvidia-430xx-utilsAUR, nvidia-340xx-utilsAUR, nvidia-525xx-utilsAUR, nvidia-510xx-utilsAUR, nvidia-utils-teslaAUR, nvidia-vulkan-utilsAUR, nvidia-390xx-utilsAUR, nvidia-470xx-utilsAUR, nvidia-550xx-utilsAUR, nvidia-535xx-utilsAUR, nvidia-utils-betaAUR) (optional) – Required to record your screen on NVIDIA
Required by (2)
Sources (1)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 19 Next › Last »
flxrbr commented on 2023-08-22 23:08 (UTC)
DEC05EBA commented on 2023-08-22 07:37 (UTC)
@flxbr that's more of a shell command question, but you can do this for the output file to get the same format as the GUI version:
-o "$HOME/Videos/Video_$(date +"%Y-%m-%d_%H-%M-%S").mp4"
flxrbr commented on 2023-08-22 03:41 (UTC)
Is there a way to generate a video file with a not static name like the GUI version does?
DEC05EBA commented on 2023-08-17 07:05 (UTC) (edited on 2023-08-17 07:38 (UTC) by DEC05EBA)
@creepergd really? I hope so. It's disappointing how many amd/nvidia driver bugs I have found.
creepergd commented on 2023-08-17 01:49 (UTC) (edited on 2023-08-17 01:50 (UTC) by creepergd)
@DEC05EBA I think pushing p5 actually fixed like literally my last issue with this software. I have had microstutters since I was using it but I felt as if it was placebo (with or without xcompmgr active), but with the latest release they are completely gone and it feels like I'm not even recording at all. You set the highest quality to be p5 for this fix right? Whatever you did it is great.
DEC05EBA commented on 2023-08-15 20:40 (UTC) (edited on 2023-08-15 21:34 (UTC) by DEC05EBA)
The application seems to freeze when recording a small window with h264 codec on nvidia (x11). I suspect this might be a new nvidia driver bug. I'm looking into it.
edit: i found the issue. Nvidia has a new (?) bug that causes preset p6 to freeze when encoding a small window. I pushed a workaround for this until nvidia fixes the bug.
DEC05EBA commented on 2023-08-13 00:04 (UTC) (edited on 2023-08-13 00:04 (UTC) by DEC05EBA)
I fixed a bug that should have affected all amd/intel users but was only noticed by some intel users. Screen capture should now work if it didn't for you before.
DEC05EBA commented on 2023-08-11 16:36 (UTC)
@ThatOneSeong is that with the regular nvidia driver or the nvidia open driver? also please report bugs by email to dec05eba at protonmail dot com, instead of here
ThatOneSeong commented on 2023-08-11 16:24 (UTC)
There seems to be an issue with recording individual windows, at least on my system running Plasma 5.27. Affects both capture from commandline and the gtk frontend, either selecting the window manually or capturing "focused". Running on an RTX 3060 ti with 535.98, but was affected on every previous driver version tried on this card.
Error: cuGraphicsGLRegisterImage failed, error invalid OpenGL or DirectX context, texture id: 2
gsr error: gsr_capture_start failed
DEC05EBA commented on 2023-08-09 10:18 (UTC) (edited on 2023-08-09 16:51 (UTC) by DEC05EBA)
It looks like there was a recent update to ffmpeg that causes cpu usage to increase a lot when recording a longer time. I'm investigating this, and reporting it to ffmpeg devs. For now you can use the flatpak version instead (https://flathub.org/apps/com.dec05eba.gpu_screen_recorder) which uses an old ffmpeg version which doesn't have this issue.
edit: I updated gpu screen recorder with an attempt to hackaround the issue. Please update gpu screen recorder aur package.
Pinned Comments
DEC05EBA commented on 2024-11-26 18:52 (UTC)
The aur package gpu-screen-recorder-git was renamed to gpu-screen-recorder. Install gpu-screen-recorder instead or you may experience issues.