[RWP] Legacy Surfaces

[indigo]

Hi Jim,
When I've enabled a control surface in Reaper's preferences/ midi 
devices, I've only used the pots and faders to tweak soft synth parameters.
I know that works, but I've never tried to get the buttons going.
I'll bet someone has, though, and may have a fix buried somewhere in the 
infinite maze of Cockos forums.
For years users have been requesting a generic definition file for 
unsupported control surfaces, which; I would assume without knowing my 
ass from my elbow as to hexadecimal or third data bytes, would either 
recognize that third byte, or be user configurable.
The Cockos forums are full of experimenters;  who often write JS or .sws 
files to do actions that are already in Reaper, only they haven't found 
the default actions yet.
I saw that when I went to the forums to learn how to transpose a midi 
file by octaves.
There were several Jessasonic VST plugs written to do that, along with 
pitch shifting, while Reaper already had default shortcuts to do it.
ReaAccess is a remap of the default Reaper keymap, so those default 
shortcuts don't work from ReaAccess, but transposing by octaves is as 
simple as pressing the shift+9 shortcut, transpose by halfstep;  12 
times to get the octave.
It's not as cool as a single key press would be, but it works.
I think the default transpose by octave action could be easily assigned 
another shortcut to use it within ReaAccess; if it's worth doing for as 
seldom as I might use it.

So, what I'm thinking is there might be a way in Reaper already in place 
to get that third byte recognized for those buttons.

You know who will be knowledgeable about that is the guy at 
www.standingwatersstudios.com
who wrote the .sws extended actions for Reaper.
Maybe he's already written something.
You guys can happily talk hexadecima lese together, anyway. smile.
Indigo L


On 3/5/2012 10:44 PM, Jim Snowbarger wrote:
> 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?
>
>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>