What to check before taking a MIDI keyboard on stage

A MIDI keyboard can work perfectly at home and still cause trouble at a venue: a key misses notes, a pedal behaves backward, or the computer does not see the device. A quick check before load-in can catch these problems while there is time to change a cable or fix a setting.

Use the MIDI Test to check whether your keyboard sends key, velocity, pedal, and knob messages to the computer. Then test the full setup you will use on stage, because a browser test cannot confirm that your music software, instrument sounds, power supply, or venue audio connections are ready.

Test the keyboard before you pack

1. Open the MIDI Test in a browser that supports MIDI. Safari does not work with this test. Connect and power on the keyboard, then allow MIDI access if the browser asks.
2. If more than one MIDI device is listed, choose the keyboard you plan to take. Press every key across the range you expect to use, including keys at the far ends. Check that each press registers and that releasing a key stops its note message.
3. Play the same key softly and firmly. The test should show changing velocity values, which represent how gently or hard you pressed. Try a few chords as well as single notes.
4. Move each knob, wheel, slider, or other control you rely on. Press the sustain pedal and any other pedals, and check that the test receives their messages. Repeat while using the actual cable and adapter you plan to bring.

For a keyboard with its own sounds, also play it through its headphone output or built-in speakers if it has them. That checks the keyboard's audio path, which is separate from the MIDI messages the browser receives.

What the test result means

Every key and control sends messages

The keyboard is communicating with the computer over MIDI, and the tested controls are registering. This does not prove the music software has selected the keyboard or that the software will send sound to the stage speakers. Open the software you will perform with and test a real instrument sound, sustain, and any custom mappings there.

Some keys do not register

If the same keys fail repeatedly in the test, the issue may be in the keyboard, its connection, or a setting that changes how it sends notes. Test those keys again after reconnecting. If the problem follows the keyboard to another computer, do not assume a stage setup will fix it. For more troubleshooting, see MIDI keyboard not sending notes: how to test it.

Keys work, but velocity barely changes

The keyboard is sending notes, but the velocity response may be limited by its settings, a velocity curve, or the way you are pressing the keys. Check the keyboard's own velocity settings and test with a range of pressure. If you use a fixed-velocity mode intentionally, confirm that your instrument software responds as expected.

The pedal or a knob sends the wrong behavior

A pedal that sends a message is not necessarily configured the way your instrument expects. A sustain pedal may act backward because of its polarity setting or because it was connected while held down. Check it in the music software too, and see Why a sustain pedal acts backward when plugged in.

The device is missing or nothing arrives

The browser may not have MIDI access, the keyboard may be off, or the cable may not carry data. Some USB cables provide power only. If the keyboard is visible to the browser but the wrong device is selected, choose the correct input and test again.

Fix problems before the show

1. Check the power and connection. Confirm the keyboard is on and its power adapter is secure. Disconnect and reconnect the MIDI or USB cable at both ends. Use a cable known to carry data, not just charge.
2. Try a direct USB port. Connect the keyboard straight to the computer instead of through a hub or dock. If you need an adapter on stage, test with that exact adapter and cable before leaving.
3. Choose the right MIDI input. In the browser test and your music software, select the keyboard rather than another controller or virtual input. In the performance software, make sure the track or instrument is set to receive from that input. Menu names vary by app.
4. Check whether the computer sees it. In Windows 11, right-click Start and open Device Manager. Look for the keyboard or MIDI interface in the device list, noting that its category and name vary. On a Mac, open Applications › Utilities › Audio MIDI Setup and inspect MIDI Studio. If it does not appear, reconnect it or try another data cable and port.
5. Check the browser's MIDI permission. If access was denied, open the browser's site permissions for the page and allow MIDI device access, then reload the test. A browser that does not support MIDI cannot use this test, so try a compatible browser before deciding the keyboard is faulty.
6. Restart the software and retest. Close other music apps that may be using the device, reopen the test or performance software, and check the input again. Test the actual instrument sound and output after the MIDI connection works.

When the keyboard or cable may be faulty

Repeat the test with another data cable and another computer if you can. If the same keys or controls fail on both computers, while other parts of the keyboard work, the fault is more likely in the keyboard. If the device disappears when you move the connector, suspect a loose port or cable. Replace a low-cost cable first; for a damaged keyboard port or consistently failing keys, contact the manufacturer or a repair shop rather than relying on it for a performance.

Do a full stage rehearsal

Before the event, connect the keyboard to the same computer, software, power source, audio interface, and output path you expect to use. Play a short passage, test sustain during it, turn your mapped controls, and confirm the sound reaches the correct outputs. Pack a spare data cable and any required adapter, and keep a backup way to play if the keyboard is essential to the set.

The MIDI Test checks messages in your browser. It does not play or upload your performance, and it cannot verify the sound system at the venue.