OrcheStruct

Inspector

Review and Edit Template Structure

Inspector is the review desk: use it to understand the template, correct bad assumptions, and prepare changes before saving.

P0Updated June 20, 2026OrcheStruct v1 launch beta, Cubase-first workflow
OrcheStruct Inspector showing a scanned template with track rows, metadata columns, suggestions, and a folder properties panel.
Inspector is the review desk: use filters, metadata columns, suggestions, and the side panel to verify structure before saving changes.

What To Review First

Start with structural decisions before detailed patch cleanup. If family, folder, and routing are wrong, downstream naming and catalog decisions will be noisier.

  • Family: strings, brass, winds, percussion, keys, synths, guitars, FX, hybrid, and related groups.
  • Folder: where the track belongs in the template hierarchy.
  • Routing: the bus or stem target the track should use.
  • Name: the visible DAW name composers rely on under deadline.
  • Library identity: vendor, product, engine, patch, and articulation clues.

Correction Pattern

Treat corrections as teaching moments for the system. A good correction should be specific enough to help the current track and future similar tracks.

  1. Filter to a small problem set.

  2. Open a representative track.

  3. Correct the strongest known field first, usually family, prefix, or product.

  4. Review the suggested downstream changes.

  5. Apply in batches only after the sample row looks right.

Avoid Over-Correcting

Do not force weak library guesses just to make the table look green. It is better to leave a row reviewable than to commit the wrong vendor or product identity.