Route audio from piano via 2xTRS to audio interface and into mainstage, and use that as input of the channel strip,
Use program change and bank select on the channel strip with the values from the manual, Because local control is off, speakers are also off.
#MAINSTAGE MIDI MONITOR DRIVERS#
This means, that you also must send the midi notes to the P-115 to have them rendered via midi. In the MIDI Environments Clicks & Ports section create a monitor (or any other useless device) and connect the IAC drivers output to the monitors input. Local control is set to off, and you can fully use midi to control the sound. You can work with the piano sounds from the piano panel settings, where you manually select the instrument sound and play. That, in combination with the setting 'local control on/off', gave me the following insight: Best of all, you can keep your CPU very low, because now Reason (in my case) is managing it.The note that put me on the right track, was in de midi manual: 'Program change and other like channel messages received will not affect the panel settings of the instrument or the notes you play on the keybed'. You can re-use any instrument throughout as many patches as you like, and split it/use chord triggers/arpeggiate it as you wish, using only one instance of that instrument.ģ. Reason can open VSTs, so now you can combine any 3rd party instruments and/or effects to your hearts content, and not just be limited to the AU plugins in MS.Ģ. The advantages of using MS and Reason this way are several:ġ. Seems pretty obvious, then again I missed it, being a MS newbie though, so thought I'd post this to safe the trouble for anyone out there trying to accomplish the same.
The solution is pretty simple:Īll you have to do is go to the concert level and then un-tick "Send unassigned MIDI to all Channel Strips" Feedback occurred because MainStage was picking up MIDI from MIDIpipe output and taking it back in again, without it being assigned as an input in any way. As mentioned in other posts, MainStage is ALWAYS listening to all virtual MIDI inputs ALL the time, no way to choose which does it listen to or not. This method is of course valid with any DAW such as Ableton, not just Reason. Using a MIDI monitor, I can see MainStage is picking back up again whatever the virtual MIDI port is outputting. Even without Reason open, MainStage is still producing the feedback. I tried this same setup with Gig Performer and it works just fine. MIDIPipe has only one virtual MIDI input port and one virtual MIDI output port straight. Deleted everything in the MainStage channel strips, including the metronome, which I also hid (metronome channel is set to not receive MIDI from anywhere). set the input on the sole keyboard in the MainStage workspace to accept only MIDI-in from my controller (keep in mind there's nothing else in the workspace, just a lonely 49 key keyboard). The problem is that MainStage is creating an endless MIDI Feedback that for the love of me, I can't figure out where it's coming from. MIDI-out from MainStage is sent to MIDI-in in Reason via the MIDI virtual port (MIDIPipe). My keyboard goes into a MainStage "External Instrument" channel strip. So my solution was to wire MainStage to Reason via a virtual MIDI port, such as the IAC Driver, or MIDIPipe. I want to use MainStage with Reason, but also be able to use VSTs within Reason (which means I avoid ReWire).