FX routing and persistence

Yrendr persists plugin effect instances in Track or Master chains. The current project model does not use clip-level plugin chains.

Routing order

Visual processing:

clip rendering -> Track FX -> compositing -> Master FX -> Preview/Render

Audio processing:

clip audio -> Track FX -> timeline mix -> Master FX -> playback/render

Persisted effect instance

A project effect instance stores a stable identifier, enabled state and parameter dictionary. The registered effect is resolved through its full ID:

<plugin_id>:<effect_id>

Design for persistence

1. Keep plugin and effect IDs stable.
2. Keep parameter keys stable when possible.
3. Use JSON-compatible parameter values.
4. Handle missing or older parameter keys defensively in the processor.
5. Avoid storing required state only in custom UI objects.

Note: Yrendr preserves unknown/unresolved effect instances in project data. Reinstalling the same stable effect ID can restore the chain.

Caution: Changing a stable effect ID is a compatibility break for projects that already reference it unless you provide an explicit migration path.