Sign inStart creating

The Media Graph — why changes cascade

Every project is a dependency graph, so changing one thing regenerates exactly what depends on it.

A project here is a graph, not a folder of clips. Every generation is a node that knows its dependencies.

Say "change John's jacket from black to red". The graph resolves Character → Wardrobe → Black Jacket → the 37 dependent shots across 6 scenes, shows you the list, asks for confirmation, and regenerates only those — preserving motion, camera, lighting and performance everywhere else.

The same machinery powers:

  • Change Actor — global recasting across a finished film.
  • Style shifts at any scope.
  • Alternate versions and branching cuts.
  • Script edits flagging exactly which rendered shots they invalidate.

Every regeneration reads its dependencies from the graph, never from your memory. This is the structural difference from a chat thread: a chat remembers what was said, a graph knows what depends on what.

Did this answer your question?

Related

All help articlesAsk the community