Hello,

every time I render a project with 2 pass rendering the render generates an error.

I got this with those render:
Vimeo 640x480 2 pass
DVD PAL 16:9 VOB 2 pass
XVid4 10000k 2 pass

Kdenlive version 0.7.6.
Is it specific to my computer?
Version 0.7.5 could render 2 pass.

Thanks for help

Well... the render DVD PAL 16:9 VOB 2 pass works.
My mistake.
The two other render mentioned did not worked.
I did not tested other render profiles.

Both of those worked fine for me here. How did you get Kdenlive - builder wizard, manual, or packages?

Can you please test a clip/movie-duration between 30 and 60 seconds and see if it still crashes?

I use the Ubuntu package 0.7.6 on a Xubuntu 9.04.
Usually I save all my projects and clips on a NAS (Network attached storage). I access it through WiFi. It was not a problem with the version 0.7.5

Today I copied the rendered DVD version on my local drive, added as single clip in a new project and rendered it as vimeo 640x... 2 pass successfully.
I will try the same with the DVD version located on the NAS.
I think the WiFi connection causes the problem, but I have to test it further to be sure.
Duration of the rendered video: 2 min 08 s

Today I could render the (same) project into Vimeo 2 pass.
The whole project was located on the NAS as before. So could it be that it is depending on the quality of the WiFi connection?

It seems it works sometimes, and sometimes not (I am quite sure the DVD rendering crashed at least once).
If it is so, the longer the project is, the more chances to get errors.

I never noticed that before the version 0.7.5, but it could be I was lucky.

I have some more test results. I cannot get 2 pass render successes.
Before that I want to say that I am very sorry for the bad, hysterical and incomplete info I give about my problem. I am quite disoriented because it seems that sometimes it works, sometime not.

So I finally tested a project saved on my local drive. And the pass 2 does not works.
The project duration is 29 sec and 4 frames (is it long enough for you, ddennedy?).
As source I use 2 kind of originals .MTS from canon and their conversion in .avi (DVD PAL).
I created one project with the DVD sources and after that I edited a copy and changed all .avi in .MTS.

Both projects reacts equally.
Render to DVD PAL, 1 or 2 passes are working.
Render to Vimeo 1 pass is working.
When I render to Vimeo 2 passes doesn't works.
All my files are saved on my local drive.

Curiously, when I use a rendered DVD PAL project as source and render it in Vimeo 2 passes is working (640x480)!

When rendering with two passes the first pass works, the x264_2pass.log.temp is created, and the second pass is started. In Knotify I can see the progress bar growing but the rendered file does not grows: it stay at 48 bytes.

At the end of the rendering (the progress bar is at 100%) an error message appears.

At the moment I use a 3rd party package (Ubuntu), version 0.7.6.
My OS is Xubuntu 9.04.

The problem was not apparent with the temporary package of sunab (deb http://ppa.launchpad.net/sunab/sunab2/ubuntu jaunty main), version 0.7.5. with two build version before the update to 0.7.6. I don't know the build number.
I think it was a build not younger than the 25st September.
When I render my CPU usage goes to 97% with melt using 70 to 85% (the second task is xorg with 4 to 7%).

Summary: the WiFi connection to a NAS is not the cause, a one-clip-project can render with 2 passes, DVD 2 passes rendering is always working and an multiple-clip-project can nor render with 2 passes.

I'm looking forward to getting suggestions to test / diagnose my problem.
Thank you for reading ;)

I am confused...
Same project, same conditions, a render in Vimeo 2 passes from the .MTS project. This time it worked. Maybe because it is the second try?
Unfortunately is it very long to test, about one hour.
I'll try on a very short project and give feedback as soon as I have results.

Please keep the discussion in the bug:
http://www.kdenlive.org/mantis/view.php?id=1197

done.
In the future I'll only consider posting on the bug report regarding this problem.