Created attachment 124648 [details] popup message when proxy is created SUMMARY When using kdenlive with image sequence from 3D source (often png in my case), I activate proxy for it. Kdenlive creates the proxy as usual, but is unable to open it. When i opened the proxy file, it is in fact corrupted or at least impossible to open with vlc or djview. STEPS TO REPRODUCE 1. Import any png image sequence into kdenlive 2. activate proxies for it 3. wait for proxy to be created OBSERVED RESULT Proxies are not used because kdenlive is unable to open it EXPECTED RESULT Proxies used for it, better playback SOFTWARE/OS VERSIONS Linux/KDE Plasma: ubuntu 19.10 Kdenlive file/version : kdenlive-19.12.0a-x86_64.appimage ADDITIONAL INFORMATION console output when starting proxy creation : // SETTING CLIP PROPERTIES: QMap(("kdenlive:proxy", "/home/tonton/.cache/kdenlive/proxy/e35a896edf80b2c907f98ac5ec14b60a.mkv")) ################### JOB finished 7 ################### JOB finished 8 * * * ** * * * WARNING + + + JOB NOT CORRECT FINISH: 8
Git commit e083567cc30cf5af56ea441651b2322d63eb63f8 by Jean-Baptiste Mardelle. Committed on 23/12/2019 at 18:29. Pushed by mardelle into branch 'release/19.12'. Fix proxying of slideshow clips. M +2 -0 src/jobs/loadjob.cpp M +12 -0 src/jobs/proxyclipjob.cpp https://invent.kde.org/kde/kdenlive/commit/e083567cc30cf5af56ea441651b2322d63eb63f8
Wow thanks that s was quick! Is there a build somewhere to try the commit? I don't have any experience to build it myself but I can try if there is not! Cheers!
Yes we have a daily AppImage build for the master branch that can be used to check if bugs have been fixed. Wait gor todays build (around 13h30 CET) and get it here: https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ Just download the file, make it executable and run it. Feedback welcome
just tested on a png sequence, seems to work perfectly Thanks a lot for the quick fix in these holidays ! Merry christmas guys, and thanks for your work on kdenlive !
Thank you for the feedback and contribution. 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.