Docs / MIDI

MIDI troubleshooting

Most MIDI problems come down to Songstead not seeing a device, or a trigger set up for a slightly different command than the device sends. The Monitor shows exactly what arrives and what goes out, so it's the place to start.

MIDI needs Backstage.

Requires Backstage

A device that shows as Connected isn't necessarily sending anything Songstead can hear. Many things can stop its commands on the way, in the device's own settings, the cable or connection, or the device you run Songstead on. When the Monitor shows nothing arriving from a connected device, the cause is almost always the device or the platform, not Songstead. See A device is connected but nothing arrives.

"This browser can't reach MIDI devices"

Safari, and every browser on iPhone and iPad, can't reach MIDI devices. Use the Songstead app, or Chrome, Edge or Firefox on a computer. See MIDI compatibility.

"MIDI access was blocked"

Songstead was refused permission to use MIDI devices. Allow MIDI for songstead.app in the browser's site settings, then reload Songstead.

"Waiting for MIDI access"

The browser is asking whether Songstead can use your MIDI devices. Look for its prompt, usually near the address bar, and allow it.

"This version of the app can't reach MIDI devices"

Update the Songstead app from the App Store or Google Play.

A device doesn't show up

  • Check that MIDI is turned on in Settings on the Setup tab. It's turned on separately on each device you use Songstead on.
  • Open the menu (the three dots) beside Devices and select Refresh Devices.
  • For a Bluetooth device on iPhone, iPad or Android, select Pair Bluetooth. On a computer, pair it in the computer's own settings first. See MIDI compatibility.
  • Another program may be holding the device. Close other music software and select Refresh Devices again.

A device is connected but nothing arrives

Press a switch or play a key and watch the Monitor. If no In row appears, the commands aren't reaching Songstead. Common causes:

  • The device's MIDI output is off, or sent elsewhere. Many devices choose in their own settings whether MIDI goes out over USB, the 5-pin port or Bluetooth, or not at all.
  • The device has more than one port. Some show up as two or three devices, and send their switches and keys on only one of them. Try each.
  • The cable only charges. Some USB cables carry power and no data. Try the cable the device came with.
  • The cables are crossed. On 5-pin MIDI, the device's MIDI Out goes to the interface's MIDI In.
  • Another program has the device. Close other music software, especially on Windows.
  • The Bluetooth connection has dropped while the device still shows. Turn the device off and on, and pair it again.

The device's manual, or its maker's support, is the best help with any of these. See MIDI compatibility for what each kind of connection and device can do.

The free MIDI Tester & Monitor checks a device with nothing from your Songstead setup involved. If nothing arrives there either, the cause is the device or its connection.

A trigger does nothing

  1. Open the Monitor tab and press the switch. If no In row appears, Songstead isn't hearing the device: see A device is connected but nothing arrives.
  2. If the row appears with a dash under Response, no trigger matched it. The trigger's kind, channel, number and device all have to match the row. Setting the command up again with Listen is the surest fix.
  3. If the Response shows the action but nothing changed, the action had nothing to act on there. The Live Mode actions only work in Live Mode, and the key, transpose, font size and annotation actions need a song open. See Actions.

A Control Change only sets a trigger off when its value goes to 64 or above. A switch that sends 0 when pressed and 127 when let go acts on release. Many footswitches have a setting to swap that.

A trigger shows in the warning color

The trigger's command can't do what the trigger asks. Open it, and its card says why:

MessageWhat to do
This command can't set anything off.Choose a Note On, Control Change, Program Change, Song Select, Start, Continue or Stop.
Held and Received twice need a command that's released.Use a note or a Control Change, or change the Event to Received.
Going to a song needs a Program Change or Song Select.Choose one of those two.
An inbound trigger listens for one command, and this saved command has more.Edit the saved command down to one command, or give the trigger a different command.

An outbound trigger for Song starts shows in the warning color when its song isn't chosen.

"Failed to send MIDI command to" a device

The command is set to go to that one device, and it isn't connected. Connect it, or change the command's To to another device or All devices. See Where commands go.

A device gets the wrong patch

Songstead counts programs from 0, and many devices count them from 1. Patch 1 on your device is usually Program 0 in Songstead. Using Listen while you pick the patch on the device gets it right every time.

A patch changes at the wrong moment in Live Mode

A song's commands go out when you move forward into the song, past the pause at the end of the song before. See When a song starts.

A note is stuck

Select Panic in the Monitor's menu (the three dots). It silences every device on every channel.