[NAMM] M-Audio Code controller keyboard series
M-Audio introduces at NAMM 2015 a new series of MIDI controller keyboards, called Code and comprising three 25, 49 and 61-key models.
The new M-Audio Code series follows the steps of Nektar with MIDI keyboards with DAW integration. The three versions include pre-mappings for Ableton Live, GarageBand, Logic, Pro Tools and Cubase.
All the models include semi-weighted keybeds with aftertouch, 16 velocity-sensitive backlit pads, an X/Y touch pad, modulation and pitch bend wheels, knobs and faders with macro ASCII support, a transport section compatible with the HUI and Mackie Control modes, a 4-zone keyboard split function and a 6-digit LED display.
Connectors on the M-Audio Code include 5-pin DIN MIDI in and out, expression and sustain pedal inputs, and a USB port that powers the units.
The Code 25, 49 and 61 ship with Ableton Live Lite and the AIR Music Technology Loom and Hybrid 3 virtual instruments.
This new series will be available starting from April, for US prices of $249 for the Code 25, $299 for the Code 49 and $349 for the Code 61.
Viewers of this article also read...
-
Rent-to-own Ozone 9 and Neutron 3 together on Splice
Splice has bundled iZotope’s latest software audio processors and offers them at a lower price through their rent-to-own program.
-
Arturia AudioFuse 8PRE audio interface review
Just over two years ago, French manufacturer Arturia first stepped into the world of audio interfaces. More recently at NAMM 2019, the Grenoble-based company announced two new models, one of which the AudioFuse 8Pre. Has it been a successful addition to the line?
-
Antelope Discrete 4 Synergy Core review
About a year and a half ago, Antelope released the Discrete, a new range of
Thunderbolt & USB interfaces including discrete preamps, their famous FPGA
module as well as the stack of audio effects that would usually come with it.
Now back in June 2019, Antelope releases a new version of its Discrete 4, this time
providing dual DSP chips in addition to the FPGA. Marketing ploy or real step
forward?
