https://bugs.kde.org/show_bug.cgi?id=512987
kido <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |FIXED --- Comment #4 from kido <[email protected]> --- (In reply to Bernd from comment #3) > >Why doesn't Kdenlive use the GPU to its full capacity in this case? Or if it > >can't use the GPU, why doesn't it use the CPU to its full capacity? > > I am guessing here, but MLT doesn't "know" there are no effects or > compositions and just touches every frame looking for something to do. That > still takes time. And because parallel processing of frames can lead to > artifacts (frames may need to "know" about previous ones and following) it > cannot be applied throughout. So once MLT has processed the frame and sends > it off to the GPU for encoding enough time has passed for the GPU to have > finished previous tasks and been sitting idle. > > Your examples just illustrate that Kdenlive/MLT is missing a step where it > determines what is to be done, and if it's just a rescale and encode > stepping out of the way and have ffmpeg do its job. But how often is that > really the case? in 99.999% of the cases a project has at least several cuts > and more than one clip. Thanks for the detailed answer. Now I understand a little better how Kdenlive works. > > Work is underway to make better use of GPUs during editing, playback, and > rendering. But resources are few and other tasks are many ... Thank you for your work. I wish you success in achieving your goals. -- You are receiving this mail because: You are watching all bug changes.
