How kde/kdenlive works
Project type and purpose
• Kdenlive is a native desktop video-editing application (C++/Qt/KDE6)
• It integrates with the MLT video-editing framework, plus frei0r, LADSPA, Python speech/SAM services
File structure
• Top-level “src” folder is subdivided into UI, controllers, core, jobs, render, capture, effects, monitors, timelines, pythoninterfaces
• “renderer” implements a separate render server process
• “deps” and “packaging” handle build and deployment (Flatpak, Snap)
• “tests” and “fuzzer” provide unit and fuzz testing
Main components
A. UI Layer
– Qt Widgets (src/uiresources, src/dialogs, src/widgets)
– QML modules (src/qml, src/monitor/view, src/timeline2/view/qml)
B. Application Core
– Controllers & Models (src/bin, src/project, src/assets, src/effects, src/transitions, src/profile, src/library)
– Job Manager (src/jobs + taskmanager)
– Timeline engine (src/timeline2/model & view)
C. Rendering Subsystem
– Renderserver (src/render/renderserver.cpp), RenderRequest/Job (renderer/)
– MLT connection (src/mltconnection.cpp, src/mltcontroller/)
– External libraries: MLT core, frei0r, LADSPA
D. Capture Subsystem
– MediaCapture (src/capture), v4l, MLT device capture
E. Monitor Subsystem
– Video/Audio scopes (src/monitor + src/scopes), OpenGL/Metal/D3D widgets
F. Python & Online Services
– Python interfaces (src/pythoninterfaces) for Whisper, Vosk, SAM
– Online resource providers (src/onlineresources)
G. Static Data & Configuration
– Build scripts & packaging (CMakeLists.txt, packaging/)
Relationships and data flow
• UI Layer → Core Controllers (user actions trigger controller APIs)
• Core → Job Manager → Render Subsystem (tasks queued, processed)
• Render Subsystem ↔ MLT Library (via mltconnection)
• Core ↔ Assets Repository (loading effect XML, LUTs)
• Timeline Engine ↔ Core (model builds timeline composition)
• Subsystem → Core (incoming video frames)
• Monitor Subsystem ← Core Frames (preview)
• Python Services → Core (speech-to-text, SAM masks)
• Online Providers → Core (download assets)
• File I/O: Core reads/writes .kdenlive project files, proxies, exports
Architectural patterns and principles
• MVC/MVVM: UI (View) ↔ Controller ↔ Model
• Producer/Consumer: Job Manager queues tasks consumed by RenderServer
• Plugin-style repositories: EffectsRepository, TransitionsRepository, AssetRepository load XML definitions at runtime
• Layered separation: UI, core, external systems
Detail level
• Repositories (Effects, Transitions, Profiles) feeding into controllers