open-audiovisual
Search GitHub

AKAI Professional

AKAI MIDImix

AKAI MIDImix is a MIDI hardware controller by AKAI Professional: 24 knobs, 9 faders and 19 buttons.

It sends CC and Note on channel 1. The profile cites 3 sources. No control is flagged unverified.

  • Manufacturer docs
  • Community notes
  • LED feedback
Kind
hardware device
Maker
AKAI Professional
Controls
52 controls
Messages
CC · Note
MIDI channels
1
LED feedback
yes, lights are driven by MIDI
Signals
midi/midimix/…
Port name matches
/midi\s*mix/i
MIDIMIXSend All123456789101112131415161718192021222324RecRecRecRecRecRecRecRec12345678Master

Play AKAI MIDImix on screen Full screen ↗ Raw JSON ↗ All controllers

Drag knobs and faders · tap pads and keys · or plug the real one in and press Connect. Nothing is sent anywhere unless you add a MIDI out.

MIDI implementation

Every control of AKAI MIDImix and the message it sends

Generated from the profile file, so it is the same table the on-screen controller plays. Channels are 1–16; numbers are real MIDI numbers.

MIDI implementation of AKAI MIDImix
ControlTypeMessageChNumberSignalLED feedbackVerified
1 k1 knob CC 1 16 midi/midimix/k1 — yes
2 k2 knob CC 1 20 midi/midimix/k2 — yes
3 k3 knob CC 1 24 midi/midimix/k3 — yes
4 k4 knob CC 1 28 midi/midimix/k4 — yes
5 k5 knob CC 1 46 midi/midimix/k5 — yes
6 k6 knob CC 1 50 midi/midimix/k6 — yes
7 k7 knob CC 1 54 midi/midimix/k7 — yes
8 k8 knob CC 1 58 midi/midimix/k8 — yes
9 k9 knob CC 1 17 midi/midimix/k9 — yes
10 k10 knob CC 1 21 midi/midimix/k10 — yes
11 k11 knob CC 1 25 midi/midimix/k11 — yes
12 k12 knob CC 1 29 midi/midimix/k12 — yes
13 k13 knob CC 1 47 midi/midimix/k13 — yes
14 k14 knob CC 1 51 midi/midimix/k14 — yes
15 k15 knob CC 1 55 midi/midimix/k15 — yes
16 k16 knob CC 1 59 midi/midimix/k16 — yes
17 k17 knob CC 1 18 midi/midimix/k17 — yes
18 k18 knob CC 1 22 midi/midimix/k18 — yes
19 k19 knob CC 1 26 midi/midimix/k19 — yes
20 k20 knob CC 1 30 midi/midimix/k20 — yes
21 k21 knob CC 1 48 midi/midimix/k21 — yes
22 k22 knob CC 1 52 midi/midimix/k22 — yes
23 k23 knob CC 1 56 midi/midimix/k23 — yes
24 k24 knob CC 1 60 midi/midimix/k24 — yes
Mute mute1 button Note · momentary 1 1 · C#-1 midi/midimix/mute1 note 1 · on 127 / off 0 yes
Mute mute2 button Note · momentary 1 4 · E-1 midi/midimix/mute2 note 4 · on 127 / off 0 yes
Mute mute3 button Note · momentary 1 7 · G-1 midi/midimix/mute3 note 7 · on 127 / off 0 yes
Mute mute4 button Note · momentary 1 10 · A#-1 midi/midimix/mute4 note 10 · on 127 / off 0 yes
Mute mute5 button Note · momentary 1 13 · C#0 midi/midimix/mute5 note 13 · on 127 / off 0 yes
Mute mute6 button Note · momentary 1 16 · E0 midi/midimix/mute6 note 16 · on 127 / off 0 yes
Mute mute7 button Note · momentary 1 19 · G0 midi/midimix/mute7 note 19 · on 127 / off 0 yes
Mute mute8 button Note · momentary 1 22 · A#0 midi/midimix/mute8 note 22 · on 127 / off 0 yes
Rec rec1 button Note · momentary 1 3 · D#-1 midi/midimix/rec1 note 3 · on 127 / off 0 yes
Rec rec2 button Note · momentary 1 6 · F#-1 midi/midimix/rec2 note 6 · on 127 / off 0 yes
Rec rec3 button Note · momentary 1 9 · A-1 midi/midimix/rec3 note 9 · on 127 / off 0 yes
Rec rec4 button Note · momentary 1 12 · C0 midi/midimix/rec4 note 12 · on 127 / off 0 yes
Rec rec5 button Note · momentary 1 15 · D#0 midi/midimix/rec5 note 15 · on 127 / off 0 yes
Rec rec6 button Note · momentary 1 18 · F#0 midi/midimix/rec6 note 18 · on 127 / off 0 yes
Rec rec7 button Note · momentary 1 21 · A0 midi/midimix/rec7 note 21 · on 127 / off 0 yes
Rec rec8 button Note · momentary 1 24 · C1 midi/midimix/rec8 note 24 · on 127 / off 0 yes
1 f1 fader CC 1 19 midi/midimix/f1 — yes
2 f2 fader CC 1 23 midi/midimix/f2 — yes
3 f3 fader CC 1 27 midi/midimix/f3 — yes
4 f4 fader CC 1 31 midi/midimix/f4 — yes
5 f5 fader CC 1 49 midi/midimix/f5 — yes
6 f6 fader CC 1 53 midi/midimix/f6 — yes
7 f7 fader CC 1 57 midi/midimix/f7 — yes
8 f8 fader CC 1 61 midi/midimix/f8 — yes
Master master fader CC 1 62 midi/midimix/master — yes
Bank ◀ bankleft button Note · momentary 1 25 · C#1 midi/midimix/bankleft — yes
Bank ▶ bankright button Note · momentary 1 26 · D1 midi/midimix/bankright — yes
Solo solo button Note · momentary 1 27 · D#1 midi/midimix/solo — yes

LED feedback is modeled for 16 of its controls: the LED column says which message lights each one.

Sources

  • manufacturer MIDImix User Guide v1.0 (AKAI)layout: 24 knobs (3 per channel), 8 mute buttons (amber-backlit; hold Solo to make them solo buttons), 8 record-arm buttons (red-backlit), 8 + 1 master faders, Bank Left / Right, Solo, Send All; Ableton Live control surface and port name "MIDI Mix"; 23.9 × 20.1 cm. It prints no MIDI numbers (the MIDImix Editor holds them).
  • community Ableton Live 12 MIDI Remote Script MIDI_Mix (decompiled; non-official)all on channel 1: knob rows CC 16 20 24 28 46 50 54 58 / +1 / +2 (the bottom row is pan), faders CC 19 23 27 31 49 53 57 61, master CC 62; mute notes 1 4 … 22, solo (Solo held) 2 5 … 23, rec arm 3 6 … 24; bank left 25, bank right 26, solo 27; LEDs note-on 127 / 0
  • community Ardour AKAI_MIDIMix_Normal_Mode.map and AKAI_MIDIMix_EQ_Mode.map (non-official)agree with the Ableton script: faders 19 … 61, master 62, mute / solo / rec notes 1–24, bank 25 / 26, solo 27, knobs 16–18 … 58–60 (EQ map), channel 1

Notes

The factory mapping (what the MIDImix Editor calls the default), channel 1. AKAI's own documents print no numbers, so every number here comes from Ableton's shipped MIDI_Mix script and Ardour's maps, which agree. Holding Solo turns the Mute row into solo buttons sending notes 2, 5 … 23 — a layer the faceplate cannot show, so those notes are not modelled (they still arrive as midi/ch/1/note/<n>). Send All re-sends every knob and fader position and has no message of its own. LED feedback: mute (amber) and rec-arm (red) buttons, note-on 127 / 0, lit while held.

Port names it recognises

matches
/midi\s*mix/i

Signals

Every control publishes midi/midimix/<control> (0..1), plus /raw; pads add /hit, encoders /delta, keys /on /off and n<note>; the last control touched is midi/midimix/last.

Use it

Use AKAI MIDImix in your own work

  1. Embed it with one line

    No import map, no build step. Change layout, add hardware="ask" for a Connect button.

    html
    <script type="module" src="https://openaudiovisual.com/packages/midi/element.js"></script>
    <oav-controller profile="akai-midimix" readout></oav-controller>
  2. Or as an iframe

    For places that only take an iframe. Every event arrives as a postMessage.

    html
    <iframe src="https://openaudiovisual.com/embed/controller/?profile=akai-midimix&readout"
            width="720" height="627" style="border:0;max-width:100%" allow="midi"
            title="AKAI MIDImix"></iframe>
    <script>
      // every control the visitor plays arrives here
      addEventListener('message', (e) => {
        if (e.data?.source !== 'openav' || e.data.type !== 'control') return;
        console.log(e.data.detail.signal, e.data.detail.value);
      });
    </script>
  3. Send it to Ableton, TouchDesigner or Resolume

    What you play on screen leaves as real MIDI on the IAC bus (macOS) or a loopMIDI port (Windows). The steps are on the catalog page.

    html
    <!-- what you play on this controller → the IAC bus (macOS) → Ableton, TouchDesigner, Resolume -->
    <script type="module" src="https://openaudiovisual.com/packages/midi/element.js"></script>
    <oav-controller profile="akai-midimix" midi-out="IAC" readout></oav-controller>
    <!-- Windows: midi-out="loopMIDI" · let the visitor pick a port: midi-out="ask" -->

    macOS: Audio MIDI Setup → MIDI Studio → IAC Driver → “Device is online”. Windows 11: the built-in Windows MIDI Services have a loopback (not tested by us); older Windows: install loopMIDI, add a port and use midi-out="loopMIDI".

In p5.js, with one line

The one-line injection names knobs, faders and pads by their order in this profile, the order of the table above. Add ?profile=akai-midimix to make the on-screen controller this one; a real AKAI MIDImix is recognised by its port name.

javascript
document.head.prepend(Object.assign(document.createElement('script'), { src: 'https://openaudiovisual.com/p5/oav-p5.js?profile=akai-midimix' }));
In your sketchControlMessage
knob11 k1CC 16 · Ch 1
knob22 k2CC 20 · Ch 1
knob33 k3CC 24 · Ch 1
knob44 k4CC 28 · Ch 1
knob55 k5CC 46 · Ch 1
knob66 k6CC 50 · Ch 1
knob77 k7CC 54 · Ch 1
knob88 k8CC 58 · Ch 1
knob(9)9 k9CC 17 · Ch 1
knob(10)10 k10CC 21 · Ch 1
knob(11)11 k11CC 25 · Ch 1
knob(12)12 k12CC 29 · Ch 1
knob(13)13 k13CC 47 · Ch 1
knob(14)14 k14CC 51 · Ch 1
knob(15)15 k15CC 55 · Ch 1
knob(16)16 k16CC 59 · Ch 1
… and 8 more, up to knob(24), in the same order
fader11 f1CC 19 · Ch 1
fader22 f2CC 23 · Ch 1
fader33 f3CC 27 · Ch 1
fader44 f4CC 31 · Ch 1
fader55 f5CC 49 · Ch 1
fader66 f6CC 53 · Ch 1
fader77 f7CC 57 · Ch 1
fader88 f8CC 61 · Ch 1
fader(9)Master masterCC 62 · Ch 1
p5.js sketch
function draw() {
  background(knob1 * 255);   // 1 · CC 16
  circle(width / 2, height / 2, 50 + knob2 * 300);   // 2 · CC 20
}

Encoders, buttons, wheels and strips are not numbered: read them as midi.cc[number] in the table above, or react in controlChange(cc, value, ch).

The whole p5.js page →

Missing

Is your controller not here?

Open an issue with the brand and model, whether you have the unit and a link to the manual. Or write the profile yourself: it is one JSON file.

GitHub

Is something in this data wrong?

Every number on this page comes from one JSON file. If it disagrees with your unit or the manual, tell us which firmware you checked and we fix the file.