<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class="">On Jun 1, 2016, at 5:41 PM, <a href="mailto:pd-list-request@lists.iem.at" class="">pd-list-request@lists.iem.at</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><span class="" style="float: none; display: inline !important;">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). </span></div></blockquote><br class=""></div>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.<br class=""><div class=""><br class="webkit-block-placeholder"></div><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">--------<br class="">Dan Wilcox<br class=""><a href="https://twitter.com/danomatika" class="">@danomatika</a><br class=""><a href="http://danomatika.com" class="">danomatika.com</a><br class=""><div class=""><a href="http://robotcowboy.com" class="">robotcowboy.com</a></div></div></div><br class=""></body></html>