Bug 496051

SUMMARY

The GUI for rendering a project has multiple incongruities that could lead to mistakenly overwriting a previously rendered file or rendering a file in a different location than expected (which can have performance impacts if paths are on different devices). This is especially true for projects that have multiple sequences.

STEPS TO REPRODUCE
1. Create a project with two sequences (with a color clip in each).
2.  Save it under /tmp/project/test.kdenlive.
2. Open the Render project dialog.
3. Render the first sequence under /tmp/render/s1.mp4
4. Save the project.
5. Activate the second sequence.
6. Open the Render project dialog again.
7. Render the second sequence under /tmp/render/s2.mp4
8. Save the project (or not)
9. Activate the first sequence.
10. Open Render project dialog.

OBSERVED RESULT

At point 2 (and others) :
The GUI offers to render either the whole project or the selected zone. Whole project actually means the active sequence, but it is not visible which sequence it is (one has to switch back to the main window to see).

At point 10 :
The render path which is prefilled in the GUI is /tmp/project/s2.mp4.

EXPECTED RESULT

At point 2 (and others) :

Whole project should be "Whole sequence" and there should be a dropdown to choose which sequence. The active sequence in the main window should be preselected in that dropdown.

At point 10 :
The path should be /tmp/render/s1.mp4, since that was where Sequence 1 was last rendered.

SOFTWARE/OS VERSIONS

The path and filename prefilled in the GUI for rendering Sequence 1 should be the same as the one that was input on first rendering.

ADDITIONAL INFORMATION

Note the path /tmp/project/s2.mp4 was never used to render a file. The GUI takes the basename of the last render (irrespective of which sequence was rendered) and the dirname of the project file.

Also note that the whole rendering path is written to the project file under property kdenlive:docproperties.renderurl, and that if the project is closed and then opened again, the Render GUI prefills this whole path, as expected. However, changing the active sequence makes the GUI subsequently discard this path in favour of the abovementionned construction.

So it seems there is some code aimed at updating the prefilled render path with respect to what sequence is to be rendered, but it is wrong.