The new Launchpad is brighter, faster and more powerful than the original, but costs the same. What's not to like?
Launchpad95: Improved Novation Launchpad remote scripts. These scripts are modified version of Ableton Live 9.2 scripts for Novation Launchpad and provide the same functionality but add support for editing the midi clips using a step sequencer, an Instrument Controller and Device Controller and an improved Instrument Mode. This feature is not available right now. Please try again later.
I'm starting to lose track of the number of grid-based DAW controllers I've reviewed over the last few years. From the original Monome to devices from Livid Instruments, Akai, Keith McMillen and, of course Ableton's new controller, the Push (reviewed in the March 2013 issue of SOS). Novation were pretty quick off the starting block with the original Launchpad , but a lot has happened in the intervening years, and the company clearly thought it was time for an update, in the form of the Launchpad S. The Launchpad S is the same price as the older model, but also, Novation say, faster and equipped with brighter LEDs, which addresses two of the major drawbacks of what from here on in I'll call the 'Launchpad 1'. The Launchpad S doesn't feature RGB LEDs or any other obvious functional additions over the original, but it's small, cheap and, in the short term, possibly more easily obtainable than the Push. Opening the box, you find the Launchpad S itself, a Getting Started guide, a registration card, some software template stickers and the characteristic right-angled USB cable.
There's no bundled CD or DVD (which, to be fair, would be wasted on many users without DVD drives); instead, all the 'bundled' software and documentation has to be downloaded. The online registration process is fiddly and irritating — more so than it needs to be, I feel, to protect the bundled applications from casual piracy — but once done, you get Ableton Live Launchpad Edition (which seems to be a rebadged Ableton Live 8 Lite), Loopmasters Content loops, additional manuals and Windows drivers.
The Launchpad S is compatible with Novation's Automap controller mapping system, although I didn't test this. Unlike its predecessor, the Launchpad S is a class-compliant MIDI device. It doesn't need any drivers and, sure enough, it appeared in the MIDI setup screen on my Mac Pro, which doesn't have the Launchpad 1 drivers installed. This is a major plus: I have a distrust of third-party drivers, and don't need the hassle of checking and upgrading drivers right up until support for my machine or OS is dropped. Class compliance also gives Linux-based musicians a chance to play, and makes the new Launchpad compatible with the iPad (via Apple's Camera Connection Kit — see the 'iLaunchpad' box).
The Windows drivers I mentioned above are a workaround for a Windows-specific problem: the standard drivers only allow a device to be accessed by one software program at a time. If you want to share the Launchpad S between applications, or use Automap, you'll need Novation's drivers.
The Launchpad S is exactly the same size (and, as far as I can ascertain, the same weight) as the Launchpad 1. The most obvious change is to the case: the original black has been replaced by a slightly metallic-looking dark grey (I think Airfix modellers used to call it 'gun metal'). All the controls are the same shape, size and in the same position, and side-by-side testing of the two Launchpad models suggests no change to the material or mechanism behind the buttons. There are, however, some changes to the labelling: the Launchpad S does not feature printing on the buttons themselves, with text and icons moved onto the case or, in some cases, removed altogether. I plugged the Launchpad S — as well as my Launchpad 1 — into my Mac via a powered USB hub, and fired up Ableton Live 9. After a few seconds of configuration, Live assumed it had two original Launchpads attached, and everything worked fine. The Launchpads operated identically.
Although it's not immediately apparent, a lot has changed under the hood in the Launchpad S: there's a new, faster processor, improved LED circuitry, and an updatable firmware layer that allows some device configuration. One of the configuration options is a device ID, allowing the USB name of the Launchpad to be changed; so if you want to use two or more units together, your software will now be able to tell which is which. Based on the press releases, I expected the Launchpad S to be much brighter than the Launchpad 1, but it wasn't; if anything, LEDs in half-intensity display mode were actually slightly dimmer. Only after downloading and reading the Advanced Features Guide did I learn that the device ships in low-power mode by default, in order to work when powered by an iPad; after a bit of fiddling, I was running in full-power mode, and the device was clearly brighter.
(This feature needs to be highlighted more prominently: I only discovered it by accident, because I download and read manuals.) Like the Launchpad 1, the S displays red, amber and green at variable intensities. Apart from the increased brightness, an improvement in the new model is the green LED colour: where the Launchpad 1's is a rather sickly pea-green, the Launchpad S shines out with an emerald intensity. The Launchpad S LED lighting is less diffused inside the buttons, so amber appears as slightly separate red and green sources. This irritated me a bit at first, but I soon ceased to notice. One consequence is that, in low-power mode, half-intensity red and half-intensity amber are difficult to distinguish. (Novation tell me that this might be addressed in a firmware upgrade.) In actual use, the only perceived difference between the Launchpad S and the Launchpad 1 — apart from LED colour and intensity — is refresh speed. The original model was pretty lethargic when it came to refreshing large numbers of LEDs at once; switching between mixer pages resulted in a pretty obvious scrolling effect as the pad matrix was repainted.
By comparison, the Launchpad S is lightning fast and the entire matrix updates in the blink of an eye. Most other matrix controllers on the market are essentially instantaneous; at last, the Launchpad is able to keep up. I liked the original Launchpad, but its limitations (dim LEDs, slow performance) were fairly apparent even when it was a new product, and in terms of functionality it's been rather eclipsed by more recent, full-colour grid controllers. I was expecting to be disappointed by the Launchpad S, which offers little new in terms of features, but I found myself liking it a lot. It's super-fast and super-bright, while remaining as simple, portable and affordable as the original. There's a lot to be said for conservative enhancement, and I think this particular controller sequel deserves to do rather well.
The Launchpad S claims iPad compatibility, so I plugged it into my iPad 3 via the Camera Connection adaptor to see how it fared. The Launchpad needs to be in low-power mode for the iPad to power it, but if you want the LEDs at full intensity you can go full-power by using a powered hub between the iPad and Launchpad. I fired up Novation's Launchpad iPad app and the Launchpad S obligingly mirrored the app, allowing loops to be triggered and effects to be punched in from the pads, with the LEDs following the display state of the app. I verified that the Launchpad S works as a generic MIDI controller using a free app called MIDI Monitor. Sure enough, the pads generate notes, while notes sent back illuminate the LEDs. Obviously, apps need to be made 'Launchpad-aware' to drive the device in all its multi-colour, multi-level glory.
Novation have made the MIDI specification available online, so if you're feeling adventurous you could probably roll some of your own support code in something like Liine's Lemur app. Novation Launchpad S £150 $170 pros.
A successful 'reboot' of an established and popular product. Clear, bright, high-intensity LED display. High-performance, fast LED refresh. USB class-compliant and iPad compatible.
Portable and affordable. Cons. No significant feature additions over the original Launchpad. The setup for full-power mode is only mentioned in the online Advanced Features Guide.
Half-intensity red and amber illumination hard to distinguish in low-power mode. The online registration process is fiddly and irritating. Summary The Launchpad S is simple, portable and affordable and offers better performance, a brighter display and easier interfacing than the original Launchpad. All contents copyright © SOS Publications Group and/or its licensors, 1985-2019. All rights reserved.
The contents of this article are subject to worldwide copyright protection and reproduction in whole or part, whether mechanical or electronic, is expressly forbidden without the prior written consent of the Publishers. Great care has been taken to ensure accuracy in the preparation of this article but neither Sound On Sound Limited nor the publishers can be held responsible for its contents. The views expressed are those of the contributors and not necessarily those of the publishers. Web site designed & maintained by PB Associates & SOS.
1 - How does ISO Controllers actually work? ISO Controllers is a standalone desktop application. It interacts with the Launchpad controller, receiving pad pressure information and sending color feedback to the pads.
In output ISO Controllers generates MIDI notes and MIDI controls (according to its selected isomorphic layout) to an output MIDI port. If you work with a Digital Audio Workstation (DAW), a virtual MIDI bus (virtual MIDI port) is required for sending MIDI from the ISO Controllers software to the DAW. 2 - How do I install ISO Controllers on my computer? To install the software, after you completed the download, unzip the ZIP package and look for the folder dedicated to your system OS. Copy this folder to any location you like to use on your computer. In this folder you will find the J74-ISO-Launchpad executable. Note for MAC users: When you try to start the application for the first time the Mac OS will by default block it, as it does not recognize the developer.
You solve this by doing: 1) Right Click on the app icon and select OPEN from the right-click menu choice. 2) A Pop-up window will come and ask you to confirm. Click on Open to confirm.
3) The app will run. Next time you can just open it as usual and you will not be asked again. 3 - Which Novation Launchpad models are supported? ISO Controllers currently supports all Launchpad models: Pro, MK2, classic, S and Mini (MK1 and MK2). 4 - Do I need other software to be installed on my computer (e.g.
Windows users are required to have the Novation driver for Launchpad installed on their system. This is necessary, as the default Windows OS USB driver for generic USB compliant devices will not be capable to support multiple applications at the same time and therefore prevent the use of ISO Controllers together with other software, such as a DAW. The Novation driver, instead, is capable of multi-client access and will allow the full functionality of the software. You can visit the Novation Support download page from:.
From the Support/Download select your device, download the driver and install it. Mac users do not need to install any driver for ISO Controllers to properly work with your Launchpad device. Also remember to enable the virtual MIDI port you wish to use as MIDI input port on the DAW preferences. 5 - What is a virtual MIDI bus?
Do I need to install this? In case of use with a Digital Audio Workstation (DAW) a virtual MIDI bus (virtual MIDI port) is required. This is a little software which allows you to send and receive MIDI between software applications, internally on your computer. This is necessary to let ISO Controllers send MIDI (in output) to a DAW (input). On the Mac you already have this: the standard IAC driver bus is a virtual MIDI bus and can be used for ISO Controllers communication to the DAW. On Windows, if you did not have that already installed, you need to get a virtual MIDI bus. Several (freeware) virtual MIDI ports are available on the Internet, such as LoopBE1, MIDI Yoke or MIDI OX.
LoopBE1 (and LoopBE30) are the recommended option in case of Windows systems. 6 - How do I configure ISO Controllers to recognize my Launchpad and send MIDI to a DAW? Before starting up the ISO Controllers application, be sure the Launchpad is properly connected. The first time you run ISO Controllers the software will try to auto-configure the Launchpad settings.
In most cases auto-configure should identify and auto configure the Launchpad properly (if connected), so all you would need to do is to select a MIDI output (virtual) port. Launchpad Select Settings You need to modify the Launchpad Select settings (red box in the picture below) ONLY if auto-configure failed to match your environment, for instance if you have multiple Launchpads (and wish to change the model ISO Controllers needs to use) or if you replace the Launchpad type with another model later on.
Meaning of the Launchpad Select settings 1. The Launchpad Select, Input defines FROM which Launchpad ISO Controllers receives MIDI (e.g.
The Launchpad Select, Output defines TO which Launchpad ISO Controllers sends MIDI (for colors) 3. The Ableton/Other selector only applies to the Launchpad MK2 (due to its Ableton Live behavior). IF the Launchpad in use is NOT a MK2 model, you can ignore this parameter. IF the model in use is a MK2 AND you work with Ableton Live as DAW, set Ableton/Other = Live (which is actually the default).
IF the model in use is a MK2 AND you work with another DAW (or any other software/hardware), set Ableton/Other = Other. The Launchpad Model selector defines the type of Launchpad. The following are the correct settings: - Launchpad Classic (the older, original model): Launchpad Model = 1 - Launchpad S: Launchpad Model = 1 - Launchpad MK2: Launchpad Model = 2 - Launchpad Mini: Launchpad Model = 1 - Launchpad Mini MK2: Launchpad Model = 1 (indeed the Mini MK2 behaves as an original Mini) - Launchpad Pro: Launchpad Model = 3 MIDI Output settings 5.
The MIDI Output menu selects the output port on which ISO Controllers sends MIDI output. This will be the port leading to the instrument you wish to play. It can be a physical MIDI port (e.g.
To a synthesizer) or a virtual MIDI port (an internal computer bus, Like the IAC driver on a Mac or a LoopBE or similar on Windows), the latter applicable in particular to the case of using a DAW. The Channel parameter defines to which MIDI channel of the MIDI Output port ISO Controllers need to send MIDI to. In most cases this can be left to channel 1. An exception to this applies to Logic X. See the notes about working with Logic X further in this manual (FAQ-7) on the topic. 7 - What about working with Logic X and ISO Controllers?
A DAW which requires a bit more attention in MIDI handling with ISO Controllers is Apple Logic X. Logic X happens to mix all input MIDI it can find and route it to any MIDI/Instrument track. By default, without any preference tweaking, you end up in getting both native Launchpad raw MIDI and the IAC bus MIDI (sent from the ISO Controllers software) mixed together in input to the instrument you are playing. Fortunately there are a few ways to address this.
Here a few suggestions: 1) Use per track MIDI channels with the Auto demix by channel if multitrack recording option in Logic X and a different MIDI channel for ISO Controllers. This way you can set ISO Controllers to send MIDI on a different MIDI channel than Launchpad's default ch 1 and separate notes in Logic X tracks. Essentially this is what you need to do: - In ISO Controllers select a channel different from 1 as output MIDI channel (example: channel 13) - In Logic X go to: File Project Settings Recording (see picture below) - On the MIDI section there is an unselected box which says Auto demix by channel if multitrack recording. Check this box (enable it) and close the window. Create TWO tracks in Logic X, let's say track 1 and track 2 (indeed, you need two).
On Track 1 select on the inspector of the track the same MIDI channel you specified in ISO Controllers (ch. 13 in this example).
On Track 2 select on the inspector of the track MIDI channel 1, the one normally use by default by the Launchpad raw MIDI. Note: Track 1 will also hold the instrument you wish to play.
Track 2 will have no instrument (just needed to catch Launchpad raw MIDI). With this approach you will set up Logic X to separate MIDI it receives from the two channels, on separate tracks. Logic X will send MIDI on ch 13 (ISO Controllers MIDI) to Track 1, and confine the raw Launchpad MIDI to Track 2. 2) Another option, if you do not use the Launchpad for other uses than ISO Controllers, is to remove the Launchpad raw MIDI input completely in Logic X. This is possible by configuring Logic MIDI Environment accordingly. In Logic MIDI Environment identify the virtual MIDI cable of the native Launchpad. What you need to do is to delete it.
Here are Apple's specifications on Logic MIDI Environment: 8 - I get double/strange notes when playing the Launchpad with ISO Controllers, can I fix that? If on the DAW the same Launchpad used by ISO Controllers is also enabled as input device, be sure to select for the MIDI track you wish to play ONLY the virtual MIDI port as MIDI input (the virtual MIDI port you selected as MIDI Output in ISO Controllers). In Ableton Live, for instance, you can do that by specifying on the track MIDI FROM menu the virtual MIDI bus you selected in ISO Controllers as output.
If you fail to assure this, and leave All Inputs enabled on the track, you will probably end up by having both ISO Controllers AND the raw Launchpad port as MIDI input to the track at the same time, and therefore with an improper behaviour. Remember: It is only from ISO Controllers that you wish to receive MIDI on this track (if you use ISO Controllers). Note: - It is also recommendable to disable the virtual port in use as MIDI output port on the DAW, this in order to avoid accidental MIDI loops. If you use Logic X as a DAW please refer to point FAQ-7 above for instructions on how to handle this. Here a few examples of setup: The picture below shows an example setup with Launchpad MK2 and Ableton Live, on a Mac: The items highlighted in red are actually default settings in Live and auto-configured settings in ISO Controllers. The items in purple are the required manual settings.
In the picture you can also notice that the virtual MIDI port (IAC Driver Bus 1) has only been enabled as input port in the DAW preferences and that, on the MIDI track armed for recording, the input MIDI From has been set explicitly to the virtual MIDI port (IAC Driver Bus 1) in question. Next an example of Launchpad S, also with Ableton Live, again on a Mac. As you can see configuration is pretty similar to the previous case. Notice in this case the Launchpad Model (LaunchModel) in ISO Controllers set to model 1 (it was model 2 in the MK2 case). The rest is conceptually identical to the previous case.
![]()
Now an example on Windows, this time with the Launchpad Pro (and again Ableton Live). Notice now that the Launchpad Model (LaunchModel) set to model 3 in ISO Controllers. The rest is again pretty similar to the previous cases (Live defaults and ISO auto-configure in red, manual settings in purple).
9 - I need to use multiple Launchpads, which settings should I use? If you have multiple Launchpad devices attached at the same time and like to switch from one to the other be sure to MANUALLY set up the options specified above for the Launchpad you wish to use.
Only after that you should be able to activate ISO Controllers on the specific Launchpad (as explained on the next page). The following gives a summary of the correct Launchpad Select settings as required by each model & OS case. Note(.): In the Classic, S, Mini, Mini MK2 case the Launchpad port name depends on the model in use. Note(.): the OS may give different names to the Launchpad ports. For instance the Launchpad Pro Port Nr. 2 (also referred to as Standalone port) changes name from Mac to Windows.
On a Mac it is named Launchpad Pro Standalone Port. On Windows it is named MIDIIN2 (Launchpad Pro) / MIDIOUT2 (Launchpad Pro) port. 10 - Everything is set up, but how do I activate/deactivate ISO Controllers Layouts from the Launchpad?
Depending on the environment in use, ISO Controllers activates the isomorphic layouts (and in the case of Ableton Live, switches Launchpad mode of operation) a bit differently. Here how to activate it in the various combinations of Launchpad model, OS and DAW. Launchpad Pro, with any DAW - Turn ON your Launchpad Pro - If you wish to use a DAW, start this up (this applies to any DAW, including Ableton Live) - Start now the ISO Controllers desktop application - Verify the selected Launchpad port and the MIDI Output configuration on ISO Controllers is correct for the Launchpad Pro case (see above). To enter ISO Controllers: hold down the Setup button and select Programmer mode (the fifth pad on the first row, in orange when Setup is hold down).
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |