Make multiple threads work correctly (even) on fast systems
Closed, ResolvedPublic

Description

While Kdenlive already supprts using multiple threads for timeline preview in principle, there are multiple reports that Kdenlive then becomes unusable on certain fast systems, such as Core i7 machines.

In particular, there seems to be some race conditions that cause preview rendering of a single frame to complete faster than the UI thread triggering the render operation. In consequence, update of the playhead doesn't work anymore: when clicking on a position in the timeline ruler, the small ruler mark moves to this new position, but the playhead never catches up. In turn, it's impossible to edit in the timeline, because the playhead doesn't correctly reflect its real position. When playing back the timeline, playhead operation works as expected though.

thediveo created this task.May 22 2016, 7:26 AM
thediveo renamed this task from Make multiple threads work on fast systems to Make multiple threads work correctly (even) on fast systems.Jun 26 2016, 6:43 PM
jessed added a subscriber: jessed.Aug 15 2016, 6:59 AM

This would be a significant benefit. The more native processing power Kdenlive can pull from the hardware for editing, the better. It feels like wasted potential when it can't be utilized, and users of all types would be much more likely to invest their trust in an editing program that they know is taking full advantage of their hardware. I second this.

jlskuz closed this task as Resolved.Nov 12 2023, 3:25 PM
jlskuz claimed this task.
jlskuz added a subscriber: jlskuz.

There have been several stability improvements on this topic. However it is also limited by some thirt-party dependencies upstream. Closing.