Is this a limitation on the nvenc chips? Or maybe a ffmpeg bug?ĮDIT: Setting the resolution to 3456x1440 works (3456 = 13824 / 4). I wouldn't be surprised if this is the issue. I also noticed that pitch is always exactly width * 4 (as it should be?) but for the ultrawide case it's width * 4 + 64. Manually setting any other "normal" resolution seems to work (I tried 1080p, 1440p, 2160p, 2560x1600) but deviating from the "normal" resolutions even just a bit causes this error (for example 1922x1080 also causes the same error to appear). Note: I compiled ffmpeg from source to add the logging for width/height/pitch to debug the problem. Error registering an input resource: resource register failed (23): I tried debugging the issue and it fails to register the HW frame with an unknown error: Not sure if this is the right place for this, but this doesn't seem to work for ultrawide resolutions. Then, I made the start-replay script autostart and used a custom shortcut for Alt+F10 to run save-replay. Mv ~/Videos/tbm-replays/* ~/Videos/"$(cat /proc/$(xdotool getwindowpid $(xdotool getwindowfocus))/comm)" What this does is basically moves the replay that was just created to the folder that was just created or the folder containing the active instances name. Next, put this below the "killall" command. Mkdir -p ~/Videos/"$(cat /proc/$(xdotool getwindowpid $(xdotool getwindowfocus))/comm)" What this does is basically makes a folder in the videos directory with the focused window name (i.e GTAV.exe). Gpu-screen-recorder -w screen -f 60 -a "$(pactl get-default-sink).monitor|$(pactl get-default-source)" -c mp4 -r 30 -o ~/Videos/tbm-replaysįor the " save-replay.sh " file, just put this line above the "killall" command. I also made sure the audio track was my default microphone and headphones combined. I had to configure the scripts (gpu-screen-recorder/scripts) it provides a bit though, so I wanted to put a simple little tutorial on how I did it.įor the " start.sh " file, just make the output go to a folder that will store temporary replays that will be moved somewhere. I was able to achieve the effect of pressing Alt + F10 and saving the last 30 seconds of a game to a folder with that game's name. I know this is a bit of old post, but huge thanks to the person who made this. The screen recorder also has a so called "replay buffer", which allows you to press a key to save the last few seconds instead of recording all the time, just like nvidia shadowplay.Įdit: I created an install script for gpu-screen-recorder for ubuntu based distros called install_ubuntu.sh. If you are on arch then the software is available in aur. Here are some demos of the screen recorder in action: With my screen recorder the fps stays at 30 (fps is locked to 30 fps in the game). My screen recorder does not require a gpu with nvfbc support either.Īs a performance comparison, playing breath of the wild with the cemu emulator at 4k and using obs makes the fps drop from 30 to 7 with my hardware. So I made my own screen recorder instead that records the screen 100% on the gpu and to my knowledge its the only such tool available for nvidia gpus on linux and its much faster than any other screen recorder to my knowledge. Neither obs with nvenc nor the obs-nvfbc plugin record the screen fully with the gpu. When I switched to linux I was missing a fully hardware accelerated screen recorder such as nvidia shadowplay which allows you to record games with barely losing any fps, without having to use a capture card. We know spam when we see it and will delete it. This means things like repetitious posting of similar content, low-effort posts/memes and misleading/exaggerated titles on link posts. We all need to support each other to help GNU/Linux gaming grow. If it's a link post, think about writing a comment to tell us more - the more you engage with us, the more we like it. Remember you are talking to another human being.ĭevs and content producers: If you've ported your game to Linux or created some GNU/Linux-gaming-related content (reviews, videos, articles) then, so long as you're willing to engage with the community, please post it here. Heated discussions are fine, unwarranted insults are not. What exactly did you do, and how, and with what version of what? How have you tried to troubleshoot the problem? Vague, low-effort tech-support requests may get removed. Include relevant details like logs, terminal output, system information. Tech-support requests should be readable by and useful to others. It is not (primarily) a tech-support forum. /r/Linux_Gaming is for informative and interesting gaming content, news and discussions.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |