[RWP] Routing Tracks to master track

[Indigo]

Adaptability is the key to survival; isn't it?
You switched back and forth between Jaws and System Access, depending on 
the need at the moment.
Me too; I love NVDA, how can it be a threat to me.
I can sympathize with anyone who wrote Jaws scripts or relied on 
teaching Sonar being afraid of losing that; but they can take a lesson 
from the dinosaurs, who ate only certain ferns; and when the climate 
changed they starved.
Wolves were around back then too, but they ate anything, plant or 
animal, and they're still around, still eating everything, and enjoying 
it all.
Mmy Woofie hates the taste of Silantro and crickets, which taste the 
same to me; everything else he likes.
Indi

On 5/22/2013 5:01 PM, David P Shortland wrote:
> Hi & Greetings from a Chilly Queensland morning
>
> I could not agree more Indigo... Well said...
>
> Oh and BTW...I am one of those people using REAPER to make money...
>
> Regards
>
> David P Shortland
> DragonScore Productions
>
>
>
> -----Original Message----- From: Indigo
> Sent: Thursday, May 23, 2013 4:38 AM
> To: Reapers Without Peepers
> Subject: Re: [RWP] Routing Tracks to master track
>
> Why not try for yourselves the set automation mode and enbelope type
> activation in the track menu, and quit thinking Sonar when you're trying
> Reaper.
> Sonar does snapshots, Reaper writes automation envelopes, and ReaAccess
> doesn't prevent it.
> This mail list is for people who want to learn Reaper, not for those who
> see it as an enemy of Sonar.
> If you have Sonar and like it, then use it and be happy, okay?
> Let's don't get a daw war going here and clutter RWP with irrelevent crap
> Indi.
> ?
> Either that or ask yourself
> On 5/22/2013 1:16 AM, Patrick Perdue wrote:
>> You can't do real track automation without a control surface in Reaper,
>> at least not just with ReaAccess, and everything else stock otherwise.
>> Maybe some extensions can do it. The promised ReaAccess 2.0, which never
>> happened, was supposed to provide such functionality, an automation
>> envelope editor, and other such potentially useful tools.
>>
>> On 5/22/2013 1:12 AM, Chris Belle wrote:
>>> So is this with just a surface or will this honor your settings on a
>>> track, from the computer keyboard,  keys and can you actually do
>>> snapshots?
>>>
>>> In other words, stop the transport, make a setting that will be
>>> remembered later, and then go on?
>>>
>>> Have you actually done this raising and lowering volume and pan and
>>> other parameters with automation not using a control surface in this
>>> manner?
>>>
>>>
>>>
>>> ----- Original Message ----- From: "Indigo" <33indigo at charter.net>
>>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>>> Sent: Tuesday, May 21, 2013 6:55 PM
>>> Subject: Re: [RWP] Routing Tracks to master track
>>>
>>>
>>>> In Reaper, action 65 is Set All Tracks Automation Mode to Write, and
>>>> Set all tracks Automation Mode to read is a little below that.
>>>> Besides write you also have touch, latch and trim.
>>>> Instead of set all tracks automation mode, while a track is selected
>>>> with up and down arrows, tab to automation mode and select with arrows
>>>> on a per track basis.
>>>> Press enter to keep selection.
>>>> Indi
>>>>
>>>> On 5/21/2013 6:16 PM, Alexander Westphal wrote:
>>>>> Hi Patrick!
>>>>>
>>>>> Well, Sonar is more comfortable in these things. There you can say
>>>>> "Write Automation" and it will do it. Okay, this is a very simple
>>>>> explanation, but it is as simple as can be. You go to the track or
>>>>> bus,
>>>>> go to the item you want to automate, e.g. volume or pan, press
>>>>> contextmenu, look for "Automation Write" and press enter, press CTRL+R
>>>>> for Automation Record and change the value while playing with plus and
>>>>> minus or - if assigned - move the slider on your controller.
>>>>>
>>>>> With the Master Bus it is also very simple, because it is available
>>>>> in a
>>>>> "Bus Panel". In most cases all audio and softsynth tracks are
>>>>> routed to
>>>>> this. Hope I understood your message right and you needed this
>>>>> explanation.*grin*
>>>>
>>>> _______________________________________________
>>>> 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
>
> _______________________________________________
> 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