sysex, pitch bend, program change
It’s been over a year and we still don’t have sysex… it’s part of MIDI… and really weird that I can’t use it
On my faderport 16, the transport buttons send sysex messages… so I can’t use any of them
And then the fader screens on the faderport16 receive sysex messages for track names and meters
“Works with any MIDI Controller
Has the manufacturer stopped supporting your gear? Don’t worry, If it sends out MIDI messages you can create a MIDI mapping script for it with Remotify.”
really, the software only supports midi notes and control messages.,. but lots of gear sends program changes when you switch banks, pitchbend is on most keyboards and is often used in motorized control surfaces for faders… and sysex is both MIDI real time messages, and as a place manufactures put settings and non-midi controls, is the most DIY idea ever and is totally in the spirit of what this software is supposed let you do
could we please MIDI fully implemented?
Is there any development in this (2 year old) case?
I just installed the app yesterday and already need to be able to use pitch bend information from my faderport which I totally expected to be possible!
Any help appreciated.
While we don’t officially provide solutions for Sysex.
It can be implemented via reactions mappings. Discussion on implementing it is here: https://remotify.io/community/question/how-display-ableton-track-colors-…
Thanks for the hint.
I still dont see how to receive raw midi data!
Like receiving the movement of a motor fader which sends pitch bend.
How can I do that?
Why not add more (or just all) MIDI Types in the MIDI Message Settings?
Or maybe a custom MIDI Type option, where you could write these numbers yourself:
144-159 Notes
160-175 Polyphonic Aftertouch
176-191 Control Change
192-207 Program Change
208-223 Channel Aftertouch
224-239 Pitch Bend
etc.
Note and CC is just not enough, if you want to use “any MIDI controller”.
This is not even Sysex.
I can’t imagine it to be that complicated to implement this because it’s just the first MIDI Byte as far as I understand…
Any response would be nice at this point.
We don’t currently have options for these (and its untested) but in the script.py code itself, you could try changing the type to pitch bend by changing
MIDI_CC_TYPE or MIDI_NOTE_TYPE to
MIDI_PB_TYPE for pitchbend,
or for sysex MIDI_SYSEX_TYPE
Sign up
User registration is currently not allowed.