This page carries the newest Media Room render-capability routing idea into the suite. It derives what the current project needs, compares candidate renderer profiles, and refuses to call a candidate “active” until a real execution runtime proves it.
Capability coverage is planning evidence only. Candidate completeness does not activate a renderer or prove execution. Creator Style DNA is requirement evidence, not proof that a renderer preserved it.
The planning profile combines DV-native visual compositing with FFmpeg master/mux/probe coverage. It remains a candidate until an exact runtime is activated and execution evidence exists.
Strong conventional timeline/audio/mastering coverage. It does not yet prove the DV visual-contract, procedural, effect or gesture runtime.
Best fit for DV-native visual behavior, but container/audio/probe capability is intentionally incomplete in the current planning profile.
The latest DV Media planner defines candidate capability surfaces. It deliberately does not prove those workers are active. LoopLab’s existing Render Engine currently masters approved source renders; it is not silently promoted here into a full Media Room compositor.