[Rwp] OSARA keymap

[Patrick Perdue]

For my part, I would only want Reaper to play when navigating between 
items if it was already playing. If Reaper is stopped, it is stopped for 
a reason.
I frequently deal with projects having hundreds of item splits, and 
things get slow enough as it is toward the upper end of those numbers. 
I'd think this would slow things down even more, unnecessarily so.

On 2/23/2015 5:39 AM, James Teh via RWP wrote:
> 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
>