Kdenlive-Blender Integrated Pipeline

Hypothesis

Can Kdenlive and Blender be combined into a unified video production pipeline, potentially with CRDT-based real-time collaboration?

Approach

  1. Analyzed MLT XML bridge between tools
  2. Evaluated complementary strengths
  3. Designed proxy and overlay workflow
  4. Explored CRDT integration for multiplayer editing

Findings

Key Observations

Complementary Strengths:

ToolStrengthUse Case
KdenliveTimeline editing, audio syncSequencing, cuts, transitions
Blender3D, VFX, compositingMotion graphics, effects

MLT XML Bridge:

Both tools can interoperate via standardized formats:

  • Kdenlive exports .kdenlive (MLT XML)
  • Blender exports OpenEXR sequences
  • MLT can process both via melt CLI

Unified Workflow:

1. Blender: Generate 3D assets/effects
   → Export: OpenEXR image sequence

2. Kdenlive: Import sequences
   → Edit: Timeline assembly, audio sync

3. Export: Final render via MLT

Proxy & Overlay Workflow:

  1. Create high-res Blender renders
  2. Generate proxy versions for editing
  3. Composite overlays in Kdenlive
  4. Final export uses original renders

CRDT Integration for Collaboration:

Potential for real-time collaborative editing using CRDTs:

FrameworkUse Case
YjsWeb-based collaboration layer
AutomergeLocal-first desktop sync

CRDT Benefits for Video:

  • Decentralized project files
  • Offline editing with sync
  • Conflict-free timeline merging
  • Non-linear versioning

Implementation Considerations:

  • Track-level conflict resolution (not clip-level)
  • Tombstones for deleted elements
  • “Last Writer Wins” for simultaneous edits
  • UX for “silent merge” notifications

Outcome

Status: Success

Pipeline integration is highly viable. CRDT collaboration is promising but requires further research.

Next Steps

  • Document standard Blender→Kdenlive workflow
  • Create template project with placeholder sequences
  • Prototype CRDT sync for timeline metadata
  • Test multiplayer editing scenario