[Rwp] OSARA keymap

[Gianluca Apollaro]

Hi James and list,
I'll try to answer your questions as best as I can
1. We changed the C hotkey because in rea-access it was mapped to edit 
signature marker, so for a continuity reason.
2. About the change master playRate I personally use those actions, and 
this is a keymap We're trying to create to se what can be done with 
osara, keeping it familiar with what we were doing with rea-access, So 
since Derek had these actions mapped to those keys and they weren't 
conflicting with anything, we kept them in
3. For Tab and Shift Tab actions, we customized them so that as you move 
by transient you hear that transient, by default the cursor would move, 
but not the playback cursor, and I know this has its pros and cons, but 
this is just our way of using it.
4. I understand your concern about item navigation, but I couldn't find 
another way to achieve what we had in rea-access, in fact, if you use 
the action select and move to next item, that you reported on the 
documentation, the cursor would move to that item but the playback 
doesn't follow it and I wanted to make so that it did
I hope my answers were clear enough.
Best regards,
Gianluca from Italy.
SkypeID: gianluca8815
Il 23/02/2015 11:39, James Teh via RWP ha scritto:
> 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
>