Hi,

I have a project based on ca. 20 clips (canon powershot s95, and some transcoded clips from an android mobile phone).
I created it 6 weeks ago and at this time everything was fine including rendering. Yesterday I tried to
render it again (which worked) but the movie itself shows some "INVALID" sequences.

Further investigations show that now some of the clips in the timeline are "INVALID". The invalid clips are
part of some *.mov-clips from my canon powershot s95.

First I thought that there is a problem with the format of the *.mov-clips. But this isn't the case because
when I add one of the "INVALID" clips again at the end of the timeline of the project with the same
cutting/render/effects/transitions it produces a valid result whereas the original clip at the original
timeline position still shows "INVALID"


gentoo linux, amd64
Kdenlive 0.8.2.1
mlt 0.7.6
ffmpeg 0.10

Hi,
Can you please upload your project file with one of the invalid clips added at the end of the timeline again?

Are the paths to the INVALID files the same? Remember Linux is case sensitive so are they *.mov or *.MOV for example. If you were using proxies previously, try building / rebuilding a proxy for the INVALID clip does it create one?

If you check the properties of the INVALID clips in the Clip Monitor does everything look ok?

- everything is linux, no proxies.
- for me as newbie the properties look fine.


so, here it is.

apart from other clips the very first clip in the timeline shows this invalid bahaviour (20120101_js_6514.mov). I re-added it again at the end and there it is correct. Moving the clips doesn't change the behaviour. the original one is invalid and the newly added is correctly displayed.

home/boss/PICS/20120101_champenvan_raw1/vid_pow/20120101_js_6514.mov

&

home/boss/PICS/20120101_champenvan/vid/20120101_js_6514.mov


There appears to be two different paths to the same source file, are both paths VALID?

^ only the first one is valid!

thanx for the hint - a manual replace of the old/obsolete path in the xml file solved my problem.

but the question is why were these old pathnames in the project file.
I think there must be a problem with (semi)automatic clip path detection because most of them are correct and only a few had still the old path.

Looks like the invalid path only occurs on clips that have a speed effect. There might be an issue in Kdenlive when trying to find missing clips with speed effect. I will check that...