MIDI input routing resets to "No MIDI Input" for "Scaler 3" source

1. Summary/Title MIDI input routing in Cubasis 3 resets to “No MIDI Input” when assigning the same track MIDI source to multiple recipient tracks.

2. Description When using multi-track MIDI generator plugins (such as Scaler 3) inside Cubasis 3, sending MIDI from a single source track/plugin to multiple recipient tracks causes previous track assignments to drop.

Steps to reproduce:

  1. Create Track 1 in Cubasis and load Scaler 3 (AUv3).

  2. Inside Scaler 3, set up multiple internal “Scaler Tracks” assigned to different MIDI channels, with internal instruments set to “No Instrument” to output MIDI directly.

  3. Create Track 2 (“Chords”) and Track 3 (“Bass”) in Cubasis, each hosting a virtual instrument.

  4. Set the MIDI Input of Track 2 to Track 1 (Scaler 3).

  5. Set the MIDI Input of Track 3 to Track 1 (Scaler 3).

Workarounds currently tested:

  • Setting Track 2 and Track 3 to “All MIDI Inputs” while setting Track 1 to “All MIDI Outputs” resolves the issue by allowing channel separation to work.

  • Routing Scaler 3’s output to an external background app (Camelot Pro via virtual MIDI ports “Camelot MIDI IN” / “Camelot MIDI OUT”) allows both Track 2 and Track 3 to select the virtual MIDI port as input simultaneously without dropping assignments.

3. Expected Results Cubasis should allow multiple target tracks to simultaneously select the same source track or plugin (Track 1 / Scaler 3) as their MIDI Input source, filtering by their respective MIDI channels.

4. Actual Results When assigning Track 1 as the MIDI Input for Track 3, the previously configured MIDI Input on Track 2 is automatically lost and resets to “No MIDI Input”. Cubasis treats Track 1 / Scaler 3 as an exclusive MIDI source that can only be assigned to a single track at a time.

Environment

  • Device: iPad Pro 13-inch (M2)

  • OS: iPadOS (latest)

  • Host App: Cubasis 3.6.8 for iPad

  • Plugins / Virtual MIDI Used: Scaler 3 (AUv3), Camelot Pro (for workaround testing)

The bug was detected in this lifestream: https://www.youtube.com/watch?v=FO-j5hSuN8o&t=648s