MIDI channel assignment on a shared classroom PC

A keyboard works in one music app but plays the wrong instrument in another, or several controllers seem to affect the same track. On a shared classroom PC, the cause may be a MIDI channel mismatch, an input selection, or a setting left behind by the last user.

MIDI channels are numbered 1 to 16. A controller sends notes and other messages on a channel, and receiving software can listen to one channel or several. Use the MIDI Test to see the messages a keyboard sends before changing settings in a music app.

Check a keyboard's MIDI channel

1. Open the MIDI Test in a browser that supports MIDI. The tool does not work in Safari. Connect one keyboard or controller to the PC at a time so you can tell which device is sending messages.
2. If the browser asks to access MIDI devices, allow access. Keep the music app closed for this first check, so another program is less likely to interfere with the test.
3. Press a few keys, then try a knob or pedal if the controller has one. Watch for incoming messages and note the channel number shown for each message.
4. Repeat with each controller. Write down the device name and the channel it sends on before changing anything. If you use a shared sign-in, don't save a new preset over someone else's setup.

A channel belongs to the message, not permanently to the computer. The MIDI Test shows what arrives at the browser, but it does not show which channel a track in a separate music app is set to receive.

What the channel result means

The controller sends on the channel the app expects

The channel assignment is probably not the problem. Check that the music app is listening to the right controller or MIDI input, and that the track is armed or set to receive input. Some apps listen to all channels by default, while others filter for a specific one.

The controller sends on a different channel

The keyboard is sending MIDI, but software that listens only to another channel may ignore it or route it to a different part. For example, if the track listens on channel 2 and the controller sends on channel 1, they will not match unless the app accepts all channels or maps them.

Two controllers send on the same channel

That is not automatically a fault. A MIDI channel is not a unique ID for a physical keyboard. The receiving app may still distinguish controllers by their input ports, but a track listening to both ports and the same channel can receive notes from both. Select the intended input in the app before changing a controller's channel.

No messages appear

This does not prove that the channel is wrong. The controller may not be connected, the browser may not have MIDI access, or the browser may not support the needed MIDI feature. A channel mismatch usually means messages are visible, but their channel differs from the one the app expects.

Notes appear on more than one channel

Some controllers can transmit on multiple channels, or send different controls through separate channels. Check the keyboard's manual or its own display and settings before deciding this is unexpected. Channel 10 is a common convention for percussion, but software and devices can use other arrangements.

Fix a channel mismatch

1. Check the receiving track first. In the music app, find the track's MIDI input or channel filter and compare it with the channel shown in the test. Choose the correct input device and channel, or use an all-channel option if that suits the setup. The exact menu names depend on the app.
2. Check the controller's transmit channel. Look at its display, onboard settings, or manual for the transmit channel. If you change it, record the original value first and change only the intended controller, not a shared software preset.
3. Reconnect one device at a time. Unplug and reconnect a USB controller, then check it again in the test. For Bluetooth MIDI, check the connection in Windows 11 under Settings › Bluetooth & devices › Devices, or on macOS under System Settings › Bluetooth. These Bluetooth menus do not set MIDI channels.
4. Check browser access. If the test cannot see a controller, use the browser's site information or permissions menu to review MIDI access, then reload the page. Permission controls vary by browser, and Safari does not work with the MIDI Test.
5. Restart the music app and retest. Some apps list MIDI inputs only when they start. Close and reopen the app after connecting a controller, then test the keyboard again in the app. If the input still fails, restart the PC and repeat the one-device-at-a-time check.

Keep a shared classroom setup predictable

Make a small inventory of each controller, its usual channel, and the app or track that uses it. Add the note near the device or in a classroom setup sheet, but avoid changing assignments just to make every keyboard's number different. Separate devices by input port when the app supports it, and use channels only when the software's routing needs them.

Before ending a session, restore any channel or track changes you made and disconnect your controller if another student will use the PC. The MIDI Test checks incoming MIDI messages in the browser; it does not rewrite a controller's stored settings.