Kdenlive 18.08.2 is out bringing usability improvements and a crash fix. The Windows version is also becoming more stable with every release and this version brings fixes to the translation installation and the introduction of a crash report.
In other news, the Refactoring is moving steadily ahead and we will release a wider test beta version soon, stay tuned. Also the refactoring branch is now building automatically on KDE’s automated integration system (CI), and all the regressions tests pass. This means that after each change to the source code, the CI will run the tests to check that no regression happens. On the sysadmin front we are cleaning up our bug tracker in preparation for the 18.12 release.
Bug fixes:
- Improve missing luma detection (region transition) – fixes project crash. Commit.
- Home/End now also seek in clip monitor. Commit.
- Update AppData for upcoming release. Commit.
- Windows crash reports. Commit.
- Update authors. Commit.
- Fix double clicking a title clip in bin tries to rename instead of opening the title dialog. Commit.
Get it:
kdenlive v. 18.08.2 funciona muy bién en WINDOWS 10 64-bit. Es por lejos el editor de videos open-source más avanzado y estable para el glorioso, hermoso, perfecto y maravilloso WINDOWS.
Just a tiny thing here. It’s not very important but annoying in the same time. In the Help tab and About Kdenlive, it is written:
Copyright © 2007–2017 Kdenlive authors
Maybe you should update to 2018 🙂
Open a bug report
Every time I get news about Kdenlive I get excited, can’t wait for the refactoring to finish so we can get more features and a better, more stable program
I use Kdenlive since version 0.9.6… Honestly, 0.9.10 is the most stable so far. I wish new feature’s development could be frozen for a bit in order to improve bug eradication.
Kdenlive is an impressive project.
Still using Kdenlive on Linux and delaying Video Editing Software migration (on Windows) as much as possible…
Interesting, what has stopped you from moving to the latest versions (They have been quite reliable and stable.)? Actually don’t know if you’ve followed the development but the refactoring is actually meant to make it more stable and maintainable (code-wise) and we are working very hard to have it ready in December.
Hi Farid,
I start to use Kdenlive 0.9.6 since 2012. Very impressed with features. Didn’t noticed big improvements with 0.9.8.
I used 0.9.10 from 2014 until 2016.
Then I moved to Kdenlive 16.12.x and nowadays I’m using Kdenlive 18.04.1.
0.9.10 was almost rock solid running either on Mint Kde or Mint Xfce editions.
I reckon that 18.04.1 is faster than the older versions (I produced 1024×576 videos with older Kdenlive versions and now I’m producing HD and full HD projects with 18.04.1).
Not a big fan of KDE, running Kdenlive on Mint 18.3 Xfce edition.
Again, I’m very grateful for Kdenlive project but I feel I need more stability and performance.
I also used Kdenlive old version (I do not remember which one) and the main difference – in the old version, the Speed can be changed to 100,000%, and in the new versions – 20,000%. And when Compiling in earlier versions there is more variety of settings (bitrate)
Looks good, Is there a way to make the cursor in the title text editor a little more visible? It’s difficult to see.
Updates have come and now this is the error on Linux Mint 19 and Ubuntu 18.04
Пакеты, имеющие неудовлетворённые зависимости:
kdenlive : Зависит: libmlt++3 (>= 6.10.0+git201810170323~ubuntu18.04.1) но 6.6.0-1build1 будет установлен
Зависит: libmlt6 (>= 6.10.0+git201810170323~ubuntu18.04.1) но 6.6.0-1build1 будет установлен
E: Невозможно исправить ошибки, у вас отложены (held) битые пакеты.
Sorry we cannot provide distribution assistance as this is a packaging issue. We strongly recommend you use the AppImage version available in the download section.
But AppImage haven`t GPU using support, so what the reason to use AppImage??? My fast comp isnt`t fast…
GPU effects are not ready for production so you are not missing out on anything really.
Kdenlive 18.08.2 (for wonderful & amazing WINDOWS 10):
more visible markers please!
ok! Ignore this comment. I already found the solution.
thanks for this wonderful software