BTW, most new kdenlive downlaods include ffmpeg, etc. Then check the fields next to the list of program names such as "FFmpeg." If that file path text box is empty, your install of kdenlive can't see your install of ffmpeg. Then go to "Enviornment" and "MLT Environment". Protip: Use the keyboard shortcut Ctrl + Shift + comma to *instantly* get to Settings/Configure Kdenlive. This is where it turned up on my Windows computer Only difference is the path to my kdenlive exeuctable folder.
Just to confirm, I was also able to fix this on Win10 by using the method described above. Let us know if you need help doing that.) If they're empty, you can try selecting the file locations manually. I don't have a Windows box at home to test that. We can try and confirm that by having you go to Settings -> Configure Kdenlive and going to the Environment section, and telling us what you see in the text boxes under "MLT environment." (I don't remember if the boxes were pre-filled with the FFmpeg/FFplay/FFprobe locations, or if they were empty and Kdenlive defaults to using executables in the same directory it's located in. So, like I said, I suspect this isn't an FFmpeg setup problem but actually an unrelated bug. Furthermore, after I had added a clip using the button, dragging from Windows Explorer seemed to start working. I found that if I clicked the "Add Clip" button in the Project Bin, I could successfully add media to the project. When I had that problem, I was trying to drag files from Windows Explorer into Kdenlive. I recently tried Kdenlive on a Windows computer at work, and I experienced the same issue you're having with the "clip is invalid" error. Like you quoted in your post, the latest version of Kdenlive for Windows shouldn't require a separate FFmpeg installation. I responded to your post on our Meetup forums ( ), but I wanted to respond here for the general KDE/Kdenlive community as well.
0 kommentar(er)
