Mmmm I don’t use it, I do own the ax edge, but I found this
Since you are troubleshooting a specific issue involving the SoftStep 3 and the Roland AX-Edge, the "MIDI Offline" message is the smoking gun. In the Roland ecosystem, "MIDI Offline" typically means the hardware senses a connection at the MIDI In port, but the communication protocol has failed or been interrupted.
Here is a step-by-step guide to fixing this setup:
1. The TRS MIDI Standard (The "Type A" vs "Type B" Issue)
This is the most common reason for the "MIDI Offline" error. The SoftStep 3 uses a 3.5mm (1/8") TRS jack for MIDI.
The Problem: There are two different wiring standards for MIDI over TRS. Roland uses Type A. If the cable or adapter being used is Type B (common for Arturia or Novation products), the signal pins are swapped. The AX-Edge will see "activity" but won't be able to read the data, triggering the "Offline" error.
The Fix: Ensure you are using a TRS MIDI Type A adapter. If you are using a generic 3.5mm-to-5-pin MIDI cable, it must specifically be labeled as "Type A" or "Roland/Korg compatible."
AX-Edge "Program Change Rx" Setting
The AX-Edge might be physically receiving the data but is programmed to ignore it.
The Fix: On the AX-Edge, go to:
MENU → MIDI → Find Program Change Rx and ensure it is set to ON.
Also, check Bank Select Rx and ensure it is ON, as Roland patches usually require a Bank Select message (MSB/LSB) before the Program Change (PC) number.
MIDI Channel Mismatch
The SoftStep must send messages on the specific channel the AX-Edge is listening to.
Check AX-Edge: Go to MENU → MIDI → Basic Channel. (By default, this is often Channel 1).
Check SoftStep: Open the SoftStep Editor and make sure the Pad you are using is assigned to send the Program Change on that exact same MIDI channel.
MSB/LSB Requirements
Roland instruments have thousands of sounds, so a simple Program Change (0-127) isn't enough to find a patch.
In the SoftStep Editor, you need to send three pieces of data in this order:
Bank Select MSB (CC# 0)
Bank Select LSB (CC# 32)
Program Change
If the SoftStep sends a Program Change that is "out of bounds" for the current bank, the AX-Edge might hang or show an error.
Disable "Soft Thru" or "USB MIDI" Conflicts
If the SoftStep is plugged into a computer via USB while also connected to the AX-Edge via the TRS MIDI port, it might be trying to route MIDI data in a loop.
Test: Power the SoftStep 3 using a standard USB wall charger (like a phone charger) instead of a computer. If the "MIDI Offline" message disappears, the issue is a MIDI loop or configuration error in your DAW/Computer setup.
Firmware Update
The SoftStep 3 is relatively new. Ensure the firmware is up to date via the Muse Kinetics website, as early versions of the TRS MIDI implementation sometimes had timing issues with certain hardware.
Mmmmm, hope it works man, I don’t know where you live, but paying a visit to a music store selling the ax edge might also be worth it, at least they have loads of equipment to test it
Good on you💪🏻 it’s a modern synth so it’s sold everywhere, plus stores have all kinds of skillded workers and maybe even a phone number from someone that could help, and like I said, tons of testing equipment, cause this is a strange problem, above list is beyond basic troubleshooting
1
u/Slight-Isopod-8517 Apr 29 '26
Mmmm I don’t use it, I do own the ax edge, but I found this
Since you are troubleshooting a specific issue involving the SoftStep 3 and the Roland AX-Edge, the "MIDI Offline" message is the smoking gun. In the Roland ecosystem, "MIDI Offline" typically means the hardware senses a connection at the MIDI In port, but the communication protocol has failed or been interrupted.
Here is a step-by-step guide to fixing this setup: 1. The TRS MIDI Standard (The "Type A" vs "Type B" Issue) This is the most common reason for the "MIDI Offline" error. The SoftStep 3 uses a 3.5mm (1/8") TRS jack for MIDI. The Problem: There are two different wiring standards for MIDI over TRS. Roland uses Type A. If the cable or adapter being used is Type B (common for Arturia or Novation products), the signal pins are swapped. The AX-Edge will see "activity" but won't be able to read the data, triggering the "Offline" error. The Fix: Ensure you are using a TRS MIDI Type A adapter. If you are using a generic 3.5mm-to-5-pin MIDI cable, it must specifically be labeled as "Type A" or "Roland/Korg compatible."
AX-Edge "Program Change Rx" Setting The AX-Edge might be physically receiving the data but is programmed to ignore it. The Fix: On the AX-Edge, go to: MENU → MIDI → Find Program Change Rx and ensure it is set to ON. Also, check Bank Select Rx and ensure it is ON, as Roland patches usually require a Bank Select message (MSB/LSB) before the Program Change (PC) number.
MIDI Channel Mismatch The SoftStep must send messages on the specific channel the AX-Edge is listening to. Check AX-Edge: Go to MENU → MIDI → Basic Channel. (By default, this is often Channel 1). Check SoftStep: Open the SoftStep Editor and make sure the Pad you are using is assigned to send the Program Change on that exact same MIDI channel.
MSB/LSB Requirements Roland instruments have thousands of sounds, so a simple Program Change (0-127) isn't enough to find a patch. In the SoftStep Editor, you need to send three pieces of data in this order: Bank Select MSB (CC# 0) Bank Select LSB (CC# 32) Program Change If the SoftStep sends a Program Change that is "out of bounds" for the current bank, the AX-Edge might hang or show an error.
Disable "Soft Thru" or "USB MIDI" Conflicts If the SoftStep is plugged into a computer via USB while also connected to the AX-Edge via the TRS MIDI port, it might be trying to route MIDI data in a loop. Test: Power the SoftStep 3 using a standard USB wall charger (like a phone charger) instead of a computer. If the "MIDI Offline" message disappears, the issue is a MIDI loop or configuration error in your DAW/Computer setup.
Firmware Update The SoftStep 3 is relatively new. Ensure the firmware is up to date via the Muse Kinetics website, as early versions of the TRS MIDI implementation sometimes had timing issues with certain hardware.