The first thing I have to mention about this CC:45 is that I’m surprised that the first two actions (set RPO, Set ROP) use separate values, mutually exclusive (2x2 or 6x6), while the rest of the functions have been implemented as a single value that toggles between on/off state.
I think this is an unfortunate decision, especially when it comes to configuration parameters. It prevents you from knowing what the result of the action will be without looking at the screen, requiring multiple clicks just to check its state (now rinse and repeat for each one 
). It also prevents storing configurations or sending batch actions from an external device, even for the most simplest sets.
A practical example with the current implementation:
I want a button that sends at once:
- VU Meter Source toggled to Main In
- Recording Source: Main In toggled to On
- Recording Source: Aux In toggled to Off
As the actions are of the toggle type, I will have to check beforehand that their state is the opposite of what is expected to do.
But wait! There’s another problem: The Aeros seems not to respond correctly to consecutive messages. Of the three messages, it only responded to the last one received. Maybe it needs some kind of MIDI buffer?.
So… I’ll have to try adding a small delay while sending messages: 25 milliseconds for the second, and 50ms for the third. Now it works!
Isn’t it great?
Well… it works with all those workarounds. But it’s not too elegant. Nor practical. Nor comfortable.
The other option would have been to implement these functions using two values for each one. Instead of using 24 values of CC:45 for those new functions we would be using 48, that’s true. But it would be infinitely more elegant. More practical. More comfortable. Then it would be great.
So please:
Make Aeros Great Again 