![good piano patches for mainstage 3 good piano patches for mainstage 3](https://i1.wp.com/mardermusic.com/wp-content/uploads/2018/02/02-Save-as-Patch.png)
- #Good piano patches for mainstage 3 Patch
- #Good piano patches for mainstage 3 software
- #Good piano patches for mainstage 3 Pc
Not easily accomplished using incoming PC messages.
#Good piano patches for mainstage 3 Patch
I want this MS patch to call up piano patch 2 and brass patch 5. The first is a Kontakt instrument bank containing 3 piano patches, the second is another containing 8 brass patches. A Mainstage patch contains two channel strips. Here's a simplified example of what I'm trying to accomplish. If you want to do this simultaneously with 2 Kontakts, you would probably need to make sure that all the correct sounds are in the right slots within each bank. If you have Kontakt on a channel strip on any of these patches, with a Bank setup such that your piano sounds are on "Unused" PC slots within the bank, Kontakt will switch sounds within the bank. Whichever patch MS is currently on, it will pass through any other PC (ie not 1-4) to the channel strips. If MS receives an incoming PC message that is "UN-USED" (ie not mapped to a MS patch), the PC message will be passed through to any channel stripes in that Patch.įor example, if you have 4 Patches (PC1-4), MS will call up Patch 4 when it receives a PC4 message. If the Patch List has individual patches assigned to distinct PC messages, MS will change Patch to the one mapped to the appropriate incoming message. MS generally responds to Program Change messages that come in from an external MIDI controller.
![good piano patches for mainstage 3 good piano patches for mainstage 3](https://i.pinimg.com/originals/49/a4/d6/49a4d61dff3be05474acfa41515efbdd.jpg)
I read the MS release notes introducing this feature, but have difficulty grasping where these 'unused Program Changes' originate, how MS differentiates between used and unused, and how the PG message gets to the channel strips, Mainstage 3 seems to have so much to offer, but without the ability to assign individual instance patches within each Mainstage patch it's useless to my way of working. It could be that my mindset is used to a certain way of working and a little creative input could shake my approach enough to solve this vexing problem. If someone has found a workaround, I'd love to hear about it. Kontakt instrument bank and Guitar Rig channel strips stay on whatever patch assignment they had on initial launch of Mainstage and changing Mainstage patches has no effect on the patches of the instances. Any instances used within that patch are completely ignored.
![good piano patches for mainstage 3 good piano patches for mainstage 3](https://ourworshipsound.com/wp-content/uploads/2020/05/ORGAN-SQUARE.jpeg)
With KORE, it's simplicity itself to assign an initial MIDI program change number to every instance used in a patch, and if I need to change any programs on instances within that patch, to assign a button sending PG increment or decrement messages to that particular instance.įrom everything I've read and tried, it seems that Mainstage's only response to MIDI program change is to change Mainstage patches.
#Good piano patches for mainstage 3 software
The brick wall I ran into was in trying to get MIDI Program change messages assigned to Kontakt instrument banks, software synths and Guitar Rig. Mainstage 3 on the face of it looked like a truly viable alternative, and my initial tests with CPU and memory comparisons (especially when using channel strip aliases) were promising enough to investigate further. It's stable and elegantly does what I need, but since it has been discontinued by NI, I keep my ears open for possible replacements. For my live performance keyboard rig, I've been using KORE 2 for the last several years. Appealing to more experienced users in hopes of an answer.