> On Jun 1, 2016, at 5:41 PM, [email protected] wrote: > > b) reduce the range of possible values for your data (e.g. 0-127, like MIDI) > and reserve the rest for addressing (128-255). If you need a greater > resolution for your values, just break them up into several bytes. This way, > sending a single 16 bit integer would take 4 bytes (address, bit 14-15, bit > 13-7, bit 0-6).
That’s a great point. Everyone complains about MIDI now (not enough range, etc) but it’s *perfect* for what it was designed to do: send small event data quickly on much older, slower hardware. I little bitmasking and away you go. -------- Dan Wilcox @danomatika <https://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
