Currently Being ModeratedOct 14, 2012 1:22 AM (in response to LucaBabetto)
You can select which keyboard/MIDI input port and channel is assigned to operate the MainStage patch changes, or you can specify that no Program Changes are accepted.
In Edit mode, select the Concert in the Patch List then make the required changes in the Concert Inspector.
Currently Being ModeratedOct 15, 2012 7:56 AM (in response to LucaBabetto)
BUT, when I change a patch on my keyboard, the output strip goes to a +6db..
Sounds like the keyboard is transmitting additional messages other than just the Program Change (probably Expression CC11 or Volume CC7). You need to carefully check what messages are being transmitted (I'd record them in Logic to have a close look).
You could block them by making dummy Screen objects mapped to "Nothing" and "Do Not Pass Thru" or use the new Assignments and Mappings pane to do the same thing.
Yes, you're right.
The keyboard is sending many other messages when the patches change. This causes not just the output fader to jump to +6db as I initially noticed, but it screws up quite all the other channel strips as well! It changes the volume and the bypass settings of the VSTs.
I've told the keyboard not to send program changes inputs but it just solved the patch change problem.
How can I get rid of this?
Currently Being ModeratedOct 15, 2012 9:14 AM (in response to LucaBabetto)
You may have several choices:
Tell the keyboard NOT to transmit this info (consult the manual for the KBD).
Create screen control objects in MS to block the MIDI events getting through to MS Channel Strips. To do this thoroughly, you'll need to establish exactly which messages are being transmitted when you do a Program Change. I use Logic for this: record the MIDI output when you do a Prog change and examine in the Event List. You could use any MIDI sequencer for that, or maybe MIDI Monitor, possibly track it down via the keyboard manual.
Two ways to create the "Blocks" in MS:
A) Create small Screen Controls manually assigned to the offending incoming MIDI Data (one for each CC message coming in). In the Screen Control Inspector, set these controls 'MIDI Thru' to "Do Not Pass Through"
B) In MS 2.2 you can do effectively the same thing without creating Screen Controls, in the Assignments and Mappings Pane in Edit Mode. Create an assignment and Map it to nothing.
Well, it sounds like I'll have to update it..
I didn't know you had to pay 30 more bucks to update a thing you've already bought!!
I've put an eye on the Kurzweil manual but it seems I can't block those MIDI messages from the keyboard, so I'm going to try the update lead..
Thanks again, man!!
Currently Being ModeratedOct 16, 2012 2:23 AM (in response to LucaBabetto)
Updating to MS 2.2 is not going to solve this problem: it will only give you a second way to block specific incoming MIDI messages.
You need to track down which MIDI messages are causing the issues, and block them. MIDI Monitor will help here:
I suggest that you start by making Screen Controls assigned to the Kurzweil MIDI Port and channel, and then to MIDI CC7 (Volume) and CC11 (Expression). Make sure that these controls are set to Do Not Pass Thru". These will prevent the MIDI messages from reaching the MS channel Strips.
You may need to make other "Blockers" as well
I've managed to get rid of the volume fader problem, I've created a dummy fader which "absorbs" the MIDI message.
But one of the keyboard buttons sends CC29 and I need it on the patches, though that message seems to be messing up the patch.
I see CC100, too..
So, I'm tracking down ALL the messages sent with Logic and then block them in Mainstage..
Currently Being ModeratedOct 18, 2012 5:30 AM (in response to LucaBabetto)
Updated to v2.2.2, gone to the mappings window: there were some "unassigned" controls sent by default to all the channel strips.
I've told MS to block all the unwanted messages and now it works great!