Bug 380035

Summary:	use GLSL compositing/dissolve/zoom by default when GLSL is enabled
Product:	[Applications] kdenlive	Reporter:	Anton Gubarkov <anton.gubarkov>
Component:	Rendering & Export	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	fritzibaby, julius.kuenzel
Priority:	NOR	Flags:	fritzibaby: timeline_corruption+
Version First Reported In:	git-master
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Anton Gubarkov 2017-05-20 16:17:47 UTC

I've come across the page on compositing here https://kdenlive.org/project/timeline-track-compositing/ that explains many performance issues I have with kdenlive when compositing multiple tracks. The default High Quality compositing is CPU. Even when I do GLSL transition, kdenlive ends up doing CPU compositing.  As a result, the frame rate for every transition drops to 5 fps (on Intel 4700MQ/16GB RAM). If I add a CPU based effect, I get 1 fps slide show. 
The sound doesnt' play smoothly either. It stutters every second. 
I work with 28M FHD movies (up to 3 cameras at a time)

Can you please accept the request to make basic video operations in GLSL entirely to make edition smooth? 

Thanks

Comment 1 Anton Gubarkov 2017-05-20 18:55:29 UTC

Side note. The rendering (with manual compositing and GLSL overlay, GLSL wipe, GLSL pan/zoom, GLSL white balance transitions/effects only) produces max 20 fps (from render log measuring). I tested it on both VAAPI and NVENC encoders. Both are capable of over 90 fps encoding - ie encoder is not a bottleneck.

Comment 2 emohr 2018-10-13 10:51:54 UTC

This should be solved in the timeline refactoring coming in December 2018. VAAPI and NVENC implemented.

Comment 3 Julius Künzel 2021-03-03 00:18:31 UTC

Can you please update to the latest version (20.12.2 at the moment, https://kdenlive.org/en/download/) and report here whether this is still happening?

Comment 4 Bug Janitor Service 2021-03-18 04:33:46 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2021-04-02 04:33:38 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!