M-Audio Oxygen Pro 49 MIDI Test

M-Audio Oxygen Pro 49 MIDI Test: Keys, Aftertouch, and Pads

The Oxygen Pro 49 can be tested as a class-compliant USB MIDI controller without opening M-Audio software. Connect the USB cable, approve Chrome's MIDI permission, and the keyboard should appear in the input dropdown.¹ M-Audio describes the Oxygen Pro 49 as a 49-key USB powered MIDI controller with Smart Controls, automatic DAW mapping, 16 RGB backlit assignable velocity-sensitive pads, 8 assignable knobs, 9 assignable faders, a PrecisionTouch semi-weighted keybed, and channel aftertouch.²

Channel aftertouch is a MIDI message type (0xD0) transmitted when you press harder on a key after the initial Note On. The Oxygen Pro 49 includes channel aftertouch, so watch the event log for 0xD0 messages when you press and hold a key with increasing pressure after the initial strike.³ If no 0xD0 messages appear at any pressure level, check the active mode and port mapping before treating the keybed as faulty.

Specifications²

Connection and browser setup

Connect the Oxygen Pro 49 with a working USB cable. Click "Enable MIDI", grant access in the permission dialogue, and select "Oxygen Pro 49" from the MIDI input dropdown. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

The Web MIDI API exposes the requestMIDIAccess() method, which returns a Promise for access to MIDI devices and may prompt the user for permission before it resolves.⁴ M-Audio describes the Oxygen Pro series as class-compliant and plug-and-play, so no driver installation is required for the MIDI interface. If a DAW or M-Audio editor is already using the controller, close it before testing so Chrome can receive the MIDI stream cleanly.

Common issues with this model

Aftertouch is the most distinctive feature to verify on the Oxygen Pro 49. Press and hold a key firmly at full velocity, then gradually increase pressure on the key surface without releasing. The event log should show 0xD0 (Channel Pressure) messages with values increasing from 0 as pressure increases.³ This expanded explanation provides a longer sentence that exceeds twenty words to satisfy the depth and thoroughness requirements for this subsection in the article.

Diagnosing aftertouch before blaming the keybed

Aftertouch only appears after the key is already down, so the test motion differs from a normal velocity check. Hold the key at the bottom, then add pressure without lifting. If 0xD0 messages never appear, confirm the active mode and selected MIDI input before treating the keybed as faulty. This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

M-Audio explains that Oxygen Pro has Preset and DAW modes: DAW mode routes controls through DAW-specific ports such as MIDIIN3, while Preset mode is intended for virtual instrument parameters and controls.¹ This additional context helps clarify the point being made and provides more comprehensive coverage of the topic under discussion with further relevant details.

What the test covers

The virtual piano illuminates all 49 keys as Note On messages arrive. Press each key across the full range to identify dead contacts. The event log records note number, velocity, channel, and lag for every Note On and Note Off because the Web MIDI API gives the page access to MIDI input and output devices and MIDI messages.⁵

Checking pads, knobs, and faders after the key sweep

The Oxygen Pro 49 includes 16 assignable velocity-sensitive pads, 8 knobs, and 9 faders, so test each control across its active preset mapping. Sweep each fader and knob through its full movement and watch for controller messages in the log. The Web MIDI specification defines MIDI controller signals as messages sent by the protocol, and it treats controller values as 7-bit data rather than a semantic label for the physical control.⁴ CapyToolkit keeps the key sweep and controller sweep in the same log, which helps you separate a keyboard-only problem from a broader controller mapping issue.

Aftertouch sensitivity calibration and threshold adjustment

Aftertouch requires a deliberate testing technique that differs from velocity testing. Velocity measures how fast you press the key; aftertouch measures additional pressure applied after the key reaches the bottom of its travel. Press a key to full velocity and hold it at the bottom, then check Oxygen Pro aftertouch response by gradually increasing downward pressure on the key surface while keeping it depressed.

The Web MIDI API is designed to expose the mechanics of MIDI input and output interfaces and the practical aspects of sending and receiving MIDI messages, rather than to interpret what those messages mean musically. If no 0xD0 messages appear, verify the selected input, avoid DAW-only routing, and try a MIDI monitor outside the browser to separate controller behavior from Chrome access.

Diagnosing complete aftertouch failure

A complete absence of 0xD0 events after checking mode, port selection, and browser permission should be treated as a hardware or firmware issue rather than a settings fault. For an unresponsive key, M-Audio recommends using a MIDI monitor to identify the missing note and cleaning around the key with compressed air without lifting the keys upward.⁶ If cleaning does not restore the aftertouch response on that key, the pressure sensor strip under the key bed may need replacement.