Remarks

Timeline Mixer aims to be compatible with as many third-party Timeline tracks as possible. Most custom tracks should work without modification, however some may require changes or may not behave as expected.

Potential compatibility issues may include:

Tracks that rely on direct access to a Playable Director during runtime.
Custom components or behaviours that query the Playable Director to set playback state or time.

Playable Director vs Timeline Mixer Workflow

Under a standard Timeline workflow, a Timeline Asset is assigned to a Playable Director. At runtime, the Director builds and evaluates a Playable Graph based on the assigned Timeline Asset.

This approach works well for playing a single Timeline, but a Playable Director can only actively play one Timeline Asset at a time.

Timeline Mixer uses a different architecture.

Rather than using one or more Playable Directors to drive playback, Timeline Mixer uses a single Playable Director primarily as a container for track bindings and exposed references.
Timeline Mixer then builds and manages its own Playable Graph containing all assigned Timeline Assets.
The Playable Directors PlayableAsset field is left empty during runtime playback.

This allows multiple Timeline Assets to be evaluated simultaneously and enables blending between tracks that target the same objects or components.

Important: Because Timeline Mixer does not use the Playable Director for runtime playback, third-party tracks that directly query or control a Playable Director may not function correctly without modification.

Remarks: Not sure whether a third-party track will work? Most custom Timeline tracks are compatible. If you encounter an issue, feel free to get in touch - I'm happy to investigate compatibility and provide guidance where possible.