| 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: | 53 |
| Popularity: | 4.33 |
| First Submitted: | 2024-11-15 18:38 (UTC) |
| Last Updated: | 2025-04-03 23:48 (UTC) |
@DEC05EBA Went back and checked, but still the issue persists.
But I'm also using mpv (always have been), yet the issue persists with new recordings. Console output when playing back in mpv even shows an A/V desynchronisation error and dropped frames - which doesn't happen with either older recordings or other local/web videos.
@ThatOneSeong Can you try it now? If it still doesn't work then it's a known bug in vlc/kdenlive, but it should work with mpv/youtube. I'll fix it for broken media players / video editors in the future.
Hi, sorry to be the bearer but I've found a new issue. With both the cli and -gtk frontend of this tool, if I'm capturing the audio from one of the device monitors, the resulting clip (either lowest-quality manual capture or replay) has desynced audio with horrible frame-pacing. Recording just the video alone does not have this issue, just when recording with audio - regardless of whether it's an actual game, or simply a soundless test shot of dragging a Plasma window around.
The same issue does not happen with OBS; even with recording to multiple audio tracks.
Unfortunately, I'm not sure what might've changed on this setup to cause it. I'm using PipeWire for my audio, which has worked as late as June 7th since that's the last day I made a manual recording that turned out fine. It doesn't seem to have anything to do with the WirePlumber transition, since the first recording I'd made with this issue was on June 15th, on the same install of Arch using pipewire-media-session at the time. And no Nvidia driver updates could've happened in that time either.
How? I just said that that doesn't seem possible in aur. Remote (in git) gives an error if you try to change the name of the package.
edit: it seems like you can change the name of a package, but it's a manual process that a moderator needs to do (after I create a new package and request merge..)
Then please rename your -git packages to ones without the -git suffices.
@MarsSeed It's not possible to change the name of a package without creating a new one (as far as I know) and I have explained the issues with that before. I dont want to use github, gitlab or those alternatives for personal reasons either.
@DEC05EBA, you should rename this package to 'gpu-screen-recorder' if you want to keep using tar.gz as source.
Or my alternative suggestion to you is to host or mirror your git source repo on a major git service like GitHub or GitLab or BitBucket. Then you wouldn't have problems with your hosting server speed and response time.
Can confirm the source issue was with NvFBC/updated vulkan, for now the temp patch from the discussion allows it to work.
As for the ask, it's easier for windows that change geometry if I just record the screen. Besides, it's the 'workflow' I'm used to with Shadowplay/Share anyways.
But I believe there is a way to record a monitor on plasma/gnome without nvfbc. I'll look into it later.
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.