Worlde
Worlde Orca PAD16
Worlde Orca PAD16 is a MIDI hardware controller by Worlde: 16 pads and 6 knobs.
It sends CC and Note on channel 1. The profile cites 1 source. 22 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
- 22 unverified
- Kind
- hardware device
- Maker
- Worlde
- Controls
- 22 controls
- Messages
- CC · Note
- MIDI channels
- 1
- LED feedback
- none sent
- Layout
- generated automatically
- Data licence
- Apache-2.0, from QLC+ (NOTICE)
- Checked on hardware
- not yet
- Signals
midi/orcapad16/…- Port name matches
/^(worlde\s+)?orca\s*pad\s*16(\s+(midi|port))*(\s+\d+)?$/i
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 Worlde Orca PAD16 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 | Evidence |
|---|---|---|---|---|---|---|---|
R1 r1 |
knob | CC | 1 | 0 | midi/orcapad16/r1 |
— | unverified |
R2 r2 |
knob | CC | 1 | 1 | midi/orcapad16/r2 |
— | unverified |
R3 r3 |
knob | CC | 1 | 2 | midi/orcapad16/r3 |
— | unverified |
R4 r4 |
knob | CC | 1 | 3 | midi/orcapad16/r4 |
— | unverified |
R5 r5 |
knob | CC | 1 | 4 | midi/orcapad16/r5 |
— | unverified |
R6 r6 |
knob | CC | 1 | 5 | midi/orcapad16/r6 |
— | unverified |
PAD1 pad1 |
pad | Note · velocity | 1 | 60 · C4 | midi/orcapad16/pad1 |
— | unverified |
PAD2 pad2 |
pad | Note · velocity | 1 | 61 · C#4 | midi/orcapad16/pad2 |
— | unverified |
PAD3 pad3 |
pad | Note · velocity | 1 | 62 · D4 | midi/orcapad16/pad3 |
— | unverified |
PAD4 pad4 |
pad | Note · velocity | 1 | 63 · D#4 | midi/orcapad16/pad4 |
— | unverified |
PAD5 pad5 |
pad | Note · velocity | 1 | 64 · E4 | midi/orcapad16/pad5 |
— | unverified |
PAD6 pad6 |
pad | Note · velocity | 1 | 65 · F4 | midi/orcapad16/pad6 |
— | unverified |
PAD7 pad7 |
pad | Note · velocity | 1 | 66 · F#4 | midi/orcapad16/pad7 |
— | unverified |
PAD8 pad8 |
pad | Note · velocity | 1 | 67 · G4 | midi/orcapad16/pad8 |
— | unverified |
PAD9 pad9 |
pad | Note · velocity | 1 | 68 · G#4 | midi/orcapad16/pad9 |
— | unverified |
PAD10 pad10 |
pad | Note · velocity | 1 | 69 · A4 | midi/orcapad16/pad10 |
— | unverified |
PAD11 pad11 |
pad | Note · velocity | 1 | 70 · A#4 | midi/orcapad16/pad11 |
— | unverified |
PAD12 pad12 |
pad | Note · velocity | 1 | 71 · B4 | midi/orcapad16/pad12 |
— | unverified |
PAD13 pad13 |
pad | Note · velocity | 1 | 72 · C5 | midi/orcapad16/pad13 |
— | unverified |
PAD14 pad14 |
pad | Note · velocity | 1 | 73 · C#5 | midi/orcapad16/pad14 |
— | unverified |
PAD15 pad15 |
pad | Note · velocity | 1 | 74 · D5 | midi/orcapad16/pad15 |
— | unverified |
PAD16 pad16 |
pad | Note · velocity | 1 | 75 · D#5 | midi/orcapad16/pad16 |
— | unverified |
Have this unit? It takes a few minutes to check this data. Verify Worlde Orca PAD16 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
- community QLC+ input profile Worlde-OrcaPAD16.qxi (non-official)community profile by Massimo Callegari; Apache-2.0; numbers read from QLC+ channel numbers, not checked by this project
Where this profile comes from
Imported from QLC+ on 2026-11-04. resources/inputprofiles/Worlde-OrcaPAD16.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
/^(worlde\s+)?orca\s*pad\s*16(\s+(midi|port))*(\s+\d+)?$/i
Signals
Every control publishes midi/orcapad16/<control> (0..1), plus /raw; pads add /hit, encoders /delta, keys /on /off and n<note>; the last control touched is midi/orcapad16/last.
Use it
Use Worlde Orca PAD16 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="worlde-orca-pad16" 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=worlde-orca-pad16&readout" width="720" height="281" style="border:0;max-width:100%" allow="midi" title="Worlde Orca PAD16"></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="worlde-orca-pad16" 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=worlde-orca-pad16 to make the on-screen controller this one; a real Worlde Orca PAD16 is recognised by its port name.
document.head.prepend(Object.assign(document.createElement('script'), { src: 'https://openaudiovisual.com/p5/oav-p5.js?profile=worlde-orca-pad16' }));| In your sketch | Control | Message |
|---|---|---|
knob1 | R1 r1 | CC 0 · Ch 1 |
knob2 | R2 r2 | CC 1 · Ch 1 |
knob3 | R3 r3 | CC 2 · Ch 1 |
knob4 | R4 r4 | CC 3 · Ch 1 |
knob5 | R5 r5 | CC 4 · Ch 1 |
knob6 | R6 r6 | CC 5 · Ch 1 |
pad1 | PAD1 pad1 | Note 60 · C4 · Ch 1 |
pad2 | PAD2 pad2 | Note 61 · C#4 · Ch 1 |
pad3 | PAD3 pad3 | Note 62 · D4 · Ch 1 |
pad4 | PAD4 pad4 | Note 63 · D#4 · Ch 1 |
pad5 | PAD5 pad5 | Note 64 · E4 · Ch 1 |
pad6 | PAD6 pad6 | Note 65 · F4 · Ch 1 |
pad7 | PAD7 pad7 | Note 66 · F#4 · Ch 1 |
pad8 | PAD8 pad8 | Note 67 · G4 · Ch 1 |
pad9 | PAD9 pad9 | Note 68 · G#4 · Ch 1 |
pad10 | PAD10 pad10 | Note 69 · A4 · Ch 1 |
pad11 | PAD11 pad11 | Note 70 · A#4 · Ch 1 |
pad12 | PAD12 pad12 | Note 71 · B4 · Ch 1 |
pad13 | PAD13 pad13 | Note 72 · C5 · Ch 1 |
pad14 | PAD14 pad14 | Note 73 · C#5 · Ch 1 |
pad15 | PAD15 pad15 | Note 74 · D5 · Ch 1 |
pad16 | PAD16 pad16 | Note 75 · D#5 · Ch 1 |
function draw() {
background(knob1 * 255); // R1 · CC 0
circle(width / 2, height / 2, 50 + knob2 * 300); // R2 · CC 1
}
function padPressed(n, velocity) { // n = 1…16, as in the table
circle(random(width), random(height), velocity * 100);
}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+.
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.