sandcobainer~

Screen Shot 2018-12-24 at 2.35.59 AM.png

Not exactly related to Max. But I took a turn from M4L and started developing MIDI Remote Scripts in Python for DJ controllers. Something weird happens here when I move a fader on the controller. A single fader transmits 2 CC values on channel 2 on 8 and 40.

The CC value on 40 is erratic, while the one on 8 is the one I'll probably end up using for slider control. But why are there 2 CCs triggered by one fader. Is this some industry standard that I do not know? If the CC value on 40 has a specific pattern, I could use it for something fun. I'm currently using it to create a random note between 0 - 127.

Hey Ableton/Max hackers,

Not exactly related to Max. But I took a turn from M4L and started developing MIDI Remote Scripts in Python for DJ controllers. Something weird happens here when I move a fader on the controller. A single fader transmits 2 CC values on channel 2 on 8 and 40.

The CC value on 40 is erratic, while the one on 8 is the one I'll probably end up using for slider control. But why are there 2 CCs triggered by one fader. Is this some industry standard that I do not know? If the CC value on 40 has a specific pattern, I could use it for something fun. I'm currently using it to create a random note between 0 - 127.





 
Hey Ableton/Max hackers,

Not exactly related to Max. But I took a turn from M4L and started developing MIDI Remote Scripts in Python fo

ccs-bug-for-python-midi-remote-scripting

HUI protocol. Two CC messages, 32 apart, one for MSB and one for LSB, gives you 14 bits of precision.

HUI protocol.  Two CC messages, 32 apart, one for MSB and one for LSB, gives you 14 bits of precision. 

I'm sorry I'm a beginner at protocols, especially MIDI and hardware. Do you have a reference to the HUI protocol?

Nope but I’m sure you can find one on line. For me it wasn’t hard to figure it out after noticing the patterns as I moved sliders etc.

CCs bug for Python MIDI remote scripting