![]() There's no aftertouch on the keys but the pads are both velocity- and pressure-sensitive and will do single or polyphonic aftertouch. They are velocity-sensitive, offering three selectable curves or can be turned off. The white keys are shiny and grip your fingers whereas the black keys have a less grippy matt texture. The keys themselves have a relatively light, synthy feel. The faders have a similar feel and are now accompanied by RGB buttons which will no doubt make themselves useful. ![]() The knobs are upright, cylindrical, feel slightly rubberised to the touch, and are taller and much more solid than the ones on the Launchkey Mini. The pads are nicely set just that little bit lower and all the other buttons follow the style and height. The look is cemented by the replacement of the red three-digit display with a cool blue-backed LCD with two rows of 16 characters. It's still made of plastic but doesn't seem as clunky as many 61-keyed MIDI controllers can feel. The hardware has a poise to it that raises both a smile and your expectations. I wonder how much customer feedback went into agonising over that decision? Pads are now over on the left with faders in the middle, just off-centre, and only the transport controls on the right. It's pleasingly compact for a 61-note controller at only 26cm deep, which is a bonus for our crowded desktops and studio spaces.īeyond the sharp lines the most obvious change is that the pads and faders have swapped positions. What were they thinking with the coloured underbelly of the MkI and MkII? It was really easy to unpack, slid out of the box with one hand and I was delighted to see foam packed under the keys. It's all clean lines, angles and elegance and it does that thing where it instantly makes the very capable MkII look garish and unfashionable. This new version looks sedate and serious. The features are the same across the range except that only the 49 and 61 have the fader bank. Along with the usual 25- and 49-key options there's now a 37-key version for those people who find the 49 too big or the 25 too small. The model under review is the largest in the range at 61 keys. It's taken longer than expected, but everything that made the Mini MkIII a very cool little controller has been stretched out into the full-sized and infinitely more playable Launchkey MkIII. When Novation revealed the Launchkey Mini MkIII last year you knew it wouldn't be long before the rest of the Launchkey range followed suit. ![]() Once the play-head reaches that position, the commands will be sent over.The third generation Launchkey offers versatile control over hardware and software alike. In this case, we will have Logic change the patch to 017 The "Val" column of your Program change command will determine the patch number within the active bank.In this case, a value of 3 will select bank C. Adjusting the "Val" of the LSB events from 1-4 will toggle between banks A-D (respectively).In this situation, the time difference between each event is negligible, and should produce the effect of the patch changing right on the first down beat of the 5th measure. The location you choose will depend upon the exact point in time you want the commands to be sent.Delay the program change's position slightly, as shown above, so that it is received after the bank change messages, yet in rapid succession (5 4 1 1 5 4 1 2).In this case, we will change our Summit to Bank C, Patch 017, make sure your event list looks exactly like this: We will have two controller events for the bank change, and then a program change event. Let's press the "+" button and add two "Controller" events onto the list.ĥ. If we hover our mouse over the boxed area indicated in the above screenshot, we can select a "Controller" type event. The Events Manager will pop up on the right-hand side of Logic's window.Ĥ. By default, the keyboard shortcut to open up Logic's Events manager is the "D" key. We will adjust exactly when to send our bank and patch change commands in Logic's Events Manager. This will create an empty green MIDI region on the track, and serve as the point in the time that the commands will be sent. Create an empty MIDI region by right-clicking on the track's timeline, and selecting "Create empty Region". Name this MIDI track " MIDI OUT to Summit". *Please note that if you could also use a DIN midi connection to a Midi interface, and simply use that as the midi destination, to achieve the same result on your Peak or Summit. In our example, our Summit's global channel is 3, and we are setting out destination to Summit, Ch 3. We will choose our Summit as the MIDI destination and choose the MIDI channel. In this example, there is a USB cable connected from our Summit and Computer. First, we'll create an external MIDI track, and select "MIDI Destination" as our MIDI interface.
0 Comments
Leave a Reply. |