C14: Changing MIDI inputs also changes MIDI channels bug?

Cubase
,
1

[Edit] Realized that I probably would have done better posting this in the Cubase 14 bug report thread, so apologies for that.

Cubase 14.0.32 - big template - changing MIDI input on several tracks at once:
This is normally done easily by selecting all the desired MIDI tracks and then click to change the MIDI input in the inspector in one go by holding shift+option (Mac).
However, since moving to Cubase 14, this command is impossible as it now also changes ALL MIDI channels to whatever comes first in the row (usually MIDI channel 1) to the same number. This means that I’ll now have to manually change each and every track out of hundreds to the desired MIDI input. Has anyone else experienced this?
I am absolutely sure this is a bug.

Thanks

2

Confirmed, on my end (C 14.0.32 Pro, Windows 10 22H2), using the Shift + Alt keys combination, as specified when hovering the mouse above the Input Routing dropdown menu. :neutral_face:

I have tried using the MixConsole instead but the result is the same. Maybe there is a reason for this, but I don’t know it…

3

I can’t possibly imagine there being a reason, but if that’s the case, it’s an incredibly poor and illogical design choice. In every other version through 13, this has always worked as expected.
For users with big templates, having to go through each and every track manually is a huge and tedious time waster.

4

I agree, but maybe as a more or less acceptable workaround, you could make different templates with Input Routing settings adapted to each of your use cases.

5

Thanks for the advice, although that doesn’t work for me. I always create and edit templates on my mobile rig (laptop) for compatibility reasons before migrating them to my studio rig. That means I have separate MIDI keyboards for each setup respectively and must be able to change the MIDI input device accordingly after migration to avoid the ”missing device” message on startup, followed by empty slots in the inspector.

6

First: Great that you post your issue in its own topic and not a collective topic. People think collective topics are good but the opposite is the case.

Also: this doesn’t look like a design choice, my nose tells me it is just a bug.

7

Hi,

This is a known and already reported issue (first time in Cubase 13.0.20). Thank you.

9

I see and well, that makes sense. A dedicated thread for each topic will get a lot easier to navigate in the long run. I just thought this kind of obvious bug report on its own would risk getting moderated, but apparently I was wrong.

1 Like
10

???
No, quite the contrary. I would think of this as a very constructive topic.

11

Thanks for confirming, Martin.
Considering that it’s a bug which breaks incredibly basic functionality, this has to get corrected as soon as possible.

12

Great to know. Thanks for the heads-up!