Proxy files are okay to a certain degree, specially early on on the editing process when bulk editing is done, but they get useless very soon after a more refine editing needs to be done
Low quality doesnt allow you to see many details that needs to be seen in order to edit the small stuff... and even when they do, the proxy slows down too after 1 or 2 effects are applied, even if less Maybe im missing something and i dont know how to use proxy well, but I have a very new beefy computer and the clip gets choppy very often, even with proxy files Also, switching proxy on and off, invalidates the whole preview... which makes not wanting to active proxy to begin with My solution has been to run preview for the whole clip, even if slow, its done in the background while editing and while im having my lunch :) Right now the spacer tool doesnt invalidate the preview as per bug https://bugs.kde.org/show_bug.cgi?id=367079 But even if you manually invalidate it, its very slow https://bugs.kde.org/show_bug.cgi?id=384593 MY WORKAROUND is to watch the whole preview and take notes of the editing that needs to be done. Then, start working on those points FROM THE END TO THE BEGINING. This way, the spacer tool and moving things around, wont invalidate previews clips If you start from begning to end, every little edit that involves spacing or insert, will invalidate the whole thing Id like comments on this idea, and hows your own workflow in kdenlive, because im new to video editing in general and kdenlive in particual, and maybe im doing something wrong Thanks for reading! PS: Also, is it possible to use several threads for preview? I have a modern i7 with 8 cores and only 1 seems to be working. Since 1 second chunks are procesed, this seems an easy target for parallelization, unless last frame preview is needed for the next and I dont know about it. Not sure if I should open a bug about this or if this new timeline that is being worked on right now will fix all these problems. A developer comment would be welcomed :)