Hey! I’ve always been a Davinci Resolve user, however, recently I’ve just been getting more and more errors and crashes and bugs and whatever else with it so I’m trying out KdenLive instead. However, the playback is absolutely atrocious for me, it plays at like 1fps which is just unusable. Is there an easy fix at all? some setting that i need to switch? something i can do? Thanks in advance.
You can enable and use proxies for your source clips, reduce the project monitor resolution, and use the preview render feature for areas that are effect heavy.
Hey! Sorry for the late reply, went to sleep then had work. The thing that concerns me, is davinci processing these exact same files has 0 issue with playback without using proxies, i have also tried reducing the resolution and it doesnt help at all, and there are no effects on the clips at all so far, the playback has been too low framerate for me to make any edits at all. I shouldnt need to use proxies here, davinci can run them just fine, why not KdenLive? Plus, i have over 60gigs of clips and thats without proxies, if i generate proxies for all of these it will take up like a quarter of my drive which i dont want.
Perhaps because DR has a team of paid programmers that allow the SW to use the GPU, and Kdenlive is the work of volunteers that don’t get paid and have other jobs to keep them afloat?
1 Like
FWIW, I found exactly the opposite. One of the PCs I use for editing is a modest 8th Gen i5 with 8GB RAM and an 256GB SATA SSD. DaVinci is slow and pretty unusable on that, mainly I think due to the lack of RAM, but Kdenlive works fine with normal HD material, with virtually no lag, whatever I’m doing.
I feel like a video editing software should be able to run like, basic 1080p H.264 video without lagging? Is that like, actually a big ask (genuine question)? I feel like my KdenLive isn’t running as well as i would expected it to run, i was kinda hoping it would run better than Davinci.
There are lots of things that can bottleneck video playback - and if you’re concerned about resource starvation with only 60GB of HD clips, then my first guess is your system has no shortage of candidates for being that bottleneck.
But that’s about where guessing ends in its usefulness for explaining anything about this. 1fps 1080p H.264 with no effects says you’ve fundamentally starved something - but from the information you’ve given us, all we can say for sure is “No, that’s not normal, you have a problem that’s ‘specific to you’ which you’ll need to investigate”.
In regard to jittery playback, I found this interesting suggestion while searching. copied and pasted a specific suggestion. Not sure this will help and perhaps dated but hopefully it sparks a related fix?
-begin-
Your project is too large
If your project is made up of multiple large clips with many edits each, you may want to decrease the session size by creating a separate project for each large file, perform your edits, then merge the edited files from the separate projects into a new “master” project. This will reduce memory load and allow you to easily make changes only to certain segments without putting your whole production at risk of corrupting.
-end-
Source:
60GB of HD video is not a large project.
That wasn’t my choice of a ‘bold’ heading. It was copied and pasted from the source listed along with the following paragraph. I figured the suggestion of breaking-up the project into smaller and separate pieces was an interesting approach. But ok, in regard to, “60GB of HD video is not a large project”. I learned something. Thank you.
Before anyone can try to find a solution, you need to provide your setup information: hardware, OS, etc. As @Ron mentioned, you didn’t provide enough info for us to go on (FYI, this is why help posts like yours often start by listing hardware+software specs).
As for settings you can change, I suppose you could start by running the Config Wizard under Settings in the Menubar (default shortcut Ctrl+M) and check if you have hardware acceleration enabled. You could also try to make a new project to see if it is a project-related issue, and if you really want to, you could completely uninstall Kdenlive and try all over again with a fresh install and configs.