https://bugs.kde.org/show_bug.cgi?id=517300
Bug ID: 517300
Summary: DJI LRF external proxy tries to generate a .LRF cache
proxy instead of attaching the existing sidecar file
Classification: Applications
Product: kdenlive
Version First 25.12.3
Reported In:
Platform: Flatpak
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Project Bin & Import
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 190492
--> https://bugs.kde.org/attachment.cgi?id=190492&action=edit
stacktrace
Kdenlive does not correctly attach existing DJI .LRF sidecar files as external
proxy clips.
Environment:
- Kdenlive: 25.12.2 (Flatpak)
- Runtime: org.kde.Platform 6.9
- OS: Ubuntu 25.10
- Session: KDE Wayland
Problem:
When "Camcorder proxy clips" is set to the built-in "DJI LRF" profile, Kdenlive
does not mark the imported .MP4 clip as a proxy clip, even though the matching
.LRF file is present in the same directory.
If I manually try to enable/create proxy clips, Kdenlive fails with:
"Failed to create proxy clip"
Expected behavior:
Kdenlive should attach the existing .LRF file as an external proxy clip and
mark the clip as a proxy clip, without trying to generate a new .LRF proxy in
cache.
Actual behavior:
Kdenlive opens both the source .MP4 and the existing .LRF, but then tries to
create a cached proxy file with a .LRF extension in the Kdenlive cache
directory. ffmpeg fails because it cannot choose an output format for a .LRF
target.
Relevant strace excerpt:
access("/home/boyan/.var/app/org.kde.kdenlive/cache/kdenlive/proxy/bd1345d0691fda0edd3886385294a448.LRF",
F_OK) = -1 ENOENT
openat(AT_FDCWD,
"/home/boyan/Videos/DJI/08.03.2026/DJI_20260308101400_0002_D.LRF", O_RDONLY) =
3
openat(AT_FDCWD,
"/home/boyan/Videos/DJI/08.03.2026/DJI_20260308101400_0002_D.MP4", O_RDONLY) =
4
ffmpeg then reports:
"Unable to choose an output format for ... .LRF"
"Error initializing the muxer ... Invalid argument"
Steps to reproduce:
1. Enable proxy clips
2. Enable "Camcorder proxy clips"
3. Select the built-in "DJI LRF" profile
4. Put these files in the same directory:
DJI_20260308101400_0002_D.MP4
DJI_20260308101400_0002_D.LRF
DJI_20260308101400_0002_D.SRT
5. Create a new project
6. Import the .MP4 file
7. Observe that the clip is not marked as a proxy clip
8. Try to enable/create proxy clips manually
Input file details:
- MP4: HEVC Main10, 3840x2160, 59.94 fps
- LRF: H.264, 1280x720, 59.94 fps
Important note:
A local workaround proves that the .LRF file itself is readable and usable as a
proxy source. If I remap the external proxy profile so Kdenlive sees the same
LRF content through a hidden ".proxy" directory with a ".MP4" filename,
Kdenlive correctly marks the clip as a proxy clip.
This strongly suggests the issue is specific to Kdenlive handling the .LRF
suffix as a generated proxy target instead of a read-only external proxy
source.
--
You are receiving this mail because:
You are watching all bug changes.
