SUMMARY On Windows it appears that Kdenlive locks proxy files such that it fails to recreate proxies when switching encoding profiles (Kdenlive prompts to rebuild proxies and then fails) and continues to use the previous proxies. This is also confusing if the new proxy encoding uses the same file extension as the new one as exiting and restarting Kdenlive will result in the old proxies *still* being used. Only by exiting and then deleting the proxies is it possible to get Kdenlive to regenerate new proxies with the desired profile. This also appears to cause errors when creating a new project and adding a few video files. If proxies are generated, they will go into the users directory and then when the project is saved, Kdenlive will prompt to move these files to the new directory which fails. STEPS TO REPRODUCE 1. Open a project with one or more video files. 2. Enable proxies and ensure that the proxies are build (P appears on the clip thumbnail). 3. Open Project Settings / Proxy tab and select a new Encoding Profile that uses the same file extension. 4. Kdenlive prompts to recreate all proxy clips for this project? Click Yes. 5. Note that nothing changes with the proxies and they are not rebuilt. This was quite confusing when experimenting with proxy profiles. Related to this file locking issue is the following: 1. Create a New project and ensure that proxies are enabled (on the Proxy tab). 2. Add a new video file to the project bin and ensure it creates a proxy. 3. In the Project Settings, if not already select, check "Use parent folder of the project file as project folder". 4. This should prompt for a location to save the project and then prompt to move all temporary files to the new location. (If not, save the project.) 5. Clicking "Continue" will result in an error popup trying to move the cachefiles/ files as well as moving the project folder .../proxy/* files that were previously generated. (This actually results in 2 different message boxes appearing at the same time.) 6. This error appears to result in the Project Setting to "Use parent folder of the project file as project folder" (set in #3) being cleared and cache and proxy files reverting to end up in the user's AppData/Local/kdenlive folder. OBSERVED RESULT When changing the proxy encoder, the user still sees the previously generated (incorrect) proxy files (no error message is displayed). When saving a new project, the user sees error messages when a custom project folder (or the project file's folder) is used. EXPECTED RESULT When changing the proxy encoder and prompted to rebuild proxies, the user expects to see proxies being rebuilt and then the results of the selected encoder. When saving a new project, the user should not see errors due to file locking. Cache and proxy files should be properly moved to the new project folder. SOFTWARE/OS VERSIONS Windows: 11
Thanks for your report. This should be fixed im the upcoming 22.12.0 version that will be released in one week. In the meantime, if you have time you can you check against the daipy development Appimage to confirm the fix: https://binary-factory.kde.org/view/AppImage/job/Kdenlive_Nightly_appimage-centos7/
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Jean-Baptiste Mardelle from comment #1) > Thanks for your report. This should be fixed im the upcoming 22.12.0 version > that will be released in one week. In the meantime, if you have time you can > you check against the daipy development Appimage to confirm the fix: > https://binary-factory.kde.org/view/AppImage/job/Kdenlive_Nightly_appimage- > centos7/ I have just tested this in 22.12.0 and both bug still appear to be there. Switching from "x264" to "ProRes" for proxy format does not rebuild the proxies and the .mov files remain locked until kdenlive is exited.