[Kdenlive-devel] Pop quiz to finish off KDE-Digest story

Mads Bondo Dydensborg mads at dydensborg.dk
Wed Nov 5 21:03:25 UTC 2008


onsdag 05 November 2008 skrev jb:
> On Wednesday 05 November 2008 20.40:16 Bugs Bane wrote:
> 
> > 1. I think I remember reading that Kdenlive takes advantage of
> > multi-core CPU's now. Is this accurate?
> Kdenlive itself is not using threads. But MLT now supports multi-threading 
> (using FFmpeg threads)... that's all I can say about that.

It is though, isn't? I think of e.g. the kthumb audiothumbproducer, which I, 
incidently, suspect of creating _some_ issues when pushed a bit...

For rendering, here is a snippet from Dan Dennedy, Feb 13. 2008:

"Also, you should no longer supply a real_time option with consumer
avformat because it now defaults to an improved multi-threaded
architecture that works even with non-threaded codecs! This just
separates the encoding from the decoding and processing. So, it will
only max out 2 processors. If you have more than 2 processors, then
you can enable the multi-threaded codecs using the threads property or
MLT_AVFORMAT_THREADS environment variable."

I read this to say, that by default, encoding and decoding always runs on 
seperate threads, which means that kdenlive rendering should always be able 
to max out at least two processers/cores. Additionally, should you have more 
than two cores, you can control the number of threads that ffmpeg uses as Dan 
states.

(Let me mention in passing, that kdenlive_start sets MLT_AVFORMAT_THREADS to 
the number of cores in your system :-)

Regards

Mads

-- 
Mads Bondo Dydensborg   mads at dydensborg.dk   http://www.madsdydensborg.dk/

"HELP, THE PRICE OF INFORMATION HAS FALLEN AND IT CAN'T GET UP"

            - http://www.shirky.com/writings/information_price.html




More information about the Kdenlive mailing list