You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Debian 12.7 Linux per 'cat /etc/debian_version'. I am using SimpleScreenRecord from Debian 12 package 'simplescreenrecorder'. The version per 'simplescreenrecorder --version' is:
SimpleScreenRecorder 0.4.4
Compiled with GCC 12.2.0
Qt: header 5.15.8, lib 5.15.8
libavformat: header 59.27.100, lib 59.27.100
libavcodec: header 59.37.100, lib 59.37.100
libavutil: header 57.28.100, lib 57.28.100
libswscale: header 6.7.100, lib 6.7.100
BTW, I love the 'Select window...' feature, no math mistakes. If I capture a browser window or whatever with MKV container, H.264 codec (supported by my GeForce RTX 2080 SUPER Mobile / Max-Q), preset 'superfast', and allow frame skipping is on, with or without sound I get a file that has 30.303 frames per second according to Kdenlive clip properties panel and 30.30 fps according to command-line tool ffprobe from ffmpeg, which more fully shows:
I can reproduce this easily on my laptop and had the same issue two years ago on Debian 11 but did not know it. Today if I use OBS Studio, Kdenlive and ffprobe report '30' frames per second. For fully, ffprobe says '30 fps, 30 tbr, 1k tbn'. I am glad your 'Select window...' feature gives me the pixel height of the main panel I like to have across the top of the screen area, which I need to correctly 'crop' the full desktop not the panel (as far as I can tell, not experienced user of OBS Studio).
I am unsure how bad the weird 30.303 fps is for video inputs for a video production. I have more than a few video captures I plan to use if I can, and it seems I can get good results. I have not seen jitter using Bforartists (Blender with facelift). One only one capture a blank frame was the last frame of the reference strip on the Bforartists timeline. Several other captures did not do that.
If you have any idea how to best handle 30.303 fps for a final render of 30 fps, I would be glad to hear it. If you have any questions on this apparent bug, I suppose you can ask me via GitHub. Thanks.
The text was updated successfully, but these errors were encountered:
I am using Debian 12.7 Linux per 'cat /etc/debian_version'. I am using SimpleScreenRecord from Debian 12 package 'simplescreenrecorder'. The version per 'simplescreenrecorder --version' is:
SimpleScreenRecorder 0.4.4
Compiled with GCC 12.2.0
Qt: header 5.15.8, lib 5.15.8
libavformat: header 59.27.100, lib 59.27.100
libavcodec: header 59.37.100, lib 59.37.100
libavutil: header 57.28.100, lib 57.28.100
libswscale: header 6.7.100, lib 6.7.100
BTW, I love the 'Select window...' feature, no math mistakes. If I capture a browser window or whatever with MKV container, H.264 codec (supported by my GeForce RTX 2080 SUPER Mobile / Max-Q), preset 'superfast', and allow frame skipping is on, with or without sound I get a file that has 30.303 frames per second according to Kdenlive clip properties panel and 30.30 fps according to command-line tool ffprobe from ffmpeg, which more fully shows:
Input #0, matroska,webm, from 'simplescreenrecorder-2024-10-26_13.51.21.mkv':
Metadata:
ENCODER : Lavf59.27.100
Duration: 00:00:18.17, start: 0.000000, bitrate: 371 kb/s
Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], 30.30 fps, 30 tbr, 1k tbn
Metadata:
DURATION : 00:00:18.167000000
I can reproduce this easily on my laptop and had the same issue two years ago on Debian 11 but did not know it. Today if I use OBS Studio, Kdenlive and ffprobe report '30' frames per second. For fully, ffprobe says '30 fps, 30 tbr, 1k tbn'. I am glad your 'Select window...' feature gives me the pixel height of the main panel I like to have across the top of the screen area, which I need to correctly 'crop' the full desktop not the panel (as far as I can tell, not experienced user of OBS Studio).
I am unsure how bad the weird 30.303 fps is for video inputs for a video production. I have more than a few video captures I plan to use if I can, and it seems I can get good results. I have not seen jitter using Bforartists (Blender with facelift). One only one capture a blank frame was the last frame of the reference strip on the Bforartists timeline. Several other captures did not do that.
If you have any idea how to best handle 30.303 fps for a final render of 30 fps, I would be glad to hear it. If you have any questions on this apparent bug, I suppose you can ask me via GitHub. Thanks.
The text was updated successfully, but these errors were encountered: