[RWP] Legacy Surfaces

[indigo]

In Reaper, you can associate any incoming midi message with any action, 
just browse through  the hundres of so far  unassigned actions in the 
actions list
It's mind boggling!
You cannot associate the Peavey to Reaper, in the sense that there's 
already a key map in Reaper, like there is  with the supported control 
surfaces, it'll be a custom job, but linking CC's to actions should go 
much quicker than assigning each control's  actions with midi learn.
For Sonar, what about those Cakewalk instrument profiles, whatever 
they're called?
Did you say your Peavey has ACT
It could be worth trying, to see how much ACT can auto assign to the Peavy.
Also, google for user written control maps. plus ask in the Peavey 
forums, maybe somebody else has already done it and will share.



On 2/29/2012 10:31 PM, Jim Snowbarger wrote:
> Does anybody have any idea how to associate a control surface with a
> particular midi connection?
> I don't see any association in options, preferences, control surfaces to
> a particular midi interface. I have several, and God knows which one it
> is trying to use.
> All I know is it apparently isn't the one I'm connected to.
> Likewise in the midi devices sectons, which for some weird reason is in
> options preferences, under audio, of all places, I don't see any way to
> associate them.
> I think I'm missing a piece somehow.
>
> ----- Original Message ----- From: "indigo" <33indigo at charter.net>
> Cc: "Reapers Without Peepers" <rwp at reaaccess.com>
> Sent: Saturday, February 25, 2012 5:48 AM
> Subject: Re: [RWP] Legacy Surfaces
>
>
>> Is that the Peavy 1600, Jim, which I've always heard was one of those
>> classic everlasting pieces of gear?
>>
>> For years now users have been requesting, and not getting, a generic
>> Control Surface catagory in Reaper's options/preferences/Control
>> Surfaces.
>>
>> No Peavy is listed in supported control surfaces, but you can do
>> something with it as it is, or configure the messages it sends to do
>> any action.
>> Just turn it on before starting Reaper, go to options/preferences/midi
>> devices and enable it for midi and also for control messages.
>> If you're useing another keyboard for note messages, and you get note
>> messages from the Peavey, only enable it for control messages.
>>
>> Reaper will receive whatever messages it sends and something will
>> happen, though the results may be unusual! smile..
>> I just enabled my Yamaha MM6 for midi and control messages; and the
>> MM6's filter controls, plus attack and decay workfor some soft synth
>> presets.
>> The arpeggiator on the MM6 is arpeggiating soft synths, the drum is
>> being received on channel 10, so I can drive other drum kits, and the
>> bass; and the whole auto accompanyment sections is transmitted, I
>> think, on channel 3 and 4.
>>
>> The output channels are fixed on the MM6, but that shouldn't matter.
>> Essentially, you can use any message Reaper receives to trigger any
>> action, and add more actions by installing .sws extended actions, from
>> www.stillwaterstudios.com
>> or maybe it's
>> www.stillwaterstudios.org
>> 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
>