Worlde
Worlde Easypad.12
Worlde Easypad.12 is a MIDI hardware controller by Worlde: 12 pads, 1 fader and 8 buttons.
It sends CC and Note on channel 10. The profile cites 1 source. 21 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
- 21 unverified
- Kind
- hardware device
- Maker
- Worlde
- Controls
- 21 controls
- Messages
- CC · Note
- MIDI channels
- 10
- LED feedback
- none sent
- Layout
- generated automatically
- Data licence
- Apache-2.0, from QLC+ (NOTICE)
- Checked on hardware
- not yet
- Signals
midi/easypad12/…- Port name matches
/^(worlde\s+)?easy\s*pad(\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 Easypad.12 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 |
|---|---|---|---|---|---|---|---|
XY Fader xy-fader |
fader | CC | 10 | 9 | midi/easypad12/xy-fader |
— | unverified |
Record record |
button | CC · momentary | 10 | 44 | midi/easypad12/record |
— | unverified |
Play play |
button | CC · momentary | 10 | 45 | midi/easypad12/play |
— | unverified |
Stop stop |
button | CC · momentary | 10 | 46 | midi/easypad12/stop |
— | unverified |
Back back |
button | CC · momentary | 10 | 47 | midi/easypad12/back |
— | unverified |
Next next |
button | CC · momentary | 10 | 48 | midi/easypad12/next |
— | unverified |
Refresh refresh |
button | CC · momentary | 10 | 49 | midi/easypad12/refresh |
— | unverified |
Left left |
button | Note · momentary | 10 | 1 · C#-1 | midi/easypad12/left |
— | unverified |
Right right |
button | Note · momentary | 10 | 2 · D-1 | midi/easypad12/right |
— | unverified |
Pad 7 pad-7 |
pad | Note · velocity | 10 | 36 · C2 | midi/easypad12/pad-7 |
— | unverified |
Pad 8 pad-8 |
pad | Note · velocity | 10 | 38 · D2 | midi/easypad12/pad-8 |
— | unverified |
Pad 1 pad-1 |
pad | Note · velocity | 10 | 39 · D#2 | midi/easypad12/pad-1 |
— | unverified |
Pad 9 pad-9 |
pad | Note · velocity | 10 | 40 · E2 | midi/easypad12/pad-9 |
— | unverified |
Pad 10 pad-10 |
pad | Note · velocity | 10 | 42 · F#2 | midi/easypad12/pad-10 |
— | unverified |
Pad 4 pad-4 |
pad | Note · velocity | 10 | 43 · G2 | midi/easypad12/pad-4 |
— | unverified |
Pad 11 pad-11 |
pad | Note · velocity | 10 | 44 · G#2 | midi/easypad12/pad-11 |
— | unverified |
Pad 3 pad-3 |
pad | Note · velocity | 10 | 45 · A2 | midi/easypad12/pad-3 |
— | unverified |
Pad 12 pad-12 |
pad | Note · velocity | 10 | 46 · A#2 | midi/easypad12/pad-12 |
— | unverified |
Pad 2 pad-2 |
pad | Note · velocity | 10 | 48 · C3 | midi/easypad12/pad-2 |
— | unverified |
Pad 6 pad-6 |
pad | Note · velocity | 10 | 49 · C#3 | midi/easypad12/pad-6 |
— | unverified |
Pad 5 pad-5 |
pad | Note · velocity | 10 | 51 · D#3 | midi/easypad12/pad-5 |
— | unverified |
Have this unit? It takes a few minutes to check this data. Verify Worlde Easypad.12 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-Easypad.12.qxi (non-official)community profile by Christoph Müllner; 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-Easypad.12.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.
Port names it recognises
- matches
/^(worlde\s+)?easy\s*pad(\s+(midi|port))*(\s+\d+)?$/i
Signals
Every control publishes midi/easypad12/<control> (0..1), plus /raw; pads add /hit, encoders /delta, keys /on /off and n<note>; the last control touched is midi/easypad12/last.
Use it
Use Worlde Easypad.12 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-easypad-12" 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-easypad-12&readout" width="720" height="393" style="border:0;max-width:100%" allow="midi" title="Worlde Easypad.12"></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-easypad-12" 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-easypad-12 to make the on-screen controller this one; a real Worlde Easypad.12 is recognised by its port name.
document.head.prepend(Object.assign(document.createElement('script'), { src: 'https://openaudiovisual.com/p5/oav-p5.js?profile=worlde-easypad-12' }));| In your sketch | Control | Message |
|---|---|---|
fader1 | XY Fader xy-fader | CC 9 · Ch 10 |
pad1 | Pad 7 pad-7 | Note 36 · C2 · Ch 10 |
pad2 | Pad 8 pad-8 | Note 38 · D2 · Ch 10 |
pad3 | Pad 1 pad-1 | Note 39 · D#2 · Ch 10 |
pad4 | Pad 9 pad-9 | Note 40 · E2 · Ch 10 |
pad5 | Pad 10 pad-10 | Note 42 · F#2 · Ch 10 |
pad6 | Pad 4 pad-4 | Note 43 · G2 · Ch 10 |
pad7 | Pad 11 pad-11 | Note 44 · G#2 · Ch 10 |
pad8 | Pad 3 pad-3 | Note 45 · A2 · Ch 10 |
pad9 | Pad 12 pad-12 | Note 46 · A#2 · Ch 10 |
pad10 | Pad 2 pad-2 | Note 48 · C3 · Ch 10 |
pad11 | Pad 6 pad-6 | Note 49 · C#3 · Ch 10 |
pad12 | Pad 5 pad-5 | Note 51 · D#3 · Ch 10 |
function draw() {
background(fader1 * 255); // XY Fader · CC 9
}
function padPressed(n, velocity) { // n = 1…12, 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).
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.