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.

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.

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

Commands like route selected, rename, and folder operations work reliably. Fully conversational natural-language requests 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.