5/6/2023 0 Comments Mainstage 3 tutorial deutsch![]() This is because the sound engine first gets the key you hit directly (without going via the MIDI port) and then gets it a second time (a fraction of a second later) via its MIDI IN port, because it was also sent over the MIDI OUT port. Because data is sent both to the MIDI OUT port and directly to the sound engine when Local Control is on, you can have weird 'echos' or retriggering of notes when you have Local Control on and a MIDI cable from MIDI OUT to MIDI IN. Think of the MIDI IN port as the input to the sound engine. If you would plug a single MIDI cable into both the MIDI OUT and MIDI IN ports, the control surface would send MIDI data to the MIDI OUT port, which goes to the MIDI IN port via the cable and is then played by the sound engine - in this setup (not that useful) the Stage would work the same with 'Local Control' on and off, because you use the MIDI cable to send the Stage's MIDI commands back to the Stage's sound engine. If you turn it off, MIDI data from the control surface is only sent to the MIDI OUT port and no longer also sent to the sound engine. ![]() Sending data from the control surface to the sound engine is done automatically, but you can turn it if off by turning off 'Local Control' this is a setting in the MIDI menu. If you send MIDI data from Mainstage to the Stage, you're actually sending control data to the sound engine, just like the control surface of your Stage would send MIDI data to the sound engine. Imagine that the knobs and keys (the 'control surface') on your Stage are connected via a MIDI cable to the sound-producing bits, the sound engine. MIDI only carries control data, such as which key you pressed and how hard you hit it. ![]()
0 Comments
Leave a Reply. |