Download Kdenlive Video Editor
Rosalinda Scollard
Up until recently, I've used the meager audio tools in kdenlive to edit audio on my a/v tracks. I'm pretty familiar with Audacity and I've read a number of people suggest using it to edit audio, leaving kden out of it entirely. What's your suggested workflow for doing this with a large number of audio (speech)-heavy clips?
I am new here and was just getting started learning kdenlive this weekend before it stopped working (it cant open my project file anymore - just crashes when importing video) so I decided to ditch kdenlive for Shotcut. I noticed I could open my kdenlive project file in Shotcut just fine, and it kept all my edits etc, but it doesnt appear to give me any kind of timeline view where I can start editing again. So my question is: can I import/open the kdenlive project properly in Shotcut to the point where I can get back to a proper timeline view and start making edits again, or is it best to just scrap the project and start again with Shotcut?
Before importing footage, you should save your project. This may seem strange given that your project is currently empty, but giving your workspace a name and location on your hard drive will establish the default skeletal structure for all Kdenlive projects. Kdenlive, like most professional-grade editors, generates lots of cache files and metadata. Starting your work without determining a place for all those temporary files to go simply means that you'll be dumping temp files into your default kdenlive directory and then abandoning them once you save.
Save your test project in its own subdirectory. I generally keep my Kdenlive project directories in a /kdenlive directory, with the default location being its own subdirectory called /kdenlive/default. This tends to work quite well and lends itself to being able to off-load old projects onto backup drives without worrying about whether or not that project is actually self-contained or whether I need to search through files to locate dependent media. Keeping the projects self-contained, even if it means replicating media, is quite liberating and should be used unless you are working in an infrastructure with stores of shared media that don't need to be saved along with your project data.
Creating a standard path for your projects is also helpful in the event that you need to migrate projects from one system to another. If the file paths are always /kdenlive/project-name, then Kdenlive losing track of media files is less likely. The path of your default Kdenlive project folder can always be changed via Project Menu > Project Settings > Project folder.
I'm trying to install it on F16 and have hit the launch failure due to something about MLT. What link/solution did you find that worked? Google is telling me to delete /.kde/share/config/kdenliverc which has not solved the problem for me.
Nice to see another kdenlive enthusiast! I admit I haven't messed around with 8.4 yet. What can I say? I'm conservative with my updates. But the bottom line is that Kdenlive is the Real Deal. I'd say if anyone tried it pre-8.x then it's definitely worth another look...and as for me, I can't wait to try 8.4 but...I will.
Nice write up Seth... looks ready for prime time.
Two questions --
- can kdenlive handle xdcam and p2 files? Both use versions of the .mxf container. Can kdenlive work with them natively or do they have to be converted/transcoded?
- Can kdenlive integrate with video server systems like Avid's airspeed & interplay systems or Grass Valley's K2 line? (Even better would be if there was an open source solution that's comparable to those set ups... but if there is I've never heard of it...)
Did I set something wrong, because on previous kdenlive an openSUSE Versions it was not using only one core.
The 20min clip took about 51 minutes to render, and there also no special compositing clips in that video, just an screencast with audio, an audio track and I reduce the volume of the Video clip.
So nothing special here.
I found kdenlive a month or two ago to quickly edit a school video project and I was looking for a free video editor that is easy to use like windows movie maker and has a lot of features like adobe premiere, and I found that kdenlive is the perfect mix.
I spent half day trying to make a movie on kdenlive, and guess what? Kdenlive was not installed with classic, because i did not notice notification, that classic is ignored for strictly confined snap. So I lost few hours of my work.
As @popey mentioned, if your personal folders and files are not on the same partition as snap, then you should grant your kdenlive-as-a-snap permission to access removable-media which actually means access to anything under /media, /mnt and /run/mnt.
I've been using kdenlive the KDE Non-LInear Video Editor for editing videos for my uni's alumni club for a while and quite like this programme. With KDE Plasma 5, the new desktop and toolkit version on the horizon, the kdenlive developers are porting their programme to a new base.
The second important step is to tell makepkg to leave the debugging symbols in so you can get a backtrace of the bug in the first place. Arch builds it's packages without debugging symbols by default so you have to compile every software you want to debug manually. This is not a huge problem in this case as we're using the development branch of kdenlive so there are no stable builds anyway.
I hope this helps new users and also helps the kdenlive guys get more bugs reported. The awesome thing about opensource is that I don't have to wait for a release for months. Jean-Baptiste Mardelle kdenlive's lead developer had a fix out for one of my issues in as fast as 17 minutes.
I will accept an authoritative negative answer to the effect of "this is just not possible, full stop", coming from an expert who knows kdenlive through and through. Knowledge of impossibility is valuable. I will then know that I must be more careful to avoid the problem. For example, whenever I split a clip, I could back the uncut version on an unused track: a manually maintained undo stack. STILL better than constantly grouping and ungrouping and having to remember what must be grouped and what not.
I can't confirm but it really looks like kdenlive can't do this. I've only started using kdenlive today, but spent most of it searching for how to do this. But I found a way which I hope helps, by manually editing the .kdelive save file. If you save it, make a cut, then save as a different .kdenlive file, you can see the difference, e.g:
Kdenlive is running as user "kdenlive", with home folder /home/kdenlive, but with read-write permission under /files. The installer, Appi or Flapi, creates /files/apps/kdenlive, so this is where I created the project, or rather tried to.
I created folders and some video files for the quick-start, under /files/apps/kdenlive/quickstart-tutorial, but this is where ran into trouble. In Puppy, we usually do not have to be concerned with folder and file permissions, but now it has become a problem.
Note, the problem is only for folders created by the administrator. If the administrator copies video and audio files into /files/apps/kdenlive/quickstart-tutorial, no problem. The files have permissions 755 and Kdenlive is able to read them, which is all that is required.
Yesterday I installed alsa-utils, and restored the defaults in kdenlive->Settings->Configure Kdnelive->playback and voilà, sound.
Thank you for your attention. It will make the curfew much more endurable!
This looks like an application issue.
Have you already tried looking into the KDE bug report?
Attached below is a link filtered by product "kdenlive" and containing the word "crash" (you can change the filter of course), there are a few reports which might look like yours, but you are the only one who can check the details.
_status=__open__&content=crash&no_redirect=1&order=changeddate%20DESC%2Cpriority%2Cbug_severity&product=kdenlive&query_format=specific
You just need to type in "kdenlive" into the console and it should throw up your error message there. If it says "Cannot mix incompatible Qt library" then try typing in "sudo pacman -Rns qt5-stylesplugin" to remove that package, everything should hopefully work then. If that is the issue then those two simple commands in the terminal should hopefully solve your problem
end of output.
With that, it stands still. Obviously tries to do something it cannot do. Bt as I only tried tp load one jpg file, it's not that the program could be busy loading it. What I see in that output, and in the program, is that it gets stuck trying to create the thumbnail for the object Iimported.
But judging by the long list of problems my install is really a wreck. So with that command you gave me above I will erase it, and also look for some config files that needs to get eliminated.
Then I will retry to install it. I have seen that there are different versions. Kdenlive, kdenlive-git, Kdenlive appimage. And from what you wrote above, I should try not to install a version from chaotic-aur?
In the meantime I also tried, if I could install Kdenlive in a Garuda live version, running from USB installation ISO. But that also didn't work. The installation went through with hundred of errors, and the app was available in the App Launcher. But it wouldn't even start. From this experience I take that I will watch carefully what errors I get during the installation process. If I can get it, I will post that log here afterwards.
Until then you're in some luck, you can download and enable flatpak and use the flatpak version of kdenlive, which will have all the dependencies it needs packed into the application itself so it can run perfectly out of the box. That should be a good temporary solution, here's a quick guide on how to set that up.
f448fe82f3