VI MIDI input channel settings ignored after project close and re-open

We have Cubase 14.0.20.240 according to Get info on the cubase app bundle - running on MacOS 13.7.3 (Ventura) via an Intel Mac. There are 2 VI’s controlled from an external keyboard with a L.H. and R.H split sending MIDI over USB on respective MIDI channels 1 and 3. There is no overlap between the 2 zones. It works just fine to add the 2 VI plugins we need into a new Cubase 14 project, set the MIDI in for each to the USB output of the keyboard controller, and then set the MIDI input channels to 1 and 3 as needed for each plugin. L.H. notes play on VI #1 and R.H. notes plat on VI #2 as expected.

But after closing and re-opening the project, the MIDI input channels still list channels 1 and 3 respectively - but now the channel filter no longer works. Both VI’s sound all notes played across the entire keyboard transmitted on either MIDI channel 1 or 3. A workaround is to set each plugin’s MIDI input channel to “any” and then set it back to the specific channel 1 or 3. Now the keyboard split works properly again. Wondering if there is a more permanent solution.

Hi, @cdr80rev2

Confirmed, but on my end, reselecting the MIDI channel input directly is also a workaround. Beside this, the Input Group and Channel dropdown list will behave as expected during the whole Cubase session.

As a test, I also tried to create track presets with given MIDI input channels already set, but it doesn’t work either : in example, incoming MIDI notes on channel 2 triggers a VI, even if the Input Group and Channel was previously set at 3, in the previously saved track preset and project.

AFAICS, the only reliable way to solve this is to use the Input Transformer with the Track option on each track, activate one of the four modules and select in its presets list, the relevent Factory Presets > Channel Filtering one.

1 Like

Thanks cubic13 for the feedback and verification . I have since tried the same project in Neundo 13 (where the MIDI input filtering works just fine when the project is closed and then re-opened), and then in the demo version of Nuendo 14 (where it behaves the same was a Cubase 14). So I presume this is a bug, side affect, or maybe regression with updates to the common Cubase/Nuendo 14 code base. Unless I am missing something it, looks like I would have to duplicate setting the split point in the input transformer on each MIDI track (which I was trying to avoid).