[Rwp] OSARA keymap

Derek Lane derek at pdaudio.net
Tue Feb 24 01:45:14 EST 2015


I'd rather run in to too much information, than not enough.

That's why, in some cases, reaaccess gave me the edge when I could instantly 
get information, even if it wasn't visible on screen.

Control+shift+J being a perfect example.



----- Original Message ----- 
From: "James Teh via RWP" <rwp at bluegrasspals.com>
To: "Reapers Without Peepers" <rwp at bluegrasspals.com>
Sent: Tuesday, February 24, 2015 12:05 AM
Subject: Re: [Rwp] OSARA keymap


> On 24/02/2015 11:19 AM, Scott Chesworth via RWP wrote:
>> SC: In this example, and any others that I can think of come to that,
>> there is some visual indication from changes in the wave forms on
>> screen though. Even if that's not the case, many people have that last
>> undo point at the end of the menu bar and could glance up to see
>> whether that'd changed.
> Sure. As I said in my next point, there probably aren't many in REAPER 
> that aren't indicated visually.
>
>> SC: I find Reaper tends to be fairly good at complaining when it's not
>> been able to do what you told it to.
> In some cases, yes, but not others. For example, if you press delete in an 
> empty project, you'll get nothing. The same is true for splitting at the 
> cursor. My point is that where REAPER *doesn't* warn you and no action 
> occurred, speaking the action name would be confusing. The other problem 
> is that OSARA has no way of telling whether REAPER warned you or not, so 
> this action would just go ahead and speak alongside the warning, which is 
> pretty redundant.
>
> Jamie
>
> -- 
> James Teh
> Email/MSN Messenger/Jabber: jamie at jantrid.net
> Web site: http://www.jantrid.net/
> Twitter: jcsteh
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp
> 



More information about the Rwp mailing list