Support |
> Per Boysen wrote: > >> Mainstage does not at all work along the old hardware based concept of >> "sending MIDI into plug-ins that are programmed to react". What >> Mainstage offers is a software concept based on two steps: >> >> 1) The user creates his own on-screen set of graphic control objects >> that directly corresponds to the physical control hardware used. These >> screen objects has MIDI Learn capabilities and connect with incoming >> MIDI events from the physical control hardware. This graphic interface >> may not be changed often once it has been set up (not until you buy a >> new MIDI mixer, MIDI pedal-board etc) >> >> 2) Next phase is to set up the binding between the on-screen objects >> and parameters in the software. When doing this you can apply data >> scaling, reverse a parameter's response on a pedal's range etc, etc. On Wed, May 27, 2009 at 8:08 PM, andy butler <akbutler@tiscali.co.uk> wrote: > So surely the assumption is that the midi controller isn't programmable > by the user? No. If the midi hardware control gear is programmable or not has nothing to do with the Mainstage interface. The software simply adapts to whatever MIDI is sent in and translates that into tweaking the targeted plug-in parameter values. > This looks like a backward step compared to simply routing midi into a > plugin. Yes, from a hardware based background it is backwards. But this software puts the focus on the user interface on the screen. Whatever outboard MIDI control gear or software plug-ins used in the box is second row. > Can't imagine that it's compatible with any but the most basic of midi > controllers. It is compatible with everything because it has full MIDI learn functionality. Greetings from Sweden Per Boysen www.boysen.se www.perboysen.com