Add MIDI input messages for the 4 main footswitches.
Current MIDI implementation has unique MIDI values for many many functions which is nice in many ways and super flexible… BUT I simply want a remote version of the footswitches. I’m using an AIRSTEP midi controller with 5 footswitches. There is no way to simply map the footswitches my controller to the 4 footswitches on the Aeros. I can map specific functions but the footswitch functions are very context dependent so doesn’t come close to replicating their functionality.
This would be nice, and I’ve seen it requested before a few times in comments. You’d need separate messages for short and long presses, because MIDI messages are ‘momentary’ or durationless. The Airstep could handle this though because it can send different messages depending on press duration.
Thanks, yes agreed! It could also be based on press and release messages. Set the midi controller to send value 127 when pressed and 0 when released. Aeros then can assume if it receives 127 and not 0 within X seconds, it’s a long press.
It’s exactly the same as the original post, being able to replicate via midi the physical aeros buttons (whose functions change of course , arm is a good example) the original poster launched a feature request and i am wondering if it ever happened and if so how it works? I am on 5.4.5
Forgot to say, my goal is to have the aeros at eye level (on a mic stand) so i can operate by foot with minimal distraction . It’s a great looper but for playing live it’s a real pain in the neck (literally)
The footswitches change behavior based on context. It’s impossible to replicate this with a remote midi footswitch. Please provide a midi based way to to do this. The midi message would tell the firmware it should react as though a physical button was pressed. i.e. Take into account current context and invoke the proper function.
The context-dependent behavior is the core issue here, and I think the proposal addresses it well. Sending a message that simply tells the firmware “act as if the physical button was pressed” would let the current state decide the function, instead of forcing users to map every possible action to a separate MIDI note. That seems far more maintainable than duplicating the logic externally. Keeping the Aeros at eye level while still operating it by foot is a sensible goal too, so a context-aware MIDI trigger would solve both problems at once. Hoping the dev team considers it in the merged request.