Integrating External Instruments In Ableton Live

Adam McLellan has some nifty tips   02-Aug-13

If you're anything like me you have a geeky, borderline unhealthy, obsession with hardware gear. Unfortunately it can be notoriously clunky when used in conjunction with software, especially with Ableton Live. While Live's "External Instrument" device is quite useful for integrating hardware, one thing that's sorely lacking is the ability to automate MIDI CCs from the arrangement view. Really, the only "out of the box" solution for automating CCs is to use clip envelopes, and this just doesn't cut it for me.

In this month's post I'm going to explore a couple options to work around this. The first option I'll explore is what I call the "Instrument Rack Hack"--basically, using a blank Instrument Rack and exploiting Live's MIDI "Remote Control" functionality. The second, and more elegant solution, is to create custom devices in Max For Live.

Commercial or homebrew VST editor

First and foremost you should see if any commercial or homebrew VST editors are available for your synth. If so you'll probably save yourself a lot of time going this route. If not, read on!

Rack hack

The rack hack exploits Live's "remote control" feature--that is, its ability to send control messages to keep external devices in sync with changes made in Live. Typically this would be used with a control surface; say, a mixer with motorized faders. The idea is that changes may be made via Live or the control surface, and the remote control option is what ultimately keeps the two sync.

This may seem a bit counter-intuitive at first: we don't actually want to control anything in Live, so what do we MIDI-map? Thankfully, Instrument Rack macros don't technically need to be mapped to anything within Live. So let's start by creating an instrument rack and expanding the macros section:

If your gear does transmit CC data, select up to 8 parameters and map them now through the typical process: CTRL + M (on Windows) -> click a knob -> move a knob on the controller -> CTRL + M again.

Important: under Live's Preferences ensure "Remote Control" is enabled for the corresponding MIDI output.


Next we'll use Live's External Instrument device to transmit MIDI and receive (an added benefit is that this leverages Live's delay compensation algorithms and also allows us to apply an additional compensation for any delay in the hardware)

More From: ABLETON
Even more news...

3 Comments... Comments are closed while we transition to Disqus

Chris S    Said...

Thank you so much for this article. It's exactly what I've been looking for. I've had a completely unhealthy obsession with integrating my Virus C synth with Live 9. Up until now, I've only been successful at clip envelopes, but thanks to your article, I've now learned how to address automation using the midi-mapped instrument rack. That is amazing! I have a question though. It basically boils down to this... Instead of mapping just 8 parameters with the instrument rack, is it possible to map all/most of the synth's parameters onto an instrument rack? I've done this with some of my vsts (Synth1) using the 'configure' option in Live and am hoping there is some way to do it similarly with an external instrument. Why, you might ask? Well, when designing sounds, my process has been to improvise on a loop--tweaking things on the fly. I'd like to record the midi information as I tweak so that I can go back through the track and edit out the best parts, save any great presets, etc. Thanks again. Any help is greatly appreciated.

12-Jan-14 11:01 PM

Chris S    Said...

Also, I'm not sure if it'll help or not but there are a couple additional things that might help facilitate this process. I'm not really sure though? There is an editor here: and there are also a couple max for live devices people have built: Thanks again! Much appreciated!

12-Jan-14 11:15 PM

Chris S    Said...

I think I figured out how to do it using a maxforlive template and the external instrument. Thanks for giving me the spark!

14-Jan-14 12:22 AM

Comments are closed while we transition to Disqus