I get the following error message when I attempt to select an output folder in the rendering step: /srv/multimedia/kdenlive/untitled.mp4 is a file, but a folder was expected. This only happens if the output format is mp4. WebM and MEPG-2 works as expected, i.e. the open file dialog is positioned in /srv/multimedia/kdenlive/ Reproducible: Always Steps to Reproduce: 1. Open kdenlive 2. Add a clip (to the timeline) 3. Click render 4. Select MP4 as format 5. Hit button (next to the lineedit with filename) to select output folder Actual Results: An error box pops up over the open file dialog: /srv/multimedia/kdenlive/untitled.mp4 is a file, but a folder was expected. Expected Results: An open file dialog positioned in /srv/multimedia/kdenlive/
I think that's a bug in KDE Frameworks that was recently fixed. Can you tell me which KDE Frameworks you use ? You can find it in Kdenlive > Help > About Kdenlive > Version
On both my machines back home (openSUSE Tumbleweed): Version 16.08.0 KDE Frameworks 5.25.0 Qt 5.6.1 (built against 5.6.1) I see the reported problem on both machines. (I also rebuilt kdenlive just to see if that had any effect.) I just tested on a machine with KDE Neon. The problem does not show up there, although I did see it a while back. Version 16.08.0 KDE Frameworks 5.25.0 Qt 5.7.0 (built against 5.7.0) I'll test with a new user on my home machines when I get back from work.
Ok, I figured out what actually causes the problem and it happens on KDE Neon too. It happens if untitled.mp4, untitled.webm or untitled.mpg already exists in the output folder and I click the select folder button. Should I close this bug and open another with a better title/description? Or wait until Frameworks 5.26 arrives at my computers to see if it fixes the issue?
Please go ahead and edit the title of this bug report yourself to better reflect the bug. Please retest as soon as you can upgrade to the new KF5 release and then report back. Until that I'm setting this report to state NEEDSINFO/WAITINGFORINFO. Thank you very much for your cooperation!
Tested with Frameworks 5.26 on openSUSE Tumbleweed and KDE Neon. This issue has been fixed.