In my large project I have around 408 clips and photos. Open the project takes over 10 minutes on an i686 with 2 gigs of ram and a fast SSD. I think this is a bit too much. Checking strace output during loading of the project, when btw the popup dialog is not updated at all, shows that for example all JPG files are opened and checked multiple times: strace -ttt -e open -p 5786 1504124281.861213 open("/home/mcfrisk/Videos/20170205_bayerische_wald_nesselwang _ski_tour/nesselwang/DSC08454_taksi_ok.JPG", O_RDONLY|O_LARGEFILE) = 21 1504124282.802752 open("/home/mcfrisk/Videos/20170205_bayerische_wald_nesselwang _ski_tour/nesselwang/DSC08454_taksi_ok.JPG", O_RDONLY|O_LARGEFILE) = 21 1504124283.295829 open("/home/mcfrisk/Videos/20170205_bayerische_wald_nesselwang _ski_tour/nesselwang/DSC08454_taksi_ok.JPG", O_RDONLY) = 21 1504124283.309766 open("/home/mcfrisk/Videos/20170205_bayerische_wald_nesselwang _ski_tour/nesselwang/DSC08455_j.JPG", O_RDONLY|O_LARGEFILE) = 21 1504124284.242783 open("/home/mcfrisk/Videos/20170205_bayerische_wald_nesselwang_ski_tour/nesselwang/DSC08455_j.JPG", O_RDONLY|O_LARGEFILE) = 21 1504124284.731773 open("/home/mcfrisk/Videos/20170205_bayerische_wald_nesselwang_ski_tour/nesselwang/DSC08455_j.JPG", O_RDONLY) = 21 Surely it would be enough to open and check the file only once. For videos for which I'm using tiny proxy files, opening seems to be faster. Also, the project loading is not utilizing multiple CPU's and GUI is not updated. Would be nice to have multiple processes or threads handling the file checks, and to have some kind of updated progress meter when doing work for several minutes.
Created attachment 107600 [details] backtrace 1
Created attachment 107601 [details] backtrace 2
Created attachment 107602 [details] backtrace 3
Created attachment 107603 [details] backtrace 4
I set breakpoints to open() with gdb when kdenlive is opening my large project. Attached traces show that a single JPG file is opened four times with different backtraces.
Thanks for your report! Can you please update to the latest version (https://kdenlive.org/en/download/) or rebuild from master and check if this is still relevant?
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!
Can you try to reproduce this issue with latest master version please?
This is likely fixed in 21.12.3 and since there was no feedback recently I am going to close. Feel free to reopen if still relevant.