OrcheStruct

Inspector

Save a Cubase XML Export

Save after review, not before. Confirm the changed fields, export to a new file, and verify the result in Cubase before using it as your working template.

P0Updated June 20, 2026OrcheStruct v1 launch beta, Cubase-first workflow
OrcheStruct toolbar with Re-scan and Save XML buttons.
Use Save XML only after review. Re-scan updates the source analysis; Save XML writes a reviewed output for Cubase verification.

Safe Save Rule

For launch, always save to a new output file first. Keep the original export untouched until the Cubase import result has been verified.

Save Workflow

Before saving, scan the visible change summary. You should be able to explain why each class of change is being written.

  1. Finish the review pass in Inspector.

  2. Check changed names, families, folders, colors, and routing decisions.

  3. Save/export to a new Cubase XML file.

  4. Import or reopen the result in Cubase.

  5. Spot-check known tracks before adopting the file as a working template.

If The Result Looks Wrong

Go back to the original source and the OrcheStruct review state. Do not compound the problem by editing the exported file repeatedly without identifying which change class failed.

  • Routing wrong: check stem set and route preview assumptions.
  • Colors wrong: check family palette and Cubase color mapping.
  • Folders wrong: check folder strategy and duplicate folder names.
  • Names wrong: check naming scheme and prefix corrections.