[RWP] Legacy Surfaces

[Jim Snowbarger]

Ran into an interesting snag on this one.

When reaper talks about CC messages, or continuous controllers, it also 
talks about a parameter value.  It's not completely clear what is meant by 
that.  But, clear it is one of the trailing bytes of data along with the 
controlelr message, either byte 2 or byte 3.

But, I know the midi messages that are sent for each of a small group of 
buttons on the Peavey StudioMix surface that I wanted to assign to various 
actions.

The bottom line is that reaper thinks all those buttons are identical.

The message sent for each button is a 3-byte message.
The first is BF hex, wich is some kind of continuous controller on channel 
16.
Second byte is a value that identifies this group of buttons.
Third byte is a unique code for each button in this group.

Reaper is only decoding the second byte, thus thinking that all buttons in 
this group are the same button.

I think I need to be able to write my own control surface.
Or, I could just by a Behringer and be done with it.  <grin>  When I'm in a 
good mood, the challenge sounds interesting.
When I'm not,  oh well.

All the known control surface definitions seem to be in one file
Reaper_CSurf.dll.  Just for grins, I copied my StudioMix.dll from cakewalk 
into that folder, but it wasn't magically picked up.
I know you can write control surfaces for Sonar.  I think Vic did it as part 
of JSonar.
Has anybody heard of peoplewriting control surface definitions for Reaper?