Re: kdenlive render pipeline (was Re: smart encoding)

2017-09-29 Thread Mikko Rapeli
On Fri, Sep 29, 2017 at 09:34:14AM +0200, Evert Vorster wrote: > Hi there. > > There was a little trick that I was doing on a virtual machine some time > ago, where I would set the project resolution to the proxy resolution, and > my proxy resolution was exactly the display window resolution, so I

Re: kdenlive render pipeline (was Re: smart encoding)

2017-09-29 Thread alberto fuentes
On Fri, Sep 29, 2017 at 9:34 AM, Evert Vorster wrote: > In short, I agree, there is a lot of speed gain to be had here, which would > open up or improve the experience of video editing for a lot more people on > older/slower hardware. And in modern hardware I dont know if im doing something wron

Re: kdenlive render pipeline (was Re: smart encoding)

2017-09-29 Thread Evert Vorster
Hi there. There was a little trick that I was doing on a virtual machine some time ago, where I would set the project resolution to the proxy resolution, and my proxy resolution was exactly the display window resolution, so I was avoiding any scaling whatsoever. Editing was indeed very, very fast,

Re: kdenlive render pipeline (was Re: smart encoding)

2017-09-28 Thread alcinos
Hi, So I think you guys are talking about different things. Harald talks about prerendering, where you basically precompute all the frames for a portion of the timeline to play it faster. That should of course remain as it is, because the intent of this is to see how the final clip would look like.

Re: kdenlive render pipeline (was Re: smart encoding)

2017-09-28 Thread harald.albrecht
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 pipelin