GPU Screen Recorder issue tracker
This is the issue tracker for GPU Screen Recorder. This is only for reporting issues, not for developing GPU Screen Recorder or suggesting features.
Describe the bug
The software don't want to start because of "missing video codec".
To Reproduce
Launch GPU Screen Recorder
Screenshots
Screenshots :
Desktop (please complete the following information):
Additional context
Add any other context about the problem here, such as terminal output of running GPU Screen Recorder and if there was an issue in the video then run the command sudo drm_info > log.log and attach that log.log file in this bug report. drm_info can be installed from your package manager or from https://gitlab.freedesktop.org/emersion/drm_info.
I can't use the 'drm_info' command. I installed it, but don't work.
Describe the bug
When recording the audio from the "Default output" source, to record desktop audio, I notice that sound is quieter than it should be.
To Reproduce
Just run the recording & you will notice it.
Expected behavior
Audio should match the volume levels that are played in audio source (desktop).
Desktop
Additional context
Audio codec doesn't matter here, as it doesn't change anything.
This might be a PipeWire bug, not the bug of this application, but I'm not sure, so that's why I'm reporting here.
I have 6700XT, Ryzen 7600 combo and 7000s series come with iGPUs capable of recording I was wondering would it be possible to offload the encoding to the iGPU instead of the main GPU?
Adding VP9 support to GPU Screen Recorder. This would give you an output format that is compatible with Discord and other platforms alike since YouTube uses VP9 alongside AV1 and other codecs. This feature would significantly enhance the software's utility especially for users like me where our hardware can do VP9 but can't do AV1. It's the next best thing for videos going to the great interwebs.
https://imagekit.io/blog/vp9-codec/
I am aware you likely don't use Discord considering you don't even use GitHub to host your project's source code anymore.
Describe the bug
Videos produced when using a 3440x1440 resolution causes the right X number of pixels to be cut off/distorted.
To Reproduce
Running with systemd at startup
/bin/sh -c 'AUDIO="${AUDIO_DEVICE:-$(pactl get-default-sink).monitor}"; gpu-screen-recorder -v no -w $WINDOW -c $CONTAINER -q $QUALITY -k $CODEC -ac $AUDIO_CODEC -a "$AUDIO" -f $FRAMERATE -r $REPLAYDURATION -o "$OUTPUTDIR" -mf $MAKEFOLDERS $ADDITIONAL_ARGS -cr $COLOR_RANGE'
Output of gpu-screen-recorder.env:
WINDOW=screen
CONTAINER=mp4
QUALITY=very_high
CODEC=auto
AUDIO_CODEC=opus
FRAMERATE=60
REPLAYDURATION=60
OUTPUTDIR=/home/rt/Videos/replays
MAKEFOLDERS=no
COLOR_RANGE=limited
Expected behavior
The recording to capture the full 3440x1440 resolution
Screenshots
Below is a screenshot of a recording, played back with MPV:
Desktop (please complete the following information):
Additional context
Does not happen if I use OBS.
mpv --no-config video.mp4 (if applicable)Describe the bug
When the monitors are shut off via DPMS, either through something like xset dpms force off or KDE's "Turn off screen" setting in Energy Saving settings, the recording will continue with audio, but the video will be stuck on the last frame displayed. In addition, the log gsr error: gsr_capture_nvfbc_capture failed: A capture to a GL buffer session has not been created for this NvFBC client is spammed multiple times per second on stderr.
To Reproduce
gpu-screen-recorder -v no -w DP-0 -c mp4 -q very_high -k auto -ac opus -a alsa_output.usb-Schiit_Audio_Schiit_Unison_Universal_Dac-00.analog-stereo.monitor -f 60 -r 600 -o /home/alex/Videos/shadowplay -mf yes -a alsa_input.usb-Elgato_Systems_Elgato_Wave_1_AS47J1A01425-00.mono-fallback -cr limited
then
xset dpms force off
Desktop (please complete the following information):
Additional context
gsr.log
drm_info.log
OBS screen recording:
https://github.com/dec05eba/gpu-screen-recorder-issues/assets/1723612/1ea18ae7-c433-4449-bd53-1cb429bb6397
Raw output:
https://github.com/dec05eba/gpu-screen-recorder-issues/assets/1723612/7ee5f9ab-9af2-4a32-bec3-55c317ff29ba
mpv --no-config video.mp4 (if applicable)Describe the bug
After installing GPU Screen Recorder from Flathub, and running it in rootful mode on GNOME Wayland session on Fedora 40, it only asks for root access the first time. It never asks for that password prompt again. However, this behaviour persists across complete reinstalls and computer reboots - meaning that whatever binary was installed the first time asking for root access was not completely removed or permissions given were completely reverted.
To Reproduce
GUI option:
--delete-data flagExpected behavior
The program asks for the root password again, because whatever it uses for privilege elevation was reverted
Screenshots
The program no longer asks for the root password, because whatever it did after requesting root access the first time is still there.
Desktop (please complete the following information):
Additional context
mpv --no-config video.mp4 (if applicable)Describe the bug
When recording, on the right side of the screen. im getting some weird color, im unsure how this happens exactly except that its only showing only on the GPU, using H264 works as expected
To Reproduce
Record with a gpu
Expected behavior
they arent suppost to be there
Screenshot
Additional context
everything has been explained, this hasnt happened on any version prior to 3.7.2 at least i believe so.
mpv --no-config video.mp4 (if applicable)Describe the bug
Any recording made by gpu-screen-recorder uploaded to discord doesn't generate a preview, even if -fm cfr is set
To Reproduce
gpu-screen-recorder -w DP-3 -c mp4 -f 60 -a "alsa_output.usb-Kingston_HyperX_Cloud_II_Wireless_000000000001-00.analog-surround-71.monitor" -fm cfr -o /mnt/hdd/Videos/replay/test.mp4
Expected behavior
Usable video for discord
Screenshots
Desktop (please complete the following information):
Additional context
This is the actual video that isn't processed through ffmpeg: link
Video runs fine on mpv, its just discord not accepting it
Obs produces videos that I can directly use on discord
Passing it through ffmpeg would make the video usable on discord: ffmpeg -i /mnt/hdd/Videos/replay/test.mp4 output.mp4, but I have to use it without -c copy, and that takes a while to do
I played the video with the command mpv --no-config video.mp4 (if applicable)
I use a laptop with an integrated GPU and a dedicated GPU
Describe the bug
Not sure if this is a bug or not, seeking help here. Video framerate is stuttering and unstable in certain games when using "constant" framerate for recording. I require constant framerate for video editing post recording. Some games run just fine, others are stuttering at 1 fps. Tested with both Steam + Proton as Flatpak and Snap on Ubuntu 23.10 and 22.04.
Example stuttering video: Alien Isolation, Everquest 2
Example fluid 60 fps video: Turok 2 PC remaster, Aliens vs Predator 1, Crazy Taxi
To Reproduce
See attached screenshot: I tried lowering the video quality settings to medium, changing the codec from H265 to H264, and dropping the resolution of the game to lower levels. I usually record at 4k60 resolution, but lower resolutions have the same issue. Lowering the graphics in-game to the lowest setting doesn't help the issue either.
Expected behavior
I expect the video to run at buttery smooth 60 fps.
Screenshots
See screenshots and video examples attached to this report.
Desktop (please complete the following information):
Additional context
flatpak run com.dec05eba.gpu_screen_recorder Gtk-Message: 21:42:45.851: Failed to load module "canberra-gtk-module" Gtk-Message: 21:42:45.852: Failed to load module "canberra-gtk-module" window name: Alien: Isolation, window id: 8388707 Warning: opus and flac audio codecs are temporary disabled, using aac audio codec instead [hevc_nvenc @ 0x603820a9c280] ignoring invalid SAR: 0/0 Info: using hevc encoder because a codec was not specified [hevc_nvenc @ 0x603820a9c280] ignoring invalid SAR: 0/0 update fps: 239 update fps: 77 update fps: 27 update fps: 17 update fps: 13 update fps: 10 update fps: 10 update fps: 9 update fps: 7 update fps: 6 update fps: 5 update fps: 4 update fps: 4 update fps: 5 update fps: 4 update fps: 4 update fps: 3 update fps: 3 update fps: 3 update fps: 3 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 2 update fps: 1 update fps: 2 update fps: 2 update fps: 2 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 update fps: 1 Notification: title: GPU Screen Recorder, body: The recording was saved to /home/sturmlocke/Videos/GPU Screen Rec/Video_2024-04-26_21-44-12.mp4
I have been recording on openSUSE Leap 15.5 with another PC that is identical to this one hardware-wise, and have not experienced these issues on openSUSE (recording with the exact same settings with constant framerate mode produces 60 fps smooth videos on Suse). On Ubuntu, recording anything outside of Steam and Proton runs just fine. I have tried recording standalone Flatpak and Snap games, such as Xonotic, and the video is super smooth at 60 fps. Worth mentioning: I've noticed that the Nvidia video engine is often at 90-100% load for the videos recorded where it's stuttering badly. In other words, 90-100% load during recording. No fps-drops in gameplay, only the video stutters post recording.
Tested with MPV player, VLC and Gnome Video player. Importing the video into Shotcut or Kdenlive video editior shows the same stuttering picture.
mpv --no-config video.mp4 (if applicable)Feel free to ask for more infos, will gladly provide more feedback.
Describe the bug
When starting replay I get this bug:
[hevc_nvenc @ 0x55f6e12112c0] ignoring invalid SAR: 0/0
[hevc_nvenc @ 0x55f6e24fcfc0] ignoring invalid SAR: 0/0
Warning: opus audio codec is chosen but your ffmpeg version does not support s16/flt sample format and performance might be slightly worse. You can either rebuild ffmpeg with libopus instead of the built-in opus, use the flatpak version of gpu screen recorder or record with flac audio codec instead (-ac flac). Falling back to fltp audio sample format instead.
[SWR @ 0x7fe0e8000900] Input channel layout "" is invalid or unsupported.
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
[SWR @ 0x7fe0e8000900] Context has not been initialized
I've tried recording with no audio and the problem fixes itself, which leads me to believe this is an issue with audio (which could be or not related to ffmpeg)
To Reproduce
The GPU Screen Recorder command you ran or if you used the GUI version then describe which options you used.
Just running:
gpu-screen-recorder -w screen -fm cfr -f 60 -a bluez_sink.C0_91_B9_DE_7C_AE.a2dp_sink.monitor -ac opus -k hevc -c mp4 -r 60 -o /home/wolf/Videos
Expected behavior
The error should not show up, audio should be clear and correct when saving.
Screenshots
The program IS running, so I can save it but then it sounds like this:
Desktop (please complete the following information):
Additional context
I've tried all codecs to no avail, this is my ffmpeg version:
ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg developers (flatpak)
System Info:
System:
Kernel: 5.15.0-102-generic x86_64 bits: 64 compiler: gcc v: 11.4.0
Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
Type: Laptop System: Dell product: Dell G15 5515 v: 1.16.0
serial: <superuser required> Chassis: type: 10 v: 1.16.0
serial: <superuser required>
Mobo: Dell model: 09YV3R v: A00 serial: <superuser required> UEFI: Dell
v: 1.16.0 date: 01/09/2024
Battery:
ID-1: BAT1 charge: 40.6 Wh (100.0%) condition: 40.6/86.0 Wh (47.3%)
volts: 12.0 min: 11.4 model: BYD 0x48,0x31,0x35,0x4B,0x69,0x03,0
type: Li-ion serial: <filter> status: Full
ID-2: hidpp_battery_2 charge: 22% condition: N/A volts: 3.7 min: N/A
model: Logitech G915 TKL LIGHTSPEED Wireless RGB Mechanical Gaming Keyboard
type: N/A serial: <filter> status: Discharging
CPU:
Info: 8-core model: AMD Ryzen 7 5800H with Radeon Graphics bits: 64
type: MT MCP smt: enabled arch: Zen 3 rev: 0 cache: L1: 512 KiB L2: 4 MiB
L3: 16 MiB
Speed (MHz): avg: 3399 high: 3965 min/max: 1200/3200 boost: enabled
cores: 1: 3170 2: 3155 3: 3441 4: 3660 5: 3965 6: 3962 7: 3165 8: 3169
9: 3435 10: 3476 11: 3605 12: 3528 13: 3169 14: 3166 15: 3162 16: 3166
bogomips: 102208
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
I have 2 speakers:
-- Built-in Laptop Speakers
-- Bluetooth Speaker (Active)
Optimus is disabled in BIOS.
Help would be appreciated, sorry if it may not be related.
Thanks
mpv --no-config video.mp4 (if applicable)Describe the bug
A clear and concise description of what the bug is.
I am trying to run gpu-screen-recorder inside a docker container.
So, here is how i build it
# This builds and updates the screen recorder we use on Netris
# From https://git.dec05eba.com/gpu-screen-recorder
FROM ubuntu:23.10
ENV DEBIAN_FRONTEND=noninteractive
# To run /usr/bin/gpu-screen-recorder.
# Add this to your runtime
# docker run --rm --cap-add SYS_ADMIN --cap-add SYS_NICE netris/gpu-screen-recorder
#Build and install gpu-screen-recorder
RUN apt-get update -y \
&& apt-get install -y \
curl \
unzip \
git \
build-essential \
ninja-build \
gcc \
meson \
cmake \
ccache \
bison \
software-properties-common \
ca-certificates \
equivs \
ca-certificates\
libcap2-bin \
libllvm15 \
libavcodec-dev \
libavformat-dev \
libavutil-dev \
libavfilter-dev \
libavdevice-dev \
libswresample-dev \
libswscale-dev \
libx11-dev \
libxcomposite-dev \
libkpipewire-dev \
libxrandr-dev \
libxfixes-dev \
libpulse-dev \
libswresample-dev \
libva-dev \
libcap-dev \
libdrm-dev \
libgl-dev \
libegl-dev \
libwayland-dev \
libnvidia-egl-wayland-dev \
libwayland-egl-backend-dev \
wayland-protocols \
&& rm -rf /var/lib/apt/lists/* \
#Install Cuda
&& cd /tmp && curl -fsSL -o nvidia_cuda_nvrtc_linux_x86_64.whl "https://developer.download.nvidia.com/compute/redist/nvidia-cuda-nvrtc/nvidia_cuda_nvrtc-11.0.221-cp36-cp36m-linux_x86_64.whl" \
&& unzip -joq -d ./nvrtc nvidia_cuda_nvrtc_linux_x86_64.whl && cd nvrtc && chmod 755 libnvrtc* \
&& find . -maxdepth 1 -type f -name "*libnvrtc.so.*" -exec sh -c 'ln -snf $(basename {}) libnvrtc.so' \; \
&& mkdir -p /usr/local/nvidia/lib && mv -f libnvrtc* /usr/local/nvidia/lib \
&& echo "/usr/local/nvidia/lib" >> /etc/ld.so.conf.d/nvidia.conf && echo "/usr/local/nvidia/lib64" >> /etc/ld.so.conf.d/nvidia.conf \
&& git clone https://repo.dec05eba.com/gpu-screen-recorder && cd gpu-screen-recorder \
&& chmod +x ./build.sh ./install.sh \
&& ./install.sh
...other codeAnd then the final image is here, where i install EGL and the like.
The problem comes in when i try to run it inside the container on a remote AWS machine with a TESLA T4 nvidia gpu
However, i keep getting this error
To Reproduce
docker run --gpus all --entrypoint /bin/bash --rm -it -v $(pwd):/games -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY=$DISPLAY --cap-add=SYS_NICE --cap-add=SYS_ADMIN ghcr.io/wanjohiryan/netris/server:nightlygpu-screen-recorder -w screen -f 60 -o "$HOME/Videos/video.mp4"Edit: Something to note, it appears that the host GPU uses EGL with llvmpipe,(this is software rendering i believe), how can I change this ?
Expected behavior
A clear and concise description of what you expected to happen.
gpu-screen-recorder should run without any EGL errors.Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here, such as terminal output of running GPU Screen Recorder and if there was an issue in the video then run the command sudo drm_info > log.log and attach that log.log file in this bug report. drm_info can be installed from your package manager or from https://gitlab.freedesktop.org/emersion/drm_info.
Attach a video that shows the issue (if applicable), in raw form as output by GPU Screen Recorder or a losslessly cut version of it.
Which game did you run while recording (if any) and does the issue also happen if you only record your desktop?
Does the issue also happen if you use obs studio instead? If you have an issue with audio make sure you are not using pulseaudio/pipewire audio processing software such as EasyEffects.
mpv --no-config video.mp4 (if applicable)Describe the bug
When trying to stop the recording, application completely freezes, no matter which container or recording quality is selected.
I don't get this bug on AMD Vega 7 or RX 5500 GPU.
To Reproduce
Start the recording & try to stop it.
Expected behavior
Recording should be stopped & saved successfully.
System info
mesa-freeworld is installed)Additional context
I compared the logs that I got from RX 6600 & RX 5500 GPUs by running flatpak run --verbose & I didn't see anything differing in the logs, except that it did not go past gsr info: gsr_kms_client_init: waiting for server to connect part of the log.
amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
pkexec version 123
/var/home/gidro
amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
[hevc_vaapi @ 0x560ad42ac900] ignoring invalid SAR: 0/0
[hevc_vaapi @ 0x560ad42ac900] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).
Info: using hevc encoder because a codec was not specified
gsr info: gsr_kms_client_init: waiting for server to connect
OBS GPU-accelerated recording works.
Describe the bug
The video is glitched when recording on wayland
To Reproduce
gpu-screen-recorder -w screen -f 60 -o video.mp4
Expected behavior
The video shouldn't look glitched
Screenshots
Desktop (please complete the following information):
Additional context
Terminal output:
[hevc_vaapi @ 0x6239a97bb380] ignoring invalid SAR: 0/0
[hevc_vaapi @ 0x6239a97bb380] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).
Info: using hevc encoder because a codec was not specified
gsr info: gsr_kms_client_init: waiting for server to connect
kms server info: connecting to the client
gsr info: gsr_kms_client_init: server connected
gsr info: replacing file-backed unix domain socket with socketpair
kms server info: connected to the client
gsr info: using socketpair
[hevc_vaapi @ 0x6239a97bb380] ignoring invalid SAR: 0/0
[hevc_vaapi @ 0x6239a97bb380] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).
update fps: 247
update fps: 247
drm_info output:
drm_info.log
mpv --no-config video.mp4 (if applicable)Describe the bug
Audio latency is roughly twice as much after commits for fixing audio desync issues
To Reproduce
gpu-screen-recorder -w screen -f 120 -a "$(pactl get-default-sink).monitor" -cr full -fm cfr -ac opus -k hevc -q very_high -o ~/videos/video.mkv
Expected behavior
Lower audio latency
Screenshots
"nodesync-build" uses the commits that fixed the audio desync. "desync-build" is the build I used to report #7. the lines show when it appears on video, the waveform shows the audio.
Desktop (please complete the following information):
X11 or Wayland: Wayland
Desktop environment/Window Manager: Sway
Distro: Debian
GPU: Radeon RX 6700XT
Version: Source
I played the video with the command mpv --no-config video.mp4 (if applicable)
I use a laptop with an integrated GPU and a dedicated GPU
I am exploring gpu-screen-recorder-gtk, which I have installed from flathub, on Kubuntu 22.04 (X11) with Intel Corporation Iris Plus Graphics G1 (Ice Lake) GPU. The app is really impressive with very low cpu load. I have some suggestions that I hope will be implemented to improve the software.
Best regards,
Describe the bug
I was testing the flatpak version (provided by @dec05eba) which gratefully fixed the audio bug when using pulseaudio, so I decided to use two sinks and see the behavior. Everything seems to sound ok, but as soon as I switch sinks (as seen on the video) the sound seems to overlap over the other and then cause major synchronization issues.
To Reproduce
The GPU Screen Recorder command you ran or if you used the GUI version then describe which options you used.
flatpak run --command=gpu-screen-recorder com.dec05eba.gpu_screen_recorder -w screen -fm cfr -f 60 -a "alsa_output.pci-0000_06_00.6.HiFi__hw_Generic__sink.monitor|bluez_sink.C0_91_B9_DE_7C_AE.a2dp_sink.monitor" -ac aac -k hevc -c mp4 -r 60 -o /home/wolf/Videos
Expected behavior
The audio should remain in sync even if you switch between sinks. It is my understanding that unless you separate the sinks using the option -a , then by separating them using | (pipe), should merge them into a single track, thus monitoring both sinks and keeping the audio on sync throughout the video.
Screenshots
Desktop (please complete the following information):
Additional context
mpv --no-config output:
wolf@wolf-mint:~/Videos/Sound$ mpv --no-config Replay_2024-04-11_18-49-14.mp4
(+) Video --vid=1 (*) (hevc 1920x1080 60.000fps)
(+) Audio --aid=1 (*) (aac 2ch 48000Hz)
AO: [pulse] 48000Hz stereo 2ch float
VO: [gpu] 1920x1080 yuv420p
Invalid audio PTS: 1.022333 -> 1.503896
Invalid audio PTS: 1.525229 -> 2.002854
AV: 00:00:21 / 00:00:49 (42%) A-V: 0.000
Invalid audio PTS: 19.841812 -> 20.319396
Invalid audio PTS: 20.340729 -> 20.822271
Invalid audio PTS: 20.843604 -> 21.321208
Invalid audio PTS: 21.342542 -> 21.649771
AV: 00:00:21 / 00:00:49 (43%) A-V: 0.000
Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).
AV: 00:00:17 / 00:00:49 (34%) A-V: 0.000
Invalid audio PTS: 15.838500 -> 16.315958
Invalid audio PTS: 16.337292 -> 16.814833
Invalid audio PTS: 16.836167 -> 17.317687
Invalid audio PTS: 17.339021 -> 17.816521
Invalid audio PTS: 17.837854 -> 18.319562
Invalid audio PTS: 18.340896 -> 18.818500
Invalid audio PTS: 18.839833 -> 19.317500
Invalid audio PTS: 19.338833 -> 19.820479
Invalid audio PTS: 19.841812 -> 20.319396
Invalid audio PTS: 20.340729 -> 20.822271
Invalid audio PTS: 20.843604 -> 21.321208
Invalid audio PTS: 21.342542 -> 21.649771
AV: 00:00:16 / 00:00:49 (32%) A-V: 0.000
Invalid audio PTS: 15.838500 -> 16.315958
Invalid audio PTS: 16.337292 -> 16.814833
Invalid audio PTS: 16.836167 -> 17.317687
Invalid audio PTS: 17.339021 -> 17.816521
Invalid audio PTS: 17.837854 -> 18.319562
Invalid audio PTS: 18.340896 -> 18.818500
Invalid audio PTS: 18.839833 -> 19.317500
Invalid audio PTS: 19.338833 -> 19.820479
Invalid audio PTS: 19.841812 -> 20.319396
Invalid audio PTS: 20.340729 -> 20.822271
AV: 00:00:14 / 00:00:49 (30%) A-V: -0.001
Invalid audio PTS: 15.339604 -> 15.817167
AV: 00:00:14 / 00:00:49 (30%) A-V: 0.475
Invalid audio PTS: 15.838500 -> 16.315958
Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).
AV: 00:00:15 / 00:00:49 (30%) A-V: 0.939
Invalid audio PTS: 16.337292 -> 16.814833
AV: 00:00:15 / 00:00:49 (30%) A-V: 1.404
Invalid audio PTS: 16.836167 -> 17.317687
AV: 00:00:15 / 00:00:49 (30%) A-V: 1.865
Invalid audio PTS: 17.339021 -> 17.816521
AV: 00:00:15 / 00:00:49 (31%) A-V: 2.329 ct: 0.059
Invalid audio PTS: 17.837854 -> 18.319562
AV: 00:00:15 / 00:00:49 (31%) A-V: 2.798 ct: 0.072
Invalid audio PTS: 18.340896 -> 18.818500
AV: 00:00:15 / 00:00:49 (31%) A-V: 3.255 ct: 0.092
Invalid audio PTS: 18.839833 -> 19.317500
AV: 00:00:15 / 00:00:49 (31%) A-V: 3.720 ct: 0.106
Invalid audio PTS: 19.338833 -> 19.820479
AV: 00:00:15 / 00:00:49 (31%) A-V: 4.188 ct: 0.119
Invalid audio PTS: 19.841812 -> 20.319396
AV: 00:00:15 / 00:00:49 (31%) A-V: 4.645 ct: 0.139
Invalid audio PTS: 20.340729 -> 20.822271
AV: 00:00:15 / 00:00:49 (31%) A-V: 5.114 ct: 0.152
Invalid audio PTS: 20.843604 -> 21.321208
Invalid audio PTS: 21.342542 -> 21.649771
AV: 00:00:33 / 00:00:49 (68%) A-V: 0.004 ct: 6.050
Invalid audio PTS: 34.090521 -> 34.572833
AV: 00:00:33 / 00:00:49 (68%) A-V: 0.480 ct: 6.057
Invalid audio PTS: 34.594167 -> 35.071792
AV: 00:00:33 / 00:00:49 (68%) A-V: 0.951 ct: 6.064
Invalid audio PTS: 35.093125 -> 35.570687
AV: 00:00:33 / 00:00:49 (68%) A-V: 1.408 ct: 6.084
Invalid audio PTS: 35.592021 -> 36.073771
AV: 00:00:33 / 00:00:49 (68%) A-V: 1.877 ct: 6.097
Invalid audio PTS: 36.095104 -> 36.572771
AV: 00:00:33 / 00:00:49 (68%) A-V: 2.341 ct: 6.110
Invalid audio PTS: 36.594104 -> 37.071667
AV: 00:00:33 / 00:00:49 (68%) A-V: 2.798 ct: 6.130
Invalid audio PTS: 37.093000 -> 37.574542
AV: 00:00:33 / 00:00:49 (69%) A-V: 3.267 ct: 6.144
Invalid audio PTS: 37.595875 -> 38.073500
Invalid audio PTS: 38.094833 -> 38.576563
AV: 00:00:34 / 00:00:49 (69%) A-V: 4.213 ct: 6.157
Invalid audio PTS: 38.597896 -> 39.075542
AV: 00:00:34 / 00:00:49 (69%) A-V: 4.670 ct: 6.177
Invalid audio PTS: 39.096875 -> 39.574438
AV: 00:00:34 / 00:00:49 (69%) A-V: 5.135 ct: 6.190
Invalid audio PTS: 39.595771 -> 40.077521
AV: 00:00:34 / 00:00:49 (69%) A-V: 5.603 ct: 6.204
Invalid audio PTS: 40.098854 -> 40.576333
AV: 00:00:34 / 00:00:49 (69%) A-V: 6.060 ct: 6.224
Invalid audio PTS: 40.597667 -> 41.079229
AV: 00:00:34 / 00:00:49 (69%) A-V: 6.529 ct: 6.237
Invalid audio PTS: 41.100562 -> 41.578146
AV: 00:00:34 / 00:00:49 (69%) A-V: 6.993 ct: 6.250
Invalid audio PTS: 41.599479 -> 42.077062
AV: 00:00:34 / 00:00:49 (69%) A-V: 7.450 ct: 6.270
Invalid audio PTS: 42.098396 -> 42.580062
AV: 00:00:34 / 00:00:49 (69%) A-V: 7.919 ct: 6.284
Invalid audio PTS: 42.601396 -> 43.078896
AV: 00:00:34 / 00:00:49 (69%) A-V: 8.383 ct: 6.297
Invalid audio PTS: 43.100229 -> 43.581792
AV: 00:00:34 / 00:00:49 (69%) A-V: 8.851 ct: 6.310
Invalid audio PTS: 43.603125 -> 43.963062
(Paused) AV: 00:00:45 / 00:00:49 (92%) A-V: 0.000 ct: 10.064
Exiting... (Quit)
This may be linked to #7 . But I decided to make it a child issue as it is reproduced in another way.
mpv --no-config video.mp4 (if applicable)Describe the bug
So I've been refining the GSR Script I use to replay (They launch on system startup), and I noticed that when saving replays they would save with some choppiness to them (latency perhaps?). Note that this is no longer a sync issue, as you will see in the video it is completely in sync. The issue is the chop.
To Reproduce
Just ran:
flatpak run --command=gpu-screen-recorder com.dec05eba.gpu_screen_recorder -w screen -fm cfr -f 60 -a "bluez_sink.C0_91_B9_DE_7C_AE.a2dp_sink.monitor" -ac aac -k hevc -c mp4 -r 60 -o /home/wolf/Videos
Expected behavior
It should sound normal, no choppiness at all.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
wolf@wolf-mint:~/Videos/Sound$ mpv --no-config Replay_2024-04-13_14-06-14.mp4
(+) Video --vid=1 (*) (hevc 1920x1080 60.000fps)
(+) Audio --aid=1 (*) (aac 2ch 48000Hz)
AO: [pulse] 48000Hz stereo 2ch float
VO: [gpu] 1920x1080 yuv420p
AV: 00:00:17 / 00:00:32 (55%) A-V: 0.296 ct: 4.253
Invalid audio PTS: 18.225604 -> 18.705146
Invalid audio PTS: 18.726479 -> 19.207104
Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).
AV: 00:00:17 / 00:00:32 (55%) A-V: 1.248 ct: 4.262
Invalid audio PTS: 19.228438 -> 19.709167
AV: 00:00:17 / 00:00:32 (55%) A-V: 1.715 ct: 4.275
Invalid audio PTS: 19.730500 -> 20.210083
AV: 00:00:17 / 00:00:32 (55%) A-V: 2.181 ct: 4.288
Invalid audio PTS: 20.231417 -> 20.710729
AV: 00:00:17 / 00:00:32 (55%) A-V: 2.641 ct: 4.308
Invalid audio PTS: 20.732063 -> 21.210854
AV: 00:00:17 / 00:00:32 (55%) A-V: 3.106 ct: 4.322
Invalid audio PTS: 21.232188 -> 21.711688
AV: 00:00:17 / 00:00:32 (55%) A-V: 3.572 ct: 4.335
Invalid audio PTS: 21.733021 -> 21.989146
AV: 00:00:20 / 00:00:32 (64%) A-V: 0.000
Invalid audio PTS: 19.730500 -> 20.210083
Invalid audio PTS: 20.231417 -> 20.710729
Invalid audio PTS: 20.732063 -> 21.210854
Invalid audio PTS: 21.232188 -> 21.711688
Invalid audio PTS: 21.733021 -> 21.989146
AV: 00:00:20 / 00:00:32 (63%) A-V: 0.000
Invalid audio PTS: 19.730500 -> 20.210083
Invalid audio PTS: 20.231417 -> 20.710729
Invalid audio PTS: 20.732063 -> 21.210854
Invalid audio PTS: 21.232188 -> 21.711688
Invalid audio PTS: 21.733021 -> 21.989146
AV: 00:00:19 / 00:00:32 (62%) A-V: 0.000
Invalid audio PTS: 18.225604 -> 18.705146
Invalid audio PTS: 18.726479 -> 19.207104
Invalid audio PTS: 19.228438 -> 19.709167
AV: 00:00:19 / 00:00:32 (62%) A-V: 0.000
Invalid audio PTS: 18.225604 -> 18.705146
Invalid audio PTS: 18.726479 -> 19.207104
Invalid audio PTS: 19.228438 -> 19.709167
AV: 00:00:19 / 00:00:32 (61%) A-V: 0.000
Invalid audio PTS: 18.225604 -> 18.705146
Invalid audio PTS: 18.726479 -> 19.207104
Invalid audio PTS: 19.228438 -> 19.709167
AV: 00:00:19 / 00:00:32 (60%) A-V: 0.000
Invalid audio PTS: 19.730500 -> 20.210083
Invalid audio PTS: 20.231417 -> 20.710729
Invalid audio PTS: 20.732063 -> 21.210854
Invalid audio PTS: 21.232188 -> 21.711688
Invalid audio PTS: 21.733021 -> 21.989146
AV: 00:00:19 / 00:00:32 (60%) A-V: 0.000
Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).
AV: 00:00:17 / 00:00:32 (54%) A-V: 0.296 ct: 0.263
Invalid audio PTS: 18.225604 -> 18.705146
Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).
AV: 00:00:17 / 00:00:32 (55%) A-V: 0.767 ct: 0.272
Invalid audio PTS: 18.726479 -> 19.207104
AV: 00:00:17 / 00:00:32 (55%) A-V: 1.235 ct: 0.285
Invalid audio PTS: 19.228438 -> 19.709167
AV: 00:00:17 / 00:00:32 (55%) A-V: 1.702 ct: 0.298
Invalid audio PTS: 19.730500 -> 20.210083
AV: 00:00:17 / 00:00:32 (55%) A-V: 2.168 ct: 0.312
Invalid audio PTS: 20.231417 -> 20.710729
AV: 00:00:17 / 00:00:32 (55%) A-V: 2.628 ct: 0.332
Invalid audio PTS: 20.732063 -> 21.210854
AV: 00:00:17 / 00:00:32 (55%) A-V: 3.093 ct: 0.345
Invalid audio PTS: 21.232188 -> 21.711688
AV: 00:00:17 / 00:00:32 (55%) A-V: 3.559 ct: 0.358
Invalid audio PTS: 21.733021 -> 21.989146
AV: 00:00:17 / 00:00:32 (55%) A-V: 0.294 ct: 2.262
Invalid audio PTS: 18.225604 -> 18.705146
Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).
AV: 00:00:17 / 00:00:32 (55%) A-V: 0.765 ct: 2.270
Invalid audio PTS: 18.726479 -> 19.207104
AV: 00:00:17 / 00:00:32 (55%) A-V: 1.239 ct: 2.277
Invalid audio PTS: 19.228438 -> 19.709167
AV: 00:00:17 / 00:00:32 (55%) A-V: 1.699 ct: 2.297
Invalid audio PTS: 19.730500 -> 20.210083
AV: 00:00:17 / 00:00:32 (55%) A-V: 2.166 ct: 2.310
Invalid audio PTS: 20.231417 -> 20.710729
AV: 00:00:17 / 00:00:32 (55%) A-V: 2.632 ct: 2.323
Invalid audio PTS: 20.732063 -> 21.210854
Invalid audio PTS: 21.232188 -> 21.711688
AV: 00:00:17 / 00:00:32 (55%) A-V: 3.570 ct: 2.343
Invalid audio PTS: 21.733021 -> 21.989146
AV: 00:00:27 / 00:00:32 (87%) A-V: 1.795 ct: 6.397
Although it seems mpv --no-config seems to be throwing sync issues. VLC replays it with no real desync.
No abnormal output from gsr, just updates on fps.
mpv --no-config video.mp4 (if applicable)Describe the bug
Audio will eventually desync from the video after a while
To Reproduce
gpu-screen-recorder -w screen -f 120 -a "$(pactl get-default-sink).monitor" -cr full -fm cfr -ac opus -k hevc -q very_high -o ~/videos/video.mkv
Expected behavior
Video and audio to remain in sync
Videos
Start of the recording:
~2 hours into the recording:
Desktop (please complete the following information):
I can provide more examples than the ones posted if required, it helps to watch the input button on the bottom right to see the difference in latency better, using a waveform makes this extremely obvious.
I'm not running any audio processing software.
I'm not able to reproduce this behaviour with obs.
I'm able to reproduce this on every game I've tried, the game in the videos is osu!
mpv --no-config video.mp4 (if applicable)Describe the bug
Flatpak version of the GTK version gives the error (screenshot) while the package it is asking me for is already installed on my system.
To Reproduce
Open latest GUI version installed from flathub with the correct packages installed
Expected behavior
Application opens without the encoder missing error
Screenshots
Desktop (please complete the following information):
Additional context
I know for a fact that they work because OBS can open for me just fine. Would prefer to use this though as it looks very promising and easy to use compared to the built in replay option in OBS. Thanks in advance :)
mpv --no-config video.mp4 (if applicable)Describe the bug
After changing from the workspace the game is on to another workspace and back (might take a few tries/minutes), the game stutters periodically.
To Reproduce
gpu-screen-recorder -w DP-3 -f 60 -q medium -r 20 -k h264 -c mp4 -ac aac -a "$(pactl get-default-sink).monitor" -o /tmp -v no -sc scripts/clip_upload.sh
This happens on sway and hyprland. On every game I played so far (Proton games: Overwatch, Helldivers II)
After killing the gpu-screen-recorder process, the stutters go away, else they don't seem to stop.
Expected behavior
No stutters
Screenshots
Recorded with gpu-screen-recorder: https://streamable.com/v2altf
screen recording in slowmotion from 144Hz: https://gitlab.freedesktop.org/drm/amd/uploads/f301d4e6ab3dcd0ffe4e89ecf47d3acb/ow.mp4 (from the AMD repo issue)
Screen recording was actual in-game footage, no recorded video.
(both too big to upload here)
Desktop (please complete the following information):
Additional context
I couldn't record these stutters with OBS, but gpu-screen-recorder seems to record them.
I have this issue for a long time now and thought its a driver issue >_<
Couldn't reproduce on desktop only
drm_info
Output always starts with this. There is no output as the stuttering starts.
[h264_vaapi @ 0x5646698fb280] ignoring invalid SAR: 0/0
[h264_vaapi @ 0x5646698fb280] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).
gsr info: gsr_kms_client_init: waiting for server to connect
kms server info: connecting to the client
gsr info: gsr_kms_client_init: server connected
gsr info: replacing file-backed unix domain socket with socketpair
kms server info: connected to the client
gsr info: using socketpair
[h264_vaapi @ 0x5646698fb280] ignoring invalid SAR: 0/0
[h264_vaapi @ 0x5646698fb280] Driver does not support some wanted packed headers (wanted 0xd, found 0x1).
mpv --no-config video.mp4 (if applicable)
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.