open-audiovisual
Search GitHub

M-VAVE

M-VAVE SMC-PAD

M-VAVE SMC-PAD is a MIDI hardware controller by M-VAVE: 32 pads, 8 knobs and 5 buttons.

It sends CC and Note on channels 1, 10. The profile cites 1 source. 45 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
  • 45 unverified
Kind
hardware device
Maker
M-VAVE
Controls
45 controls
Messages
CC · Note
MIDI channels
1, 10
LED feedback
none sent
Layout
generated automatically
Data licence
Apache-2.0, from QLC+ (NOTICE)
Checked on hardware
not yet
Signals
midi/smcpad/…
Port name matches
/^smc[\s-]*pad(\s+(midi|port))*(\s+\d+)?$/i
M-VAVE SMC-PADKNOBSKnob 1Knob 2Knob 3Knob 4Knob 5Knob 6Knob 7Knob 8PADSBUTTONS

Play M-VAVE SMC-PAD 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 M-VAVE SMC-PAD 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 M-VAVE SMC-PAD
ControlTypeMessageChNumberSignalLED feedbackEvidence
Left (<) left button CC · momentary 1 25 midi/smcpad/left — unverified
Right (>) right button CC · momentary 1 26 midi/smcpad/right — unverified
Play play button CC · momentary 1 27 midi/smcpad/play — unverified
Stop stop button CC · momentary 1 28 midi/smcpad/stop — unverified
Record record button CC · momentary 1 29 midi/smcpad/record — unverified
Knob 1 knob-1 knob CC 1 30 midi/smcpad/knob-1 — unverified
Knob 2 knob-2 knob CC 1 31 midi/smcpad/knob-2 — unverified
Knob 3 knob-3 knob CC 1 32 midi/smcpad/knob-3 — unverified
Knob 4 knob-4 knob CC 1 33 midi/smcpad/knob-4 — unverified
Knob 5 knob-5 knob CC 1 34 midi/smcpad/knob-5 — unverified
Knob 6 knob-6 knob CC 1 35 midi/smcpad/knob-6 — unverified
Knob 7 knob-7 knob CC 1 36 midi/smcpad/knob-7 — unverified
Knob 8 knob-8 knob CC 1 37 midi/smcpad/knob-8 — unverified
Pad 1 pad-1 pad Note · velocity 10 36 · C2 midi/smcpad/pad-1 — unverified
Pad 2 pad-2 pad Note · velocity 10 37 · C#2 midi/smcpad/pad-2 — unverified
Pad 3 pad-3 pad Note · velocity 10 38 · D2 midi/smcpad/pad-3 — unverified
Pad 4 pad-4 pad Note · velocity 10 39 · D#2 midi/smcpad/pad-4 — unverified
Pad 5 pad-5 pad Note · velocity 10 40 · E2 midi/smcpad/pad-5 — unverified
Pad 6 pad-6 pad Note · velocity 10 41 · F2 midi/smcpad/pad-6 — unverified
Pad 7 pad-7 pad Note · velocity 10 42 · F#2 midi/smcpad/pad-7 — unverified
Pad 8 pad-8 pad Note · velocity 10 43 · G2 midi/smcpad/pad-8 — unverified
Pad 9 pad-9 pad Note · velocity 10 44 · G#2 midi/smcpad/pad-9 — unverified
Pad 10 pad-10 pad Note · velocity 10 45 · A2 midi/smcpad/pad-10 — unverified
Pad 11 pad-11 pad Note · velocity 10 46 · A#2 midi/smcpad/pad-11 — unverified
Pad 12 pad-12 pad Note · velocity 10 47 · B2 midi/smcpad/pad-12 — unverified
Pad 13 pad-13 pad Note · velocity 10 48 · C3 midi/smcpad/pad-13 — unverified
Pad 14 pad-14 pad Note · velocity 10 49 · C#3 midi/smcpad/pad-14 — unverified
Pad 15 pad-15 pad Note · velocity 10 50 · D3 midi/smcpad/pad-15 — unverified
Pad 16 pad-16 pad Note · velocity 10 51 · D#3 midi/smcpad/pad-16 — unverified
Pad 1 (bank B) pad-1-bank-b pad Note · velocity 10 52 · E3 midi/smcpad/pad-1-bank-b — unverified
Pad 2 (bank B) pad-2-bank-b pad Note · velocity 10 53 · F3 midi/smcpad/pad-2-bank-b — unverified
Pad 3 (bank B) pad-3-bank-b pad Note · velocity 10 54 · F#3 midi/smcpad/pad-3-bank-b — unverified
Pad 4 (bank B) pad-4-bank-b pad Note · velocity 10 55 · G3 midi/smcpad/pad-4-bank-b — unverified
Pad 5 (bank B) pad-5-bank-b pad Note · velocity 10 56 · G#3 midi/smcpad/pad-5-bank-b — unverified
Pad 6 (bank B) pad-6-bank-b pad Note · velocity 10 57 · A3 midi/smcpad/pad-6-bank-b — unverified
Pad 7 (bank B) pad-7-bank-b pad Note · velocity 10 58 · A#3 midi/smcpad/pad-7-bank-b — unverified
Pad 8 (bank B) pad-8-bank-b pad Note · velocity 10 59 · B3 midi/smcpad/pad-8-bank-b — unverified
Pad 9 (bank B) pad-9-bank-b pad Note · velocity 10 60 · C4 midi/smcpad/pad-9-bank-b — unverified
Pad 10 (bank B) pad-10-bank-b pad Note · velocity 10 61 · C#4 midi/smcpad/pad-10-bank-b — unverified
Pad 11 (bank B) pad-11-bank-b pad Note · velocity 10 62 · D4 midi/smcpad/pad-11-bank-b — unverified
Pad 12 (bank B) pad-12-bank-b pad Note · velocity 10 63 · D#4 midi/smcpad/pad-12-bank-b — unverified
Pad 13 (bank B) pad-13-bank-b pad Note · velocity 10 64 · E4 midi/smcpad/pad-13-bank-b — unverified
Pad 14 (bank B) pad-14-bank-b pad Note · velocity 10 65 · F4 midi/smcpad/pad-14-bank-b — unverified
Pad 15 (bank B) pad-15-bank-b pad Note · velocity 10 66 · F#4 midi/smcpad/pad-15-bank-b — unverified
Pad 16 (bank B) pad-16-bank-b pad Note · velocity 10 67 · G4 midi/smcpad/pad-16-bank-b — unverified

Have this unit? It takes a few minutes to check this data. Verify M-VAVE SMC-PAD 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/M-VAVE-SMC-PAD.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
/^smc[\s-]*pad(\s+(midi|port))*(\s+\d+)?$/i

Signals

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

Use it

Use M-VAVE SMC-PAD 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="m-vave-smc-pad" 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=m-vave-smc-pad&readout"
            width="720" height="472" style="border:0;max-width:100%" allow="midi"
            title="M-VAVE SMC-PAD"></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="m-vave-smc-pad" 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=m-vave-smc-pad to make the on-screen controller this one; a real M-VAVE SMC-PAD is recognised by its port name.

javascript
document.head.prepend(Object.assign(document.createElement('script'), { src: 'https://openaudiovisual.com/p5/oav-p5.js?profile=m-vave-smc-pad' }));
In your sketchControlMessage
knob1Knob 1 knob-1CC 30 · Ch 1
knob2Knob 2 knob-2CC 31 · Ch 1
knob3Knob 3 knob-3CC 32 · Ch 1
knob4Knob 4 knob-4CC 33 · Ch 1
knob5Knob 5 knob-5CC 34 · Ch 1
knob6Knob 6 knob-6CC 35 · Ch 1
knob7Knob 7 knob-7CC 36 · Ch 1
knob8Knob 8 knob-8CC 37 · Ch 1
pad1Pad 1 pad-1Note 36 · C2 · Ch 10
pad2Pad 2 pad-2Note 37 · C#2 · Ch 10
pad3Pad 3 pad-3Note 38 · D2 · Ch 10
pad4Pad 4 pad-4Note 39 · D#2 · Ch 10
pad5Pad 5 pad-5Note 40 · E2 · Ch 10
pad6Pad 6 pad-6Note 41 · F2 · Ch 10
pad7Pad 7 pad-7Note 42 · F#2 · Ch 10
pad8Pad 8 pad-8Note 43 · G2 · Ch 10
pad9Pad 9 pad-9Note 44 · G#2 · Ch 10
pad10Pad 10 pad-10Note 45 · A2 · Ch 10
pad11Pad 11 pad-11Note 46 · A#2 · Ch 10
pad12Pad 12 pad-12Note 47 · B2 · Ch 10
pad13Pad 13 pad-13Note 48 · C3 · Ch 10
pad14Pad 14 pad-14Note 49 · C#3 · Ch 10
pad15Pad 15 pad-15Note 50 · D3 · Ch 10
pad16Pad 16 pad-16Note 51 · D#3 · Ch 10
… and 16 more, up to pad(32), in the same order
p5.js sketch
function draw() {
  background(knob1 * 255);   // Knob 1 · CC 30
  circle(width / 2, height / 2, 50 + knob2 * 300);   // Knob 2 · CC 31
}

function padPressed(n, velocity) {      // n = 1…32, as in the table
  circle(random(width), random(height), velocity * 100);
}

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.