Bug 382422

Summary:	Use all threads by default
Product:	[Applications] kdenlive	Reporter:	Matthias <shalokshalom>
Component:	User Interface	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	CONFIRMED ---
Severity:	normal	CC:	fritzibaby
Priority:	NOR	Flags:	fritzibaby: timeline_corruption+
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description Matthias 2017-07-17 07:23:37 UTC

Currently, the threads selection is hide under the "more options" field plus Kdenlive use 1 (!) single thread on all machines, while the very most today offer at least 4. I think that is a waste of resources and puts a bad light on Kdenlive, since the very most people who start to use it, might thing it renders just for its own fails so slowly. Which is, more or less, even the case.

Comment 1 emohr 2018-12-10 17:08:09 UTC

Processing thread: use only 1 (solving this issue is ongoing).

For rendering here some input:
render TIME 2min42 sec (off Parallel, threads:3)
render TIME 2min45 SEC (on parallel,thread:3)
render TIME 7min3 sec (on parallel, thread:1)
render TIME 2min2sec (on parallel,thread:0)

Comment 2 emohr 2023-10-20 18:10:00 UTC

Some of the effects Kdenlive uses are not thread save. So, we set 1 thread by default to avoid crashes or other unexcepted behaviors like not proper rendered files. 
Closing this bug.

Comment 3 Matthias 2023-10-21 09:34:55 UTC

How do we inform the user currently about this?

It could simply set the threads to the maximum possible by default?
Whats the point of reducing this by default for all cases, who can use more?
Seems like we can fine tune this and indicate somewhere, which effects are thread save.