Reference

Supported Files and Privacy

OrcheStruct is Cubase-first for write-back. Other DAW support should be treated as inspection/planning unless a release note says otherwise.

P1Updated June 20, 2026OrcheStruct v1 launch beta, Cubase-first workflow

OrcheStruct Settings integrations surface with privacy-focused connection cards and warnings. — Launch docs should keep privacy language explicit: integrations and support flows need to say what stays local and what should not be sent by default.

Launch File Support

For v1 launch docs, treat Cubase XML as the clearest path for scanning and write-back. Logic and Pro Tools are part of the broader architecture, but user-facing write-back promises should stay conservative until those flows are verified.

Cubase XML / track archive workflows: primary launch path.
Cubase live bridge: primary launch live-control path.
Logic and Pro Tools: inspect/planning language only unless verified for the specific build.

Privacy Posture

Composers should know what they are sharing. Do not send private project files, license keys, unreleased cue data, or client material in support requests unless a specific diagnostic item is requested.