[Rwp] OSARA keymap

[Derek Lane]

We changed the console from c, to shift+c because c creates a tempo marker, 
and shift+c edits the marker closest to the cursor.
Again, trying to preserve as much of the reaaccess functionality as 
possible.

I use vary-speed a lot because of my work in editing large podcasts.  Its 
good to be able to speed through material I know to be fine.

As far as the tab and shift+tab transient navigation goes, playback doesn't 
follow the cursor, but the actions we chained together makes this the case.

The automatic playback of items is another excellent means of seeking 
through a large project.
Unlike reaaccess, it  gives you the perk of being able to play your project, 
and while playing, jump to the next item, not the beginning of the currently 
playing item.

There are some osara actions missing, which deal with metering and a few 
other things, but I'll report those if necessary.
It would be nice to have an action which would echo the previous action.
For example, reaaccess speaks when you do things like stretch and fit items 
to time selection, add tempo changes, etc.  Rathe than attempt to make 
everything speek, adding an "echo last action" function would give keymap 
designers the ability to speek or not speek sertain actions.










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


> Hi Gianluca,
>
> Thanks for your work. Some questions:
>
> On 23/02/2015 7:14 PM, Gianluca Apollaro via RWP wrote:
>> Pressing alt+c brings up the reaconsole, which lets you adjust track 
>> settings from a command line.
> SWS binds this to just "c" by default. Is there a reason you changed this?
>
>> Then we added some other actions we think are useful like some Vary speed 
>> changing that changes the master playrate of a project by either a 
>> semitone or cents of a semitone.
> Wow. Are these really so commonly used? I can see them being useful for 
> special effects or the like, but didn't imagine they'd be used by most.
>
>> and chained some others for navigating to next or previous transient in 
>> item using tab and shift Tab respectively.
> Don't tab and shift+tab do this by default without chaining? Or am I 
> missing something?
>
>> In our keymap when we move to an item the cursor starts playing, whereas 
>> in rea-access that didn't happen if the cursor was stopped.
> Was this an intentional change or something you couldn't work around 
> without losing some other desired behaviour? My concern here is that this 
> might not be desirable for editing.
>
> Thanks,
> 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
>