Troubleshooting
Known Issues and Recovery
Start with the known-issues page, then collect app version, OS version, Cubase version, action, source file type, and exact error text.
Start Here
The current known-issues page is the support shield for launch. If the behavior is listed there, follow the workaround before filing a new report.
What To Include In A Report
The most useful reports are precise and boring. They make the problem reproducible.
- OrcheStruct app version.
- macOS version.
- Cubase version if Cubase is involved.
- Surface used: Inspector, Tracks, Library, Studio, Cue Builder, Software, OSF.
- Source file type and approximate size/track count.
- Exact action taken immediately before the issue.
- Exact error text or screenshot.
What Not To Send By Default
Do not send private client files, license keys, unreleased music, or complete project folders unless a specific diagnostic item is requested.