Skip navigation

Mainstage patch change

777 Views 10 Replies Latest reply: Oct 18, 2012 5:30 AM by LucaBabetto RSS
LucaBabetto Calculating status...
Currently Being Moderated
Oct 14, 2012 1:17 AM

Hi guys!


I can't get rid of a problem with Mainstage 2.


I'm using a Kurzweil PC1SE as a Master Keyboard.


The problem is that when I change a patch in the Keyboard, the buttons change the Mainstage patches as well!


I've created the concert starting from the internal preset and I've configured the MIDI settings as they should be setted.


Any suggestions?





MacBook Pro, Mac OS X (10.6.8), 2,4 GHz Intel Core 2 Duo, 8GB RAM.
  • CCTM Level 6 Level 6 (8,510 points)
    Currently Being Moderated
    Oct 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.




  • CCTM Level 6 Level 6 (8,510 points)
    Currently Being Moderated
    Oct 15, 2012 7:56 AM (in response to LucaBabetto)

    LucaBabetto wrote:


    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.




  • CCTM Level 6 Level 6 (8,510 points)
    Currently Being Moderated
    Oct 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.




  • CCTM Level 6 Level 6 (8,510 points)
    Currently Being Moderated
    Oct 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





More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.