Silently hiding under the mixing desk: Roland A-880

Recently I had to revise some cabling and routing under the mixing desk, when I found a rack device. A MIDI patch bay, the A880. It was happily blinking and had silently done its useful job there for at least 10 years. After looking it up, it turned out to be an actually more than 30 years old product from Roland! You can also see the dust on the cables in my setup.

Then the question is: do you need a MIDI patch bay? The answer is twofold. MIDI itself is an ancient protocol. If you have MIDI devices and a computer hooked up via MIDI, I will say that you cannot do without a MIDI patch bay. However, MIDI is showing its age and probably some of you are using USB instead. Also, new MIDI standards are now seriously being discussed. Possibly resulting in something altogether new that may not be supported by the A-880.

The current standard MIDI protocol is ancient. And when you look at it technically it is also slow and limited. Of course it is fast enough to connect a keyboard to an instrument or a computer. Most devices allow daisy-chaining to connect any chain of computer and keyboard and MIDI instruments you have. However, that is when you will find that MIDI has its limitations. If you daisy-chain more than three devices you will likely hit one of its limitations: bandwidth. When too much information passes through a single chain, then you will get traffic jams and you might start hearing hick ups.

This is where a MIDI patch bay kicks in. Instead of daisy-chaining you can now connect devices in parallel. The A-880 connects 8 inputs to 8 outputs. Each of the individual connections to a midi device from the patch bay can now pass the maximum amount of data without traffic jams. Also with some simple button presses you can determine which input gets sent to which output. Allowing you to have more keyboards and route inputs from there to more devices. The forever friendly blinking lights show you which inputs go to which outputs.

Inputs 1 and 2 are special. They are positioned on the front panel and easily reachable when you assign those as merging inputs (<- edited because of Fred’s comment below). I use the patch bay in its most simple and useful form. The inputs from my main master keyboard are mixed with the input from the computer and then sent out through all remaining outputs at once. This is the blinking pattern that been the core of my setup for more than a decade. Only occasionally I push the Signal button. Then the blinking lights show which devices actually send data.

It may be that the future of MIDI does not include the A-880. This will be the moment when I will switch off this blinking, silently working work horse. And I will remove it from its hidden place under the mixing desk.

Komplete Kontrol A49, you’re not using it right

Please note: starting with version 10.0.5, support for the A40 keyboard is integrated in Ableton live. If you use a new version of Ableton Live please read this article.

After a month of working on singing and performing. Everything but working in the studio, I wanted to get up and running again with making music. As always, I started with updating the studio software. When updating the Native Instruments (NI) suite I am using, the A49 was part of the updates. When playing around in Ableton Live after that it soon became obvious that things did not work quite right. So it was time to reserve some hours diving into this.

The NI Native Access manager was updated and the first step is then of course to check all the software installations inside it. It soon turned out that the VST installation path of Komplete Kontrol was not correct anymore. NI likes to think that it is the only source for plugins on your computer, so I needed tot tell it that VSTs are located elsewhere on the computer. The Komplete Kontrol installation was then fixed by reinstalling. Nice.

After checking if both the version of Komplete Kontrol inside Live and Komplete Kontrol as a standalone application were matching. Things started working again. A plugin rescan was needed to pick up all NI instruments in both versions, so a lot of instrument settings were not matching up apparently. Also a quick scan of the MIDI integration settings revealed that the integration was still correct.

I use the Komplete Kontrol Rack VST in Ableton Live, but when you update your NI software this is not automatically updated in Ableton Host Integration. Time to copy vst files (vst) all over again from C:\Program Files\Common Files\Native Instruments\Host Integration\Ableton Live to D:\Documents\Ableton\Library\Presets\Instruments\Instrument Rack. Or some equivalent on a Mac.

This Komplete Kontrol instrument rack can host any plug in instrument and map the A49 knobs to macros to controls in the instrument. Please note: Only use this for all instruments other than NI instruments! You must manually map any control to any control inside the instrument. Not very pretty, but once you’ve set it up it works.

And what if you do want to use a NI instrument? I also found out that instead of adding Kontakt to a track to start working with a NI instrument, as I always did, its better to use the Komplete Kontrol plugin. This immediately gives you full control with the A49 and allows you to quickly switch instruments on the fly. Oh well. Never too old to learn.