SUMMARY I am on Windows 10. If I archive a project into another folder, then try to open that project I get an error: The project file contains missing clips or files. These referenced files are in fact in the correct location. However, whoever wrote the code mixed Linux and Windows "paths". Look at the following referenced file from the error message... F:/Video Workbench/Electronics/E003 Raspberry Pi Camera Demonstrator/E003 P5 Camera Assembly\videos/MVI_0583_0.MP4 Notice that before the sub-directory videos, there is a \ instead of the appropriate / for a Windows computer. STEPS TO REPRODUCE 1. Create archive on Windows computer with mp4 files (not sure if file type is important or not. 2. Open resulting project file in the archived directory - you will get error code. 3. Look at path shown with the associated error code/report. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I flagged this as critical because if someone archives a project and doesn't check it before deleting the original, they will have lost a LOT of work.
Some archive issues are fixed. Please try with daily build: https://binary-factory.kde.org/job/Kdenlive_Nightly_mingw64/lastSuccessfulBuild/artifact/
Go to https://kdenlive.org/en/download/ scroll to the bottom. On the right side under Windows is the instruction how to install. Let me know if this instruction is OK.
Created attachment 132158 [details] attachment-17907-0.html Hello, I believe I did the update following those directions. The version number is now 20.08.0 I did a quick test on a small file and it seemed to work okay. Thank you! Chris DeHut On Tuesday, October 6, 2020, 09:38:54 AM CDT, emohr <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=427162 --- Comment #2 from emohr <fritzibaby@gmx.net> --- Go to https://kdenlive.org/en/download/ scroll to the bottom. On the right side under Windows is the instruction how to install. Let me know if this instruction is OK.
Thank you for the feedback. Glad to hear it works. We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.