Import Tracks from Project: state not importing (Output Routing, Track Heights, Automation State)

Cubase
,
1

I’m very happy that expression maps and drum maps now import correctly in Cubase 15, but there are a few more remaining elements of track state that still don’t seem to import properly. Fixing these issues would make track import for large orchestral templates much smoother!

Here are two small source projects and an empty destination project to import into that should reproduce the issue (along with screenshots):

2026-04-30_C15-Import-Tracks-Issues.zip (3.7 MB)

Steps to reproduce from those projects:

  1. Open Destination.cpr (or just start from a blank project).
  2. File > Import > Tracks from Project… and select Instr A.cpr.
  3. In Import Options dialog, select Folder A (which should also check all tracks that are nested within it). Make sure Track Data to be Imported includes Events and Parts, Channel and Inspector Settings, and Automation. Hit OK.
  4. File > Import > Tracks from Project… and select Instr B.cpr.
  5. In Import Options dialog, select Folder B. Hit OK.

-> Result (as I saved in Destination (after imports).cpr) = The following elements of imported track state don’t import properly:

  • Output Routing: most seriously, the MIDI tracks under Folder B are incorrectly routed to Instr A (from Instr A.cpr) instead of Instr B (from Instr B.cpr).
  • Track Heights: don’t match the source project they were imported from (and they seem to be inconsistent from one import to the next).
  • Read Automation State: not enabled where it should be (on the automated plug-in parameters “AUX 1 Return” and “AUX 2 Return” under the Instr A - Out1 and Instr B - Out1 instrument return tracks.

Screenshot of that destination after import:

image
image1556×1512 333 KB

Versus e.g. what source Instr B.cpr project looks like:

image
image1564×820 108 KB

Tested on: Cubase 15.0.21 Build 252 (Apple Silicon) running on macOS Sequoia 15.7.4.

(There does seem to be a workaround for Output Routing: if the instrument track is instead ordered first–ABOVE any MIDI tracks that output to it–then the Output Routing assignment for those MIDI tracks seems to import correctly. So that suggests that there might be a 1-pass import algorithm that can’t handle the routing for the MIDI tracks correctly when the instrument track they output to hasn’t been processed yet).