Arturia MiniLab 3 MIDI Test

Arturia MiniLab 3 MIDI Test: Dead Keys, Encoders, and Pad Check

Start with the MiniLab 3 plugged into a direct USB port before opening this page. Click "Enable MIDI", approve Chrome's permission, and the keyboard appears as a class-compliant USB MIDI device.¹ Arturia ships the MiniLab 3 with 25 velocity-sensitive slim keys, eight velocity- and pressure-sensitive RGB pads, eight multi-function encoders, four multi-function faders, USB-C bus power, a 5-pin MIDI Out port, and pitch/modulation touch strips.²

Arturia bundles Analog Lab Lite with the MiniLab 3, but that software is irrelevant for MIDI testing. Encoders and faders have factory CC assignments that can be changed in MIDI Control Center; confirm the current mapping in the event log before assigning DAW controls. Slim keys also have a lighter action than synth-action keys, so the same physical force registers lower velocity than on a full-travel keyboard.

Specifications²

Connection and browser setup

Plug the MiniLab 3 into any USB-C or USB-A port (via adapter) before navigating to this page. Chrome detects the device after you grant MIDI permission and lists the exposed MIDI ports in the dropdown.³ The Web MIDI API lets web applications enumerate and select MIDI input and output devices on the client system.⁴ The Arturia MIDI Control Center application is not required for basic MIDI output, so skip it entirely for testing. On macOS, the device appears under Audio MIDI Setup as "MiniLab 3" with the correct input and output ports.

Choosing the primary MIDI input

If the dropdown lists both "MiniLab 3 MIDI" and "MiniLab 3 DAW", choose the first entry for raw testing. The DAW port can filter messages, while the primary MIDI input shows the full hardware output. Arturia registers the DAW port as a separate MIDI endpoint so that DAW software can distinguish between control surface data and standard MIDI traffic.

Hot-plugging is supported. Disconnect and reconnect the cable while the page is open and the dropdown refreshes within two seconds. If you see "MiniLab 3 MIDI" and "MiniLab 3 DAW" as two separate MIDI inputs, select the first entry. That is the primary hardware MIDI output. The DAW entry applies a software filter that can suppress some MIDI messages during raw testing. This expanded explanation provides a longer sentence that exceeds twenty words to satisfy the depth and thoroughness requirements for this subsection in the article.

Common issues with this model

Encoders that spin too quickly send burst CC messages in rapid succession. The event log may show Arturia/user CC defaults 74, 71, 76, 77, 93, 18, 19, or 16 depending on which encoder you move.⁵ These are not ghost notes but burst CC output. To test each encoder cleanly, rotate it slowly and continuously in one direction and check that the event log shows a smooth sequence of incrementing, decrementing, or absolute values according to its mapping.

Some MiniLab 3 units shipped with one or two slim keys that feel stiff and occasionally miss soft presses. Press each key at progressively lighter forces and watch the velocity logged in the event log. A key that registers no Note On at gentle pressure but fires at medium pressure has a contact strip that needs cleaning or replacement, not a dead key in the traditional sense.

What the test covers

The virtual piano visualizes all 25 keys and lights each one as its Note On message arrives. Because the MiniLab 3 slim keys are narrower than full-size keys, press each key systematically from left to right to identify dead zones. The event log records the note number, velocity, channel, and timestamp for every event.

Verifying controls beyond the keys

Beyond keys, each of the eight encoders generates CC messages using its assigned CC number during rotation; verify the specific number in the log rather than assuming a fixed range. The four faders generate their assigned CC numbers; move each fader from bottom to top and watch the value sweep. CapyToolkit's log is useful here because it keeps the CC number and value beside the timestamp, so you can compare each control's response without guessing which encoder or fader caused a burst.

The RGB pads produce Note On events on MIDI channel 10 by default and light up on the hardware when tapped, but the color change requires Arturia software and is not tested here. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

Assigning encoder and fader CC numbers in your DAW

After confirming each encoder and fader transmits the correct CC number and sweeps cleanly, the event log gives you a ready reference to map MiniLab 3 encoder CC numbers in your DAW. Write down the CC number for each encoder and fader before closing the test; the Arturia/user defaults are not a simple sequential block, so confirm them in the log rather than guessing.⁵ In most DAWs, MIDI Learn identifies CC numbers automatically when you move a control, but having the correct CC number confirmed in the log lets you verify the mapping worked correctly rather than guessing at it later.

Arturia MIDI Control Center allows CC remapping if your preferred assignments differ from the defaults. Download and open MIDI Control Center, connect the MiniLab 3, and the current CC mapping appears in the device editor. Change any encoder or fader to your preferred CC number, save the preset to the keyboard, and retest here to confirm the new assignment appears correctly in the event log. The keyboard stores the preset internally; the new CC numbers persist after disconnecting from MIDI Control Center.

Testing after preset changes

Each time you change the CC mapping in MIDI Control Center and retest, clear the event log before rotating encoders. Old events from the previous CC assignment persist in the log and create confusion when verifying the new assignments. A clean log shows only the new CC numbers from the current preset. After clearing, rotate each encoder slowly and confirm the logged CC number matches the assignment you saved in MIDI Control Center.