--- In bc2000@yahoogroups.com, "Royce" <rpcfender@...> wrote:
> There are also some strange actions like
>
> Btn 1
> $B0 7 0 ;off
> $B0 7 10 .on
>
> Btn 2
> $B0 7 0 ;off
> $B0 7 110 ;on
>
> Btn 2 going on will make Btn 1 go on (> the on value of 10)
> but
> Btn 1 going on will not make Btn 2 go on
>
> A bit of hysteresis going on or is it the bit setting
> 10 = 000 1010
> 110 = 110 1110
> Perhaps Mark knows.
A button set up via ".easypar CC" reacts to any incoming message on the same channel and controller (via MIDI or from another button/encoder) based on the AVERAGE of its Value1 and Value2: below the average, the LED goes into its "low" state, above the average into the "high" state, where "low" and "high" are "off" and "on" or vice versa, depending on whether Value2 is smaller or larger than Value1.
In the above, I've been intentionally vague about the exact cut-off point, since I've found a seemingly strange, slight mismatch:
Value1=127, Value2=0:
0..63: off
64..127: on
Value1=0, Value2=127:
0..62(!): on
63..127: off
I'd have to investigate further to figure out exactly how this works.
Anyway, I'm sure I've written about this phenomenon before, but right now I can't find it in "BC MIDI Implementation.pdf", so either it's buried in there somewhere, or (more likely) I wrote about it in a message thread in this forum or elsewhere. So maybe I'll have to update the document.
In any case the phenomenon of buttons/encoders affecting other buttons/encoders ("value synchronization") is discussed in section 14.9 of BCMI.
Hope this helps,
Mark.Message
Re: mulfunction or?
2012-06-25 by Mark v.d. Berg
Attachments
- No local attachments were found for this message.