<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>For my workflow, I'm glad that the render pipeline is as is: because I need to resize the timeline height while working on my project this would otherwise invalidate the whole prerendering data. The downscaling is cheap, while the prerendering is expensive. I fail to see how changing the pipeline would improve the situation except to where low end hardware is used which even cannot scale down in realtime.<div><br></div><div>Best regards,</div><div>Harald<br dir="auto"><div dir="auto"><br></div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Ursprüngliche Nachricht --------</div><div>Von: Mikko Rapeli <mikko.rapeli@iki.fi> </div><div>Datum: 28.09.17 13:53 (GMT+01:00) </div><div>An: kdenlive <kdenlive@kde.org> </div><div>Betreff: kdenlive render pipeline (was Re: smart encoding) </div><div><br></div></div>Related to this, kdenlive render pipeline for time line preview on<br>the monitor GUI component is far from optimal. First the clips are rendered<br>to project profile and then rescaled to fit the monitor screen size.<br>Also with proxy clips.<br><br>IMO better would be to render project previews directly to the<br>current monitor/preview size without passing through current project<br>profile except for frame rate.<br><br>For final rendering, naturally, the project profile should be used.<br><br>https://bugs.kde.org/show_bug.cgi?id=384764<br><br>-Mikkoo<br></body></html>