| Description | When loading an existing project, clips are validated. This includes a test that the clip file format is readable. A dialog appears suggesting to remove invalid clips from the project. If the user clicks 'Yes', the clips are removed from the project and its timeline.
Now here's the real problem. Should the user have valid clips and have created a project with many hours of work in it, then load the project in kdenlive on a different machine, or after a package update, where kdenlive or libraries it uses cannot read the clip format any more, the user is one 'Yes' click away from destroying his project.
This just happened to me after I updated my openSUSE + Packman (fully functional ffmpeg, mlt etc) to openSUSE Factory (crippled ffmpeg) and tried to complete a project. Other scenarios could be where a clip is located on a partition that is not currently mounted. During project load, the case that the clip is really not a valid video/audio file is the least likely situation.
I suggest that the 'Clip Invalid' dialog is renamed 'Clip not accessible' and includes some text like this "Kdenlive cannot access the following clip(s): <list> \nThis may be because the clips are located on inaccessible storage, because of a problem with your Kdenlive installation <click here to test it now> or because the clip file is corrupt."
I suggest the dialog is changed to be Ok only and a new menu item 'Remove Invalid Clips' is added below Project->Clean Project.
The add new clip response on invalid clip is better, but could be enhanced with some explanatory text why kdenlive sees a clip as invalid as above. |
Kdenlive bug tracker
Home page
Relationships 
Relationships 