March 7, 20242 yr Hi, I'm exploring the ability for AAO to use MIDI system messages (these are in the MIDI spec a sequence of bytes prefixed with 0xFO and end with 0xF7). In my test scenario, I'm sending a single value in the middle, such as 0xF001F7 to send system message "1". When I send such a sequence to AAO, it indeed reads but I only seem to get CHN: 0 EVT:0 CLICK no matter what I send. I'm not sure how it's coded to read these messages, so I know what it expects so I can send the correct sequence over. The MIDI controller I'm using is a programmable one (it's actually a touch tablet running Hexler's TouchOSC which can send any MIDI as well as OSC) and I can send custom system messages. I have not found specifically in the documentation or examples how MIDI system messages are handled (or what is required), so far AAO understands Control Changes for fader/knobs, and MIDI note on/off for click. Thank you for any insights - specifically an example of a MIDI system message understood by AAO as a click.
March 10, 20242 yr Commercial Member AAO doesn't really process SysEx messages. It receives them, but it doesn't care about the byte content. TMBK SysEx messages are hardware dependant and there is no universal spec for the contents. So it seemed pointless to try and implement any processing logic. In other words, you now have the chance to make your own spec. I'm open to all ideas that can be implemented with reasonable effort. Edited March 10, 20242 yr by Lorby_SI LORBY-SI
March 11, 20242 yr Commercial Member OK, so I went ahead and implemented the following for AAO version 4.20: MIDI SysEx messages will be understood and processed as 0xF0-CHN-EVT-VAL-0xF7. CHN, EVT, VAL are single byte values for channel (0-255), event-ID (0-255) and value (0-127) So a "button" would send 127 for the "down" event and 0 for the "up" event. An axis/slider/rotary encoder would send the full range 0 through 127 (ideally a rotary encoder would continue sending 0 0 0 or 127 127 127 when you turn it beyond the boundaries). If you want, send me an email to the support address (last page of the AAO manual) with your proof of purchase. Then you can test the 4.20. Edited March 11, 20242 yr by Lorby_SI LORBY-SI
March 12, 20242 yr Author 12 hours ago, Lorby_SI said: OK, so I went ahead and implemented the following for AAO version 4.20: MIDI SysEx messages will be understood and processed as 0xF0-CHN-EVT-VAL-0xF7. CHN, EVT, VAL are single byte values for channel (0-255), event-ID (0-255) and value (0-127) So a "button" would send 127 for the "down" event and 0 for the "up" event. An axis/slider/rotary encoder would send the full range 0 through 127 (ideally a rotary encoder would continue sending 0 0 0 or 127 127 127 when you turn it beyond the boundaries). If you want, send me an email to the support address (last page of the AAO manual) with your proof of purchase. Then you can test the 4.20. This is great, thank you. I think the sys-ex messages are very helpful with the "glass" midi controllers because it opens up quite a few more commands. Looking forward to 4.20 and I'll send you the info. Cheers.
Archived
This topic is now archived and is closed to further replies.