Problems photoshows - "Fading In" in combination with "panorama effect"

hi,

first of all !!! GREAT JOB !!! i was searching for a long time and finally found kdenlive as video editor.
I ubdated my (k)ubuntu from hardy to jaunty just for one reason kdenlive ... i will never regret.

Yesterday i wanted to make a photoshow with embedded panorama-panning and some little video and had some crashes and some problems with the rendered result. See my solution below, it is a little bit complicated - sorry. Two problems occured:
1) My Solution works in the preview, but the rendered result is jumping arround at the end of the panning (only video is jumping ...).
2) While adding the panorama picture kdenlive crashed two or three times. It is a big jpg (~25MB) ...

May be someone can help?

My system: Quadcore, 4GB, Jaunty 64bit, KDE4, kdenlive 0.73 (intstalled from the basis-repositories)

Questions are:
* Should i update to 0.74 and if so, how can i do this?
* Should i resize my photos before i use them within kdenlive (with mogrify or so) ...
* I can not reproduce the crashes, should i add a bug anyway?

* I can add screenshots or the project itself if necessary.

By the way kdenlive, works fine with panasonic sdr-s7 !!!

Thanks a lot!
hasp

MY SOLUTION:

A) What do i want? - The timeline should look like
picture in picture intro video with title (crossfade) photo (crossfade) photo ...
(crossfade) photo (crossfade) panorama left side (panning) panorama right side (crossfade) panaorma as a whole (crossfade) photo (crossfade) ...

B) My Solution:
01) title with picture in picture intro video like in the video tutorial
02) photoshow with all photos (incl. crossfading) assume that we have the following sequence in our photoshow: 'photo0' 'photo1' 'panorama' 'photo2'

03) cut photoshow shortly before showing the panorama as a whole means we cut _out_ the crossfade between 'photo1' and 'panorama'
04) add 'photo1' as picture at the end of the photoshow ('photoshow' 'photo1' without any transition)
05) add the panorama picture three times at a different video-track ('panorama' 'panorama' 'panorama')

reason for step 5: 1.panorama fadein 2.panorama pan 3.panorama fadeout

06) adjust the length of the first panorama to the length of 'photo1' we will need this for the crossover
07) add contribute, change size like described in video tutorial "video-panorama" and align it to the left (startpicture of the panning)
08) change within the contribute dialog visibility (?) to 0 at the beginning and to 100 at the end

result until here: 'photoshow' (invisible cut) 'photo1' (crossfade) panorama left side

09) change length of second panorama (paning time)
10) add contribute, change size like described in video tutorial "video-panorama"
11) add keyframe at the end align it to the right

result until here: 'photoshow' (invisible cut) 'photo1' (crossfade) panorama left side (invisble cut) panorama left side (panning) panorama right side

12) add 'panorama' to a new video track -> will be used for the crossfade, change length to 2 sec (or so)
13) change length of the third panorama (added in step 5) to the length of 'panorama' from step 12 (2 sec or so)
14) add contribute to step 13, change size like described in video tutorial "video-panorama", align it to the right (the end picture of the panning)
15) change within the contribute dialog visibility (?) to 100 at the beginning and to 0 at the end

result until here:
'photoshow' (invisible cut) 'photo1' (crossfade) panorama left side (invisble cut) ...
panorama left side (panning) panorama right side (crossfade) panorama as a whole

16) add photoshow with cutted out crossfade before 'panorama' (see 02) at the end of step 12

result:
'photoshow' (invisible cut) 'photo1' (crossfade) panorama left side (invisble cut) ...
panorama left side (panning) panorama right side (crossfade) panorama as a whole (invisible cut) panorama as a whole (crossfade) 'photo2'

Yes, you should upgrade to 0.7.4. Kdenlive 0.7.4 is using MLT 0.4.2 video engine which is much more stable. Sorry for the inconvenience. Kdenlive is under heavy development, so every upgrade is likely to fix between 20 and 50 bugs.