Midi Conflict Mainstage + Mobius (multi output)

[buzap]

Hi folks

I have a problem when using Mobius as Multi Ouput (Software Instrument) in Mainstage2:
I'm using 2 midi controllers (Korg NanoKontrol and NanoKey, in CC# mode) to control mobius. Now the problem is, when using it inside Mainstage2, it recognizes all my midi inputs as _one_ midi device and maps it to the same midi channel.

I don't think I can find enough CC parameters (ca. 70) to map, since I try to avoid the Mainstage standard CC parameters that previously were screwing up everything (1, 2, 11...; but also some weird stuff i.e. triggering _all_ channel sends at once ... crazy!!).
So how can I keep up different midi channels for two seperate midi controllers and still use Mobius in multi output mode?

thanks!
Buzap

[Per Boysen]

So how can I keep up different midi channels for two seperate midi controllers and still use Mobius in multi output mode?

By setting which MIDI Input a given Channel Strip (instrument, audio or MIDI channel strip) shall listen to. You do this by clicking on the Channel Strip to select it and then look inside the Channel Strip Inspector under the tab "MIDI Input".

Except for Channel Strips, as mentioned above, one can also set a certain MIDI In port for any object created in the layout window.

example:
Over here I mostly use two MIDI In ports, both physically located on my RME Firefae400 (but sometimes I pop in an extra USB MIDI In port as well). Port 1 I use for three different physical control surfaces (Behringer FCB1010 and two Faderfox MIDI Mixers). They all send on many different MIDI channels so do not use any MIDI In port set to "All Channels" (that would lead to a catastrofy ;-) Instead I select each graphical object in the design window and set its port, its MIDI channel and its event type.

Port 2 I use only for physical MIDI instrument playing, i.e. EWI that sends MIDI notes, pitchbend and and four different CC#s. For these CC#s I have of course also created knobs in the design view, but for different patches these physical channels from the instrument may target different parameters in the software depending on what synth, sampler or effect I want to play in that patch.

For Mobius I mostly use direct MIDI input according to the Moibus MIDI Control window settings that are the same as when Mobius is used in the standalone version. IMPORTANT here is to not use the same MIDI Channel and Port in Mainstage. You should not let Mainstage detect the MIDI port used for direct MIDI control of Mobius.

However, I use some host based MIDI control for MOibus. To do this you first make Mobius display those parameter to the host (Mobius/Parameters) and then you create screen objects in Mainstage's layout mode, learn them to the correct Port, MIDI channel and event type. Then go to Edit Mode and learn them to the plugin Mobius targeting the Mobius parameter. If using different Port, MIDI channel and event type you can have the same Mobius parameter reachable both as direct MIDI Input and by host based parameter control. I'm doing that and it works fine. I now use buttons in Mainstage like I previously used Buttons in the the Mobius GUI, because it looks better and can be designed to fit the screen better. Some buttons are assigned to external MIDI surfaces while other have to be mouse clicked on the screen.

Sorry, for the long post that is not very well thought out from an educational perspective ;-)) Just hacking fast because time time is about to run out here....

[buzap]

Hi Per

thanks, man :)

>You should not let Mainstage detect the MIDI port used for direct MIDI control of Mobius.
That part was very helpful. I'll try that.

My problem, at least on channel strip level, is that _all_ my midi controllers (3) are recognized by MS as _one_ midi device. Thus, I can't really differentiate on channel strip level.

Since I prefer looping "screen free", I'll probably skip controlling Mobius via Mainstage, I guess.

best regards
Buzap