Hi all. Cubase 13.0.30 pro, Win 10. In the Functions Browser>Mix Console I changed the Bank/Channels number from 8 to 16 (I am about to put a Behringer x32 as a controller for the faders, for the moment used a Midi Twister to prepare things) and next time I opened Cubase, in the Mix Console, the Output section was not there. (It was there before I changed the Bank/channels number). I changed back to 8, restarted etc, it is gone. I can still assign a parameter to the Master Output by selecting a function by clicking it in the project, but if I don’t save the song or a template, next time I open cubase it does not remember it. The Output section reappears if I select a different controller (and re-disappears if I select Twister again). Any thoughts? TIA
I can replicate this here, and yes, I would consider this to be a bug. Upon saving the settings json of the remote, there’s a miss concerning the output zone.
If you don’t mind losing your current mappings and just keep the control surface, you can delete the connected json file from [yourDocumentsFolder]\Steinberg\Cubase\MIDI Remote\User Settings. You’ll recognize it by its name. Then you can restart Cubase, and the output in mixConsole should be visible. Now, as as workaround, if you immediately assign a control to an element of the output, and then set the mixer bank zone to 16 channels, the output channel will no longer be invisible from the assistant. At least this is what I’ve observed.
Thank you very much m.c. Well I kind of do mind losing the mappings on my other 3 banks of 16x2 encoders/switches of Midi Twister that are already mapped to Channel Settings, Eq, plug ins etc. I dont mind living with this bug for the moment, I will pay attention to export/back up scripts more often as a precaution until (let’s hope) Steinberg fixes the bug. Thanks again!
This sounds maybe related or similar to what I had reported quite a while ago?
I missed this post! Yes it does soumd similar! However, after I removed all mappings to this section and restarted, the output section has not reappeared. (Same in cubase 12)
So your scenario would seem similar but a little different than mine, but potentially pointing to a common root problem area.