
Kdenlive needs to recognize the relationship between the camera original and its smaller companion file. An LRV or LRF file sitting somewhere on the drive is not enough. Check the selected camera profile, the names of both files and their relative folders before generating another proxy.
Key Takeaways
- Camera proxies are matched through a naming and folder profile.
- Enable external proxies in the relevant project.
- Keep the original recordings available for final rendering.
Start with a matched recording pair
Choose one short recording for diagnosis. Make a working copy of its original and camera proxy while retaining their relative layout. Record both full filenames, including prefixes, suffixes and extension case. Do not rename the only copy of camera media to make a profile appear to fit.
The Kdenlive 26.08 camera-proxy documentation describes profiles that map these relationships. Its listed schemes include GoPro LRV, DJI LRF and particular Insta360 variants. That list describes filename conventions; it does not establish that every recording mode from every camera model is supported.
Configure recognition before importing the test
In Project Settings, enable proxies, enable external proxy clips and select the matching camera profile. Then add the test recording. The manual documents this import workflow for using the companion already recorded by the camera.
If the profile expects a proxy beside the original but your ingest tool moved all proxies into an unrelated folder, preserve the original card structure in a separate working copy and try again. If it expects a distinct filename prefix, compare the actual prefix rather than treating the file extension as the entire rule.
For a proposed travel-film example, the original might arrive from one card folder while a file manager collected small previews into another. A correct camera name in the menu cannot repair that changed relationship. Resolving the layout is a different task from reducing the proxy generation resolution.
If the scheme does not match
The manual documents custom external-proxy mappings. Build one only when you can describe the relationship consistently across more than one recording. A one-file rename can conceal a rule that fails on the next card.
Alternatively, keep the camera originals and let Kdenlive generate editing proxies. Do not overwrite original recordings with the camera's small files. A KDE discussion about LRV recognition illustrates this user question on an older version; it is not proof of a current universal defect.
Accept recognition and delivery separately
Check that the selected test clip uses the intended companion and that another recording follows the same rule. Then make a short final render with originals online. The project proxy documentation distinguishes editing proxies from the original media used for full-resolution rendering. Successful companion recognition should save editing work without replacing the delivery source.
Related tasks
- Shotcut proxies in an open project: separate generation from reload
- The final film contains a proxy watermark: confirm which media the export uses
- When Archiving a Kdenlive Project, Should You Include Unused AI Takes and Source Images?
Sources and scope
- Kdenlive 26.08 Using Camera Proxy Clips: External proxies: camera profile and path/filename mappings; Camera profile maps original and proxy names/paths.
- Kdenlive 26.08 Project Proxy Settings: Global versus project proxy settings; thresholds; original rendering; profile tests; Camera profile maps original and proxy names/paths.
Official primary documentation opened and read. Individual proposed examples and diagnostic reasoning; no hands-on testing or benchmark claimed. No AI citation frequency measured.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Paparazzi Ratzfatzzi / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.