Hi all! Can anyone think of a way I could give a Musician footswitch control of the Play button on Ableset being controlled by a browser on a Tablet. Tablet would be connected to the playback network via WiFi. This would be the hardware button connecting via the Tablet (maybe bluetooth) - not a separate WIDI or RTP MIDI path back to the Playback computers.
@njrsound you might like the new AbleSet Connect app, which allows you to connect MIDI controllers to your iPad via USB and use AbleSetās MIDI mapping features over WiFi or Ethernet.
Itās still in beta, but you can give it a try if you like: AbleSet 3.1.0-beta.16
Let me know if that works for you 
1 Like
Iāve got an airturn that is bluetoothed to my main ableton/ableset machine and changes everything, works really well, and just mimics keyboard input on the computer. But we donāt have a failover setup
Hi Leo, Iāve downloaded Beta 16 and test flight Ableset Connect to my (rather old) iPhone 12m on iOS 26.5. Most normal functions of Ableset Connect are working fine, as are things like sending a cue light. Unfortunately even though I have Midi Forwarding turned on and it shows āconnected to , when I open Settings: Edit MIDI Mapping: add new mapping from any MIDI device, it doesnāt detect incoming MIDI. I have a teensy-based MIDI Note sender button connected to my iPhone via a Lightning Camera Connection Kit adapter, and if I use Midi Scope app on the iPhone, itās seeing the MIDI Note messages from the teensy coming into the iPhone OK. Is there any steo Iām missing? Cheers, nick
Hey @njrsound, thatās an interesting observation, thank you for reporting this! Does it work when you add a mapping for the specific device you connected to your iPhone?
no, the specific device isnāt showing up as a device in the MIDI Mapping settings either. I have now tried two MIDI Devices, the Teensy and a Korg Nano Key, both of which show up OK in MIDI Scope on the iPhone.
by the way - Iād be very interested in the Ableset Connect concept being available as a MacOS app as well that could run on a MacBook Neo or Mac Mini on stage, with the MIDI Forwarding feature that could work over a wired network connection.
Hey @njrsound, thatās strange. Could you send me a log package of AbleSet on the computer youāre connecting to so I can take a closer look?
Regarding running this on macOS, the app will also be available on the macOS App Store on Apple Silicon Macs so you can run it there as well. Alternatively, you can set up an RTP MIDI connection natively on macOS to route MIDI from connected controllers to your main computer.
Hi Leo,
Tried to send the log package to you (support@ableset.app) but Microsoft Exchange rejected the message several times saying it presented a potential security issue! I canāt seem to upload it direct to this forum either. Iāve sent it via Wetransfer instead.
Good to hear youāll be enabling the app on the MacOS App Store. I personally donāt use Macās internal RTP MIDI (network MIDI) through Audio MIDI setup on shows as I find it unreliable to re-establish connections from day to day. I use RTP MIDI in my Playback rigs, but only with hardware like iConnectivity or DoReMidi.
Cheers,
nick
Hey @njrsound, thanks for the log package! It seems like AbleSet Connect never actually connects to the MIDI server of AbleSet. Could you send me a screen recording of what it looks like in the app?
Are you letting AbleSet Connect automatically detect AbleSet or are you connecting manually? Does switching to the other method of connecting help?
Iām looking forward to your reply!
Hi Leo, Iāve sent you the screen recording and a new log file to match via Wetransfer. Ableset Connect automatically finds Ableset on the playback computer, and on-screen buttons work fine, just not passing on external MIDI device attached to phone. Thanks for looking into this!
Hey @njrsound, thank you for the log package and the video!
Could you check if the āNative MIDI Forwardingā option is enabled in AbleSetās MIDI Forwarding settings? You can also turn on āRTP MIDI Forwardingā temporarily to see a list of all MIDI devices that AbleSet has detected.
I hope this helps and look forward to your reply!
Hi Leo, yes - Native MIDI forwarding was on in the settings page as seen from the Ableset Connect app. When I turned on RTP MIDI Forwarding - Ableset Connect could indeed see the Teensy controller (which came up as āPort 1ā) and forward it to the Mac Mini and on to Ableset to be mapped. So the issue is only in the Native MIDI Forwarding option. If I were to use the RTP option, how does that work with AbleNet redundancy?
Hey @njrsound, I just released a new AbleSet 3.1.0-beta.17 and AbleSet Connect. This doesnāt change anything with the way connections are handled, but Iāve added a new page for troubleshooting. If you go to Settings ā MIDI Forwarding ā Connection Diagnostics, you should see a list of connections and their state, along with any potential connection errors.
You can use the copy button on the bottom right of that page to copy this text to the clipboard and then paste it here so I can take a closer look at it.
Iām looking forward to your reply!
Hi Leo,
Here it is:
{
āsocketā: {
āconnectionsā: [
{
āstateā: āconnectingā,
āconnectionErrorsā: ,
ācomputerNameā: āOffice Mac miniā,
āurlā: āhttp://office-mac-mini.local:80/ā
}
]
},
ārtpā: {
āconnectionsā: ,
āavailableSessionsā: ,
ādroppedSessionsā: ,
āhardwarePortsā: {
āinputsā: [
āPort 1ā
],
āoutputsā: [
āPort 1ā
]
},
ālocalNameā: āSession 1ā,
ānetworkNameā: āNicks 12mā,
āsessionEnabledā: false
}
}
Cheers, nick
Hey @njrsound, thank you for the debug info!
It seems that for some reason, the app never manages to actually connect to the server and gets stuck. I released a new beta version on TestFlight which adds even more debug logging around this to hopefully get to the bottom of this issue.
Could you try using the latest beta and send me the connection diagnostics again?
Iām looking forward to your reply!