Start Here
First Launch Checklist
Start with the app installed, Cubase available, and one known test template or track archive ready. Confirm the app can see its local data before you try live Cubase control.
Before You Start
Use a copy of a template or a known-safe test archive for your first pass. OrcheStruct is designed to preserve the original project while you inspect and export, but the first session should still be low-risk.
- Install the current OrcheStruct build.
- Have Cubase installed if you want live bridge or write-back workflows.
- Prepare one Cubase XML track archive or template export for testing.
- Close unrelated project files so it is clear which Cubase session you are controlling.
Recommended First Run
Do the first run in two passes. First, scan and inspect a file without live Cubase actions. Second, connect Cubase and test Live Session once the app itself is working.
Open OrcheStruct.
Confirm the main navigation loads: Inspector, Tracks, Library, Studio, Cue Builder, and Software.
Open Inspector and scan a small or medium Cubase XML export.
Review track families, folders, routing, and library identity.
Open Tracks, then Live Session only after the bridge setup is complete.
If Something Looks Wrong
Do not keep clicking through errors. Capture the app version, what file you opened, the exact error text, and whether Cubase was open.
Most first-run issues fall into three buckets: missing local data, a scan file that does not match the expected format, or Cubase bridge setup not being finished yet.