Kdenlive 25 Not Using LRV Proxy Files As Documented

Hello. I’ve read a few Kdenlive docs which state how to enable proxy clips as well as how to enable using external proxy clips which are pre-generated by cameras (such as Insta 360 Ace Pro). I configured my Kdenlive (v 25), in both project and global settings, to use external proxy clips, selecting “Insta360 AcePro lrv”. I then used the lrv file in my timeline (for better performance), and when I rendered the project the rendered mp4 quality seemed not that great, so I replaced the lrv file in the timeline with the full quality mp4 file that camera recorded. When I rendered the project using the fully quality mp4 file, the rendered mp4 seemed to be of a higher quality than the mp4 that was rendered using the lrv in the timeline. When I compared the bitrate of the two rendered mp4 files, the one rendered using the full quality mp4 in the timeline had a much high bit rate. Seems like Kdenlive is not automatically using the higher quality mp4 file when rendering, as I’ve seen documented. Anyone know how I can get Kdenlive to use the lrv files in the timeline but use the high quality mp4 files when rendering?

That’s not how it works - if you import and work with the low-res files directly, then they are just ordinary clips (which could themselves then have proxies).

You need to work with the source clips you want to use for rendering, and enable the Proxy Clip option in the bin menu. That will either then generate a proxy or use the external one if configured for that and one is found.

1 Like

Thanks. Yep, that worked. I hadn’t seen the doc section you linked to. Google’s AI and search results were very mis-leading/informing. I noticed that when I right-clicked on the higher-res/mp4 file in the bin, and then selected Proxy Clip, Kdenlive did not show a progress meter as if it were generating a proxy clip (because it knew to use the lrv file), and now the performance has greatly improved. Hopefully this thread bubbles up to the top in Google’s AI - thanks again.