Generic layout
Generic 49-key keyboard
Generic 49-key keyboard is a generic layout, not a product: 49 keys, 1 button and 2 wheels. Its messages are conventions rather than one maker's chart. Pick it for a controller that is not in the library, press Learn and move your controls in order.
- Generic layout
- Kind
- generic layout
- Controls
- 52 controls
- Messages
- Pitch bend · CC · Note
- MIDI channels
- 1
- LED feedback
- none sent
- Signals
midi/keys49/…- Port name matches
- none: assign by hand, then learn
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 Generic 49-key keyboard 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.
| Control | Type | Message | Ch | Number | Signal | LED feedback | Verified |
|---|---|---|---|---|---|---|---|
Pitch pitch |
wheel | Pitch bend · springs to centre | 1 | 0–16383 · centre 8192 | midi/keys49/pitch |
— | yes |
Mod mod |
wheel | CC | 1 | 1 | midi/keys49/mod |
— | yes |
Sustain sustain |
button | CC · momentary | 1 | 64 | midi/keys49/sustain |
— | yes |
Keys keys |
keys | Note · velocity | 1 | 36–84 (C2–C6) | midi/keys49/keys/on · midi/keys49/keys/off · midi/keys49/n36…n84 |
— | yes |
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
- convention open-audiovisual generic layoutKeys 36–84 on channel 1 (C2–C6, scientific pitch: 60 = C4), pitch bend, mod wheel CC 1, sustain CC 64 — the General MIDI conventions every keyboard follows. Keys catch any note on their channel, so octave shifts on the hardware just scroll the on-screen keys.
Port names it recognises
Generic layouts never match a port by themselves: assign one by hand, then learn.
Signals
Every control publishes midi/keys49/<control> (0..1), plus /raw; pads add /hit, encoders /delta, keys /on /off and n<note>; the last control touched is midi/keys49/last.
Use it
Use Generic 49-key keyboard in your own work
Embed it with one line
No import map, no build step. Change
layout, addhardware="ask"for a Connect button.<script type="module" src="https://openaudiovisual.com/packages/midi/element.js"></script> <oav-controller profile="generic-keys49" readout></oav-controller>Or as an iframe
For places that only take an iframe. Every event arrives as a
postMessage.<iframe src="https://openaudiovisual.com/embed/controller/?profile=generic-keys49&readout" width="720" height="188" style="border:0;max-width:100%" allow="midi" title="Generic 49-key keyboard"></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>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.
<!-- 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="generic-keys49" 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 layout, the order of the table above. Add ?profile=generic-keys49 to make the on-screen controller this one.
document.head.prepend(Object.assign(document.createElement('script'), { src: 'https://openaudiovisual.com/p5/oav-p5.js?profile=generic-keys49' }));| In your sketch | Control | Message |
|---|---|---|
notePressed(note, velocity) | 36–84 (C2–C6) | a key goes down |
function draw() {
background(20);
}
function notePressed(note, velocity) { // a key goes down
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).
This is a generic layout. Its numbering applies when you choose it as the on-screen controller; an unknown real controller numbers its knobs in the order you turn them.
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.