Jump to content

Archive:Kdenlive/Manual/Windows Issues/en: Difference between revisions

From KDE UserBase Wiki
FuzzyBot (talk | contribs)
Importing a new version from external source
FuzzyBot (talk | contribs)
Importing a new version from external source
Line 3: Line 3:


The current '''Kdenlive''' on Windows® (April 2019, version 19.04.0) has a few issues that have workarounds. The purpose of this wiki page is to document these issues and their workarounds.
The current '''Kdenlive''' on Windows® (April 2019, version 19.04.0) has a few issues that have workarounds. The purpose of this wiki page is to document these issues and their workarounds.
===First time use of Kdenlive===
That <tt>kdenliverc</tt> is correct set up please start Kdenlive twice (start -> close -> start). Then start your work.
===Intel graphic card driver===
The newest driver version x.6890 and x.6912 lead to a corrupted Kdenlive GUI. Please downgrade to version [https://downloadcenter.intel.com/download/28731/Intel-Graphics-Windows-10-DCH-Drivers x.6709] which solves the issue.


===Timeline: right-click menu close immediately after releasing mouse button===
===Timeline: right-click menu close immediately after releasing mouse button===

Revision as of 20:10, 4 July 2019

Windows Issues

The current Kdenlive on Windows® (April 2019, version 19.04.0) has a few issues that have workarounds. The purpose of this wiki page is to document these issues and their workarounds.

First time use of Kdenlive

That kdenliverc is correct set up please start Kdenlive twice (start -> close -> start). Then start your work.

Intel graphic card driver

The newest driver version x.6890 and x.6912 lead to a corrupted Kdenlive GUI. Please downgrade to version x.6709 which solves the issue.

Timeline: right-click menu close immediately after releasing mouse button

Don’t use the style Fusion.

Go to: SettingsStyle → choose Default or Windows.

Icons are missing

Go to: settings → untick force breeze icon theme. Kdenlive restarts and you should see the icons.

Cannot open projects made with previous version, timeline snaps back, cannot import clip

Press Win + R (Windows key and R key simultaneously) and type appdata. Go to local and within it rename kdenliverc to kdenliverc.old. Start Kdenlive -> do nothing -> close Kdenlive -> and restart Kdenlive again.

If you have still problems delete proxy clips and other cached data by going to Project menu → Project SettingCache Data tab → there you can delete cached data.

If you have still problems try Any critical bug.

Windows 10: timeline stuttering or Kdenlive hangs.

Most probably you got a major Win10 update (i.e 1809). If so you have to update all drivers for audio and video.

Intel driver can be updated with this updater: https://downloadcenter.intel.com/en/download/28425/Intel-Driver-Support-Assistant.

"Clip is invalid, will be removed"

This bug can appear if you do a clean reinstall of Kdenlive (see above). Simply close and open Kdenlive once, and it should be fixed.

Additionally this can be a problem either with the kdenliverc file (see here Cannot open projects) or you have some mismatch in the "local" folder (see here Any critical bug).

Any critical bug

This describes the process of doing a clean install on Windows®.

Firstly, delete your normal Kdenlive folder (containing the application)

Access the Appdata folder (Win + R and then type APPDATA in full caps). Go to local and search for folder kdenlive.

Note

If you have any saved effects or clips stored in your library, make a backup of the library folder.


Then once you have backup up your library folder, delete the kdenlive folder.

Reinstall the latest version of Kdenlive from the download page

JPG files appear as white picture after rendering

This issue should be solved with Windows version 19.04.0. If not convert the JPG to PNG and it renders correctly.

Play/Pause Issue

This issue is solved with Windows version 18.08.2 (30. Oct 2018). Get the current version from the download page.

Qt rendering crash

When switching from kdenlive for windows 17.12 → 18.04/18.08, a Qt rendering crash appears. To make sure this doesn't happen, you need to edit the kdenliverc file in the appdata/local folder. To access your appdata, press Win + R (Windows key and R key simultaneously) and type appdata. Go to local and within it rename kdenliverc to kdenliverc.old.

Kdenlive cannot be deleted, running process on exit

This issue is solved with Windows version 18.12.1. Get the current version from the download page.

If you want to reinstall Kdenlive or re-run Kdenlive, it may tell you "The file or folder is open in another program". Windows® then won't let you delete or re-run Kdenlive.

To fix this you have to kill the running process: press and hold Ctrl + Shift + Esc & expand the task manager by clicking all details. Then find kdenlive.exe & dbus-daemon.exe, and click End task for both of them.

Or download the File:Kdenlive-kill.zip. Unpack it and just double-click the batch file which kills all running Kdenlive processes.

Kdenlive cannot be uninstalled

If the uninstaller doesn't work you can delete following folder: C:\Program Files\kdenlive. You have to manually delete in the start menu the Kdenlive folder.

Kdenlive crash or green Monitor

Get all newest Windows® updates. Afterwards, update your graphic card driver and your sound card driver and your printer driver. Some crashes could occur of incompatibility of the graphics card and sound card with the newest Windows®10 updates (18.09 update). After you have updated the drivers re-start the computer and try again by starting kdenlive.exe.

If this is not solving the problem switch your standard printer to “Microsoft XPS Document Writer” and try again to start Kdenlive.

Delete the kdenliverc file as descript here under Qt rendering crash.

Make sure you set processing thread to 1: Ctrl+Shift+, (comma)EnvironmentProcessing thread → set to 1

General Issues

The current Kdenlive version (November 2018, version 18.08.3) has a few issues that have workarounds.

Audio Pops and Ticks in Render

If this problem appears make sure the audio file is: 16-bit PCM WAV.