Bug 467591 - Spectacle records video with low framerate (25fps)
Summary: Spectacle records video with low framerate (25fps)
Status: RESOLVED FIXED
Alias: None
Product: KPipeWire
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 6.6.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-20 00:27 UTC by Patrick Silva
Modified: 2023-05-18 14:58 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
memory leak (468.24 KB, image/png)
2023-05-17 15:53 UTC, Patrick Silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2023-03-20 00:27:52 UTC
STEPS TO REPRODUCE
1. records your screen with Spectacle on Wayland session
2. 
3. 

OBSERVED RESULT
the framerate of the video recorded with Spectacle is 25 fps. Mouse pointer movements are barley noticeable
in the recorded video.

EXPECTED RESULT
higher framerate

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Graphics Platform: Wayland
Comment 1 Nate Graham 2023-05-17 13:46:13 UTC
This should be substantially better in the final version, and with Plasma 5.27.5. Can you confirm that?
Comment 2 Patrick Silva 2023-05-17 15:53:58 UTC
Created attachment 159034 [details]
memory leak

Currently the framerate is 60 fps, but the mouse pointer is still barely visible while moved.
And the memory leaks continuously while Spectacle records the screen and I move the mouse pointer, until the whole computer stops. Please see the attached screenshot.

Operating System: Arch Linux 
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9
Kernel Version: 6.3.2-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 2 × Intel® Celeron® CPU G1820 @ 2.70GHz
Memory: 23,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics
Comment 3 Nate Graham 2023-05-18 14:58:07 UTC
The memory leak is a different issue: Bug 469005.