Keep the editorial structure
The native adapter supports flat video and audio tracks, clips, gaps, source ranges, and supported retiming in imported OTIO timelines.
Alchemist Connect
Let the cut travel. Keep its meaning.
A direction for more connected editorial workflows, grounded in the native editor's OTIO interchange. Move a supported timeline today, then follow the roadmap toward shared project history and reconnectable editing.
Interchange foundation exists · Connected sync plannedCurrent native foundation
Carry the cut.
- 01Editorial timelineTracks, clips, source ranges
- 02OTIO / OTIOZA portable timeline snapshot
- 03Alchemist ProValidate, relink, keep editing
The native editor imports and exports supported OTIO structures, with OTIOZ import for bundled media. A snapshot moves an edit at a point in time; effects support depends on the source application.
- Timeline handoff
- OpenTimelineIOSupported tracks, clips, ranges, gaps, and timing.
- Bundled media
- OTIOZ importOpen a timeline archive with its included media.
- Future connection
- Shared historyLocal edits and server reconciliation are planned.
01 — The interchange foundation
Carry an edit, not just a movie.
The current native editor can exchange supported timeline structure. Media references, timecode, and editable clip relationships travel with the cut.
Respect source and record time
Source timecode origins and timeline timing are mapped deliberately, including media whose frame rate differs from the sequence.
Bring the media with the handoff
OTIOZ import extracts bundled media and resolves supported references. Missing or ambiguous sources stay visible for explicit relinking.
Preserve supported audio intent
Selected pan, gain, fade, and audio-transition data can be mapped into the native timeline. Support depends on the exported representation.
Round-trip native project detail
Native-authored OTIO exports can include Alchemist document metadata, which the native importer prefers when it is present.
Make compatibility visible
Unsupported timing structures are rejected before replacing the sequence. Playback-only compatibility does not promise identical effect rendering.
02 — Compatibility, clearly stated
A handoff has a contract.
Interchange support belongs to the native editor today. Connect's future synchronization is a separate step; importing a timeline does not establish a live link to its source application.
| Workflow | Stage | What to expect |
|---|---|---|
| Native OTIO round-trip | Existing foundation | Supported native exports can retain Alchemist document metadata. |
| Flat foreign timelines | Existing foundation | Structural import of supported clips, tracks, gaps, timing, and selected audio data. |
| OTIOZ archives | Existing foundation | Import bundled media; unresolved references remain offline for relinking. |
| Resolve effect parity | Partial / deferred | Selected records are supported or playback-only. Full rendering parity is not promised. |
| Connected project history | Planned | Local committed edits reconciled with a server-ordered project history. |
| Live Premiere / Resolve links | Not implemented | The native plans do not define a shipping live synchronization adapter for other editors. |
Nested compositions, unsupported transitions, and unknown timing effects remain outside the supported structural import contract.
03 — Beyond the snapshot
Keep working. Reconnect with context.
The planned project model records meaningful edits locally, then reconciles them with a shared history. That is the foundation for connected editing across Alchemist.
Local work stays local
The plan keeps committed edits in a local project history. A network connection is not the prerequisite for making an edit.
A common order for changes
A shared service will order project changes so each client can reconstruct a consistent timeline from the same history.
Surface conflicts for a decision
On reconnect, local changes are reconciled with the server's history. Displaced or incompatible edits are intended to be surfaced rather than silently lost.
Connected editing depends on shared media identity and the Server project service. It is planned work, separate from the existing live review session transport.
04 — The connection roadmap
From portable cuts to shared projects.
Each stage builds on a concrete capability. The roadmap makes room for collaboration without claiming every editor speaks the same effects language.
- 01Foundation
Timeline interchange
Use the native editor's OTIO export and OTIO / OTIOZ import to move supported cuts and media references.
- 02Planned
A durable edit history
Record committed project changes, recover them through replay, and preserve meaningful undo behavior.
- 03Planned
Shared media identity
Recognize the same media bytes across machines, with background verification and remote proxy workflows.
- 04Later
Connected project editing
Connect local history to the shared service, reconcile changes on reconnect, and make conflicts visible to the editor.
Across the suite
Keep the next step close.
Move from a portable timeline to the editor and service model that suit your work.
Keep your options open.
Follow the development of connected workflows, from reliable interchange to a shared project history.
Connect synchronization is planned. Native interchange is the existing foundation.