https://bugs.kde.org/show_bug.cgi?id=486502
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from [email protected] --- disclaimer: i have no idea what's going on and claude wrote this. I can reproduce this with DJI footage (HEVC/H.265, 10-bit) on Kdenlive 26.04.1 Flatpak (Linux Mint, `org.kde.Platform/x86_64/6.10`) and have identified the root cause. The source file contains DJI proprietary data streams alongside the main video and audio: - Stream 2: `djmd` (DJI metadata) - Stream 3: `dbgi` (DJI debug data) - Stream 4: `tmcd` (timecode) - Stream 5: MJPEG thumbnail (attached picture) Kdenlive's proxy generation hardcodes `-sn -dn -map 0 -ignore_unknown` into the FFmpeg command. The problem is that `-map 0` is an *explicit* stream selector and overrides `-sn -dn`, so all DJI data streams get passed to the muxer regardless. Recent versions of the bundled FFmpeg/MLT are stricter about codec tags in MOV/MP4 containers and reject this combination, producing: ```[mov @ ...] Could not find tag for codec h264 in stream #2, codec not currently supported in container``` The fix should be to replace `-map 0` with `-map 0:V -map 0:a` in `proxytask.cpp`, which explicitly selects only video and audio streams while genuinely excluding subtitles, data tracks, and attached pictures. -- You are receiving this mail because: You are watching all bug changes.
