Known issues and workarounds.

Very large templates take time to scan.

Templates with thousands of tracks, full master templates, and large KOMPLETE setups can take several minutes on first scan. The scan reads every track, plugin, and routing detail. Subsequent loads use a cache and are fast.

Workaround: Let the first scan finish. A progress bar shows status, and you can switch tabs while it runs.

Progress can move unevenly across scan phases.

Large-template scans do different kinds of work at different times: XML structure, enrichment, patch clues, routing, and cache writes. Some phases can appear slower than others even when the scan is still healthy.

Workaround: For a first scan, wait for the final result unless the app reports an error or the same small file stalls repeatedly.

Write-back is Cubase-only for now.

OrcheStruct can read Logic Pro and Pro Tools projects for track list, families, and structure, but applying changes back, such as renames, colors, and routing, is currently supported only for Cubase XML. Logic and Pro Tools write-back is in progress.

Workaround: Use OrcheStruct to plan and organize Logic and Pro Tools projects, then apply changes manually in those DAWs until write-back ships.

Live Session depends on Cubase bridge setup.

File scanning can be useful without live Cubase control, but Live Session refresh, track reveal/select, Patch Capture, and route application need the bridge pieces installed and the intended Cubase project open.

Workaround: Confirm Live Session can refresh and select one harmless visible track before using Patch Capture or Auto Route.

Hidden or folded Cubase tracks may require reveal fallback.

A live row click first tries a fast select path. If Cubase does not confirm the target, OrcheStruct may need a broader reveal pass before the exact selection can be verified.

Workaround: Refresh Live Session, make sure the intended project window is frontmost, and retry selection before applying any route changes.

Auto Route is preview-first.

Auto Route plans route decisions before applying them in Cubase. Rows can be pending, already correct, skipped, refused, or unresolved depending on evidence and active stem-set context.

Workaround: Review the route preview and apply only when the pending destinations match your expectation.

Some tracks are intentionally refused or skipped.

OrcheStruct may refuse to route structural rows, duplicate names, weak family-only evidence, inactive stem targets, or tracks where the current Cubase readback does not match the planned operation.

Workaround: Treat refused rows as review items. Fix family/product/routing evidence or route those tracks manually.

The command bar understands structured commands, not free-form chat yet.

Commands like route selected, rename, reorder, and surface-specific repair operations work reliably. Fully conversational natural-language requests belong to OS Agent workflows and are still being expanded.

Duplicate folder names can need disambiguation.

If your template has two folders with the same name in different branches, an agent command may ask you to pick the target folder or may need a more specific instruction.

Workaround: Include the parent folder in your command.

Plugin inventory display is partial.

OrcheStruct detects inserts and plugins, and you can filter by them, but a richer per-track plugin panel is still in progress.

Sub-family nesting is limited.

Some sub-families, for example PIANO, currently fold into their parent family folder, such as KEYS, rather than nesting as a separate sub-folder. Full nested sub-folders are planned.