[RWP] Legacy Surfaces

[indigo]

Maybe try not setting up your Peavey in Reaper preferences/control surface.
Instead, with the Peavey running, go to preferences/midi devices, look 
for entries from the Peavy in the same box where entries from your midi 
keyboard appear.
The word Disabled should be showing after each of the Peavey entries.

Focus on the top Peavy entry,  route to your pc cursor, right click at 
the number pad, then you should get the configuration dialog for that 
Peavy entry at your arrow keys.
click on configure, and put a check on the second item, send control 
messages, I think it's worded; but do not put a check on the top item, 
which could cause the Peavey to send note messages from its buttons, as 
if it was a midi keyboard.
Reaper treats midi keyboards and control surfaces the same, with the 
same configuration dialog for either; in preferences/midi devices.
Repeat configuration for all Peavey entries.
Then, after you get Enabled to appear after each Peavey entry, tab down, 
click apply, then click okay.
Indigo L


On 3/3/2012 11:15 PM, Jim Snowbarger wrote:
> Still working a bit on this Peavy control surface without too much
> progress.
>
> Got the midi monitor Indigo mentioned from
> http://midi-monitor.software.informer.com/
>
> It is acessible enough to let me puzzle out the messages being sent from
> my Studio Mix. So, I know it's protocol now. But, the problem is getting
> Reaper to connect a control service to a physical midi connection.
>
> Most of you probably already know this. But, I found that, if, in
> options, preferences, control surfaces, I Double left click the name of
> a control surface, a dialog opened that let me edit some things about
> that surface. two items in that dialog were the things I was looking
> for, the midi ports for input and output. But, they are not in the tab
> order. It is necessary to single left click to the right of the colon
> where it says, Midi Input: or Midi output:. Then, focus goes there, and
> you can use regular arrow keys to choose from one of your physical midi
> ports.
>
> The problem is that, even though I choose a valid port, when I clic ok,
> reaper says that it has encountered an error in opening a midi input, or
> output, depending on which one I set up, and both if both were configured.
> Of course, like all cuddly software, it doesn't say anything useful
> about what that error might be. Nothing like, unrecognized control
> surface, or anything like that. Just an error.
>
> You might say, well, of course, because Reaper doesn't know about your
> particular control surface, since your Peavy Studio mix is not in the list.
> But, I figure that, if I am just setting the midi input, so Reaper could
> accept control messages, it wouldn't have any idea what was out there,
> and no way to ask. So, how can it be upset about what it doesn't even know.
> Anyway, all of the defined surfaces are giving me those same errors.
>
> Yep, I can communicate in and out between reaper and external midi sound
> modules and keyboards. So, I don't think there is anything wrong
> physically.
> The midi monitor was able to receive data from the Studio mix just fine
> on that same port.
> And, I don't think I am going to be able to play any games associating
> midi events to actions, because those midi messages come from the
> control surface, which can't so far be established.
> Besides, the Studio mix protocol involves a string of 4 midi controller
> messages for each control action.
>
> Anybody have any ideas, why it might be throwing that error? I'm baffled.
> Thanks heaps.
>
>
> ----- Original Message ----- From: "indigo" <33indigo at charter.net>
> To: "Reapers Without Peepers" <rwp at reaaccess.com>
> Sent: Saturday, February 25, 2012 6:15 AM
> Subject: Re: [RWP] Legacy Surfaces
>
>
>> Oops, I sure screwed up that link to Standing Waters Studios.
>>
>> Here's the correct one:
>> http://www.standingwaterstudios.com/installation.php
>>
>> Jim, the assignment of any midi message from your control surface to
>> any Reaper action is a cinch, just joining the midi message to the
>> action number with a single letter, I think a semicolon; but
>> considering my recent example of my undependable memory, better check
>> SWS website.
>> Sorry,
>> Indigo L
>>
>> On 2/24/2012 11:55 PM, Jim Snowbarger wrote:
>>> Man, I hate to admit it, but I've got an old Peevee studio mix here
>>> that I'd love to marry up with Reaper. It's pretty ruggid hardware,
>>> and seems still quite reliable. It makes sense to keep using it. I
>>> didn't see it in the list. I need to go through and try all the
>>> settings one by one, to see if one works. Anybody's guess at which
>>> would be most likely?
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at reaaccess.com
>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>
>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>