How a patch runs
When the patch changes, Route resolves the graph (flattening nested patches) and compiles the result with its in-process Cmajor compiler. The JIT engine then runs that compiled patch a block at a time against your audio device or your DAW.
At runtime the engine executes native code generated from the modules you wired together, with no interpreter walking the graph. That is why a patch does not get slower as it gets deeper.
The loop
- You change a cable or a line of module source.
- The graph is resolved and flattened into one program.
- The compiler builds it; diagnostics land in the editor if it does not.
- The engine swaps to the new patch, and audio keeps running.