OrcheStruct

Troubleshooting

Scan Performance

Large templates can take several minutes on first scan. That is normal when OrcheStruct is reading thousands of tracks and rich metadata.

P0Updated June 20, 2026OrcheStruct v1 launch beta, Cubase-first workflow

What Is Normal

A small track archive should scan quickly. A large master template with thousands of tracks, folders, plugins, routing, and patch clues can take several minutes on first scan.

  • First scans do the most work.
  • Cached or previously scanned sources can load faster.
  • Progress can move unevenly because different scan phases do different kinds of work.

When To Investigate

Investigate when the app is unresponsive, progress does not move for a long time on a small file, or the same source fails repeatedly with the same error.

  1. Record the file type and approximate track count.

  2. Capture the exact error text if there is one.

  3. Try a smaller known-good export.

  4. Check known issues before assuming the template is broken.