open-audiovisual
Search GitHub

Novation

Novation Launch Control

Novation Launch Control is a MIDI hardware controller by Novation: 32 knobs and 24 buttons.

It sends CC and Note on channels 1, 9. The profile cites 1 source. 56 of its controls are marked unverified: the number is our best reading, and Learn rebinds it in one move.

  • Community notes
  • From QLC+
  • Layout generated automatically
  • 56 unverified
Kind
hardware device
Maker
Novation
Controls
56 controls
Messages
CC · Note
MIDI channels
1, 9
LED feedback
none sent
Layout
generated automatically
Data licence
Apache-2.0, from QLC+ (NOTICE)
Checked on hardware
not yet
Signals
midi/launchcontrol/…
Port name matches
/^launch\s*control(\s+(midi|port))*(\s+\d+)?$/i
NOVATION LAUNCH CONTROLKNOBSKnob 1A UsKnob 2A UsKnob 3A UsKnob 4A UsKnob 5A UsKnob 6A UsKnob 7A UsKnob 8A UsKnob 1B UsKnob 2B UsKnob 3B UsKnob 4B UsKnob 5B UsKnob 6B UsKnob 7B UsKnob 8B UsKnob 1A FaKnob 2A FaKnob 3A FaKnob 4A FaKnob 5A FaKnob 6A FaKnob 7A FaKnob 8A FaKnob 1B FaKnob 2B FaKnob 3B FaKnob 4B FaKnob 5B FaKnob 6B FaKnob 7B FaKnob 8B FaBUTTONS

Play Novation Launch Control on screen Raw JSON ↗ All controllers

Layout generated automatically: QLC+ has no faceplate data, so this is a list of the controls, not a picture of the device.

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 Novation Launch Control 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 Novation Launch Control
ControlTypeMessageChNumberSignalLED feedbackEvidence
Knob 1A User knob-1a-user knob CC 1 21 midi/launchcontrol/knob-1a-user — unverified
Knob 2A User knob-2a-user knob CC 1 22 midi/launchcontrol/knob-2a-user — unverified
Knob 3A User knob-3a-user knob CC 1 23 midi/launchcontrol/knob-3a-user — unverified
Knob 4A User knob-4a-user knob CC 1 24 midi/launchcontrol/knob-4a-user — unverified
Knob 5A User knob-5a-user knob CC 1 25 midi/launchcontrol/knob-5a-user — unverified
Knob 6A User knob-6a-user knob CC 1 26 midi/launchcontrol/knob-6a-user — unverified
Knob 7A User knob-7a-user knob CC 1 27 midi/launchcontrol/knob-7a-user — unverified
Knob 8A User knob-8a-user knob CC 1 28 midi/launchcontrol/knob-8a-user — unverified
Knob 1B User knob-1b-user knob CC 1 41 midi/launchcontrol/knob-1b-user — unverified
Knob 2B User knob-2b-user knob CC 1 42 midi/launchcontrol/knob-2b-user — unverified
Knob 3B User knob-3b-user knob CC 1 43 midi/launchcontrol/knob-3b-user — unverified
Knob 4B User knob-4b-user knob CC 1 44 midi/launchcontrol/knob-4b-user — unverified
Knob 5B User knob-5b-user knob CC 1 45 midi/launchcontrol/knob-5b-user — unverified
Knob 6B User knob-6b-user knob CC 1 46 midi/launchcontrol/knob-6b-user — unverified
Knob 7B User knob-7b-user knob CC 1 47 midi/launchcontrol/knob-7b-user — unverified
Knob 8B User knob-8b-user knob CC 1 48 midi/launchcontrol/knob-8b-user — unverified
Button UP User button-up-user button CC · momentary 1 114 midi/launchcontrol/button-up-user — unverified
Button DOWN User button-down-user button CC · momentary 1 115 midi/launchcontrol/button-down-user — unverified
Button LEFT User button-left-user button CC · momentary 1 116 midi/launchcontrol/button-left-user — unverified
Button RIGHT User button-right-user button CC · momentary 1 117 midi/launchcontrol/button-right-user — unverified
Button 1 User button-1-user button Note · momentary 1 9 · A-1 midi/launchcontrol/button-1-user — unverified
Button 2 User button-2-user button Note · momentary 1 10 · A#-1 midi/launchcontrol/button-2-user — unverified
Button 3 User button-3-user button Note · momentary 1 11 · B-1 midi/launchcontrol/button-3-user — unverified
Button 4 User button-4-user button Note · momentary 1 12 · C0 midi/launchcontrol/button-4-user — unverified
Button 5 User button-5-user button Note · momentary 1 25 · C#1 midi/launchcontrol/button-5-user — unverified
Button 6 User button-6-user button Note · momentary 1 26 · D1 midi/launchcontrol/button-6-user — unverified
Button 7 User button-7-user button Note · momentary 1 27 · D#1 midi/launchcontrol/button-7-user — unverified
Button 8 User button-8-user button Note · momentary 1 28 · E1 midi/launchcontrol/button-8-user — unverified
Knob 1A Factory knob-1a-factory knob CC 9 21 midi/launchcontrol/knob-1a-factory — unverified
Knob 2A Factory knob-2a-factory knob CC 9 22 midi/launchcontrol/knob-2a-factory — unverified
Knob 3A Factory knob-3a-factory knob CC 9 23 midi/launchcontrol/knob-3a-factory — unverified
Knob 4A Factory knob-4a-factory knob CC 9 24 midi/launchcontrol/knob-4a-factory — unverified
Knob 5A Factory knob-5a-factory knob CC 9 25 midi/launchcontrol/knob-5a-factory — unverified
Knob 6A Factory knob-6a-factory knob CC 9 26 midi/launchcontrol/knob-6a-factory — unverified
Knob 7A Factory knob-7a-factory knob CC 9 27 midi/launchcontrol/knob-7a-factory — unverified
Knob 8A Factory knob-8a-factory knob CC 9 28 midi/launchcontrol/knob-8a-factory — unverified
Knob 1B Factory knob-1b-factory knob CC 9 41 midi/launchcontrol/knob-1b-factory — unverified
Knob 2B Factory knob-2b-factory knob CC 9 42 midi/launchcontrol/knob-2b-factory — unverified
Knob 3B Factory knob-3b-factory knob CC 9 43 midi/launchcontrol/knob-3b-factory — unverified
Knob 4B Factory knob-4b-factory knob CC 9 44 midi/launchcontrol/knob-4b-factory — unverified
Knob 5B Factory knob-5b-factory knob CC 9 45 midi/launchcontrol/knob-5b-factory — unverified
Knob 6B Factory knob-6b-factory knob CC 9 46 midi/launchcontrol/knob-6b-factory — unverified
Knob 7B Factory knob-7b-factory knob CC 9 47 midi/launchcontrol/knob-7b-factory — unverified
Knob 8B Factory knob-8b-factory knob CC 9 48 midi/launchcontrol/knob-8b-factory — unverified
Button UP Factory button-up-factory button CC · momentary 9 114 midi/launchcontrol/button-up-factory — unverified
Button DOWN Factory button-down-factory button CC · momentary 9 115 midi/launchcontrol/button-down-factory — unverified
Button LEFT Factory button-left-factory button CC · momentary 9 116 midi/launchcontrol/button-left-factory — unverified
Button RIGHT Factory button-right-factory button CC · momentary 9 117 midi/launchcontrol/button-right-factory — unverified
Button 1 Factory button-1-factory button Note · momentary 9 9 · A-1 midi/launchcontrol/button-1-factory — unverified
Button 2 Factory button-2-factory button Note · momentary 9 10 · A#-1 midi/launchcontrol/button-2-factory — unverified
Button 3 Factory button-3-factory button Note · momentary 9 11 · B-1 midi/launchcontrol/button-3-factory — unverified
Button 4 Factory button-4-factory button Note · momentary 9 12 · C0 midi/launchcontrol/button-4-factory — unverified
Button 5 Factory button-5-factory button Note · momentary 9 25 · C#1 midi/launchcontrol/button-5-factory — unverified
Button 6 Factory button-6-factory button Note · momentary 9 26 · D1 midi/launchcontrol/button-6-factory — unverified
Button 7 Factory button-7-factory button Note · momentary 9 27 · D#1 midi/launchcontrol/button-7-factory — unverified
Button 8 Factory button-8-factory button Note · momentary 9 28 · E1 midi/launchcontrol/button-8-factory — unverified

Have this unit? It takes a few minutes to check this data. Verify Novation Launch Control with your unit →

LED feedback is not modeled for this one yet, so OAV does not light its LEDs. Every control still plays and sends its message.

Sources

Where this profile comes from

Imported from QLC+ on 2026-11-04. resources/inputprofiles/Novation-LaunchControl.qxi

Notes

Imported from QLC+. The messages are what its community profile lists; nobody has checked them on a unit for this project, so every control is unverified. QLC+ has no faceplate data, so the layout was generated from the list of controls and does not look like the device. The port-name pattern was written from the model name, not read from a unit. QLC+ numbers these controls without a MIDI channel, so channel 1 here is a placeholder: the unit may send on another.

Port names it recognises

matches
/^launch\s*control(\s+(midi|port))*(\s+\d+)?$/i

Signals

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

Use it

Use Novation Launch Control 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="novation-launch-control" 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=novation-launch-control&readout"
            width="720" height="465" style="border:0;max-width:100%" allow="midi"
            title="Novation Launch Control"></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="novation-launch-control" 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=novation-launch-control to make the on-screen controller this one; a real Novation Launch Control is recognised by its port name.

javascript
document.head.prepend(Object.assign(document.createElement('script'), { src: 'https://openaudiovisual.com/p5/oav-p5.js?profile=novation-launch-control' }));
In your sketchControlMessage
knob1Knob 1A User knob-1a-userCC 21 · Ch 1
knob2Knob 2A User knob-2a-userCC 22 · Ch 1
knob3Knob 3A User knob-3a-userCC 23 · Ch 1
knob4Knob 4A User knob-4a-userCC 24 · Ch 1
knob5Knob 5A User knob-5a-userCC 25 · Ch 1
knob6Knob 6A User knob-6a-userCC 26 · Ch 1
knob7Knob 7A User knob-7a-userCC 27 · Ch 1
knob8Knob 8A User knob-8a-userCC 28 · Ch 1
knob(9)Knob 1B User knob-1b-userCC 41 · Ch 1
knob(10)Knob 2B User knob-2b-userCC 42 · Ch 1
knob(11)Knob 3B User knob-3b-userCC 43 · Ch 1
knob(12)Knob 4B User knob-4b-userCC 44 · Ch 1
knob(13)Knob 5B User knob-5b-userCC 45 · Ch 1
knob(14)Knob 6B User knob-6b-userCC 46 · Ch 1
knob(15)Knob 7B User knob-7b-userCC 47 · Ch 1
knob(16)Knob 8B User knob-8b-userCC 48 · Ch 1
… and 16 more, up to knob(32), in the same order
p5.js sketch
function draw() {
  background(knob1 * 255);   // Knob 1A User · CC 21
  circle(width / 2, height / 2, 50 + knob2 * 300);   // Knob 2A User · CC 22
}

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 →

Other software

Use this controller outside this project

The same data, as files other programs read. Nobody has tested these on this exact unit unless the table above says so.

QLC+

An input profile: every control and LED value, for lighting. Copy it to your user folder (macOS ~/Library/Application Support/QLC+/InputProfiles, Linux ~/.qlcplus/inputprofiles, Windows %USERPROFILE%\QLC+\InputProfiles) and restart QLC+. Then set the MIDI channel of this input to Omni.

Mixxx

A starting point, not a finished mapping: decks, EQ and hot cues go to the controls in order. Put both files in the folder that Preferences → Controllers → Open User Mapping Folder opens, then remap what you like with the Learning Wizard.

The data itself

Everything above comes from this file: faceplate, messages, LEDs, SysEx and who checked what. tools/export-controller.mjs writes these files from any profile.

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.