Wesley Smith wrote:
> Alright, so I've got Nesa's patch doing something. It talks to the
> proper encoder, but I'm not getting it to behave like the settings
> should make it behave. When I send it the settings:
>
> knob, 42, NRPN, ccpar 9, min 0, max 1046, absolute/14, show value on,
> 1dot, increment 1, I get instead
>
> knob, 42, SPC, [no channel], [nor ccpar], [no min], [no max], 1dot, on
>
> Has anyone used this patch successfully? Here's the version I'm working
> with.
But as I understand from the web info on the BCR 2000, its an endless
encoder box. Why the hell would you want to bother to do the calculation
within the BCR, flood the Midi cable with long Midi messages instead of
using increment and decrement settings. Each tick would be one or two
Midi bytes instead of 4 NRPN or 10 (at least) Sysex bytes. Then within
your patch you can easily define the resolution you want... (up to 32-bit)
My way to setup faderboxes is always the same: I take the manual, choose
the one and only usefull setting for its lifetime and trash the manual
(not realy ;-).
For the use with max the programmability of a faderbox is nothing you
would ever want to deal with, unless its initial setup is unintuitive,
which is likely when it comes out of the box...
I have a bunch of flavors to decode endless encoders in my St.ools and
abhaXions: St.Dialin, dialin, dtlin... Just hack them and enjoy the
principle of endless encoders set to Midi inc/dec.
Stefan
--
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com