[Rwp] OSARA keymap

[Chris Belle]

For some reason that control i doesn't work.

But everything else does.



On 2/23/2015 3:14 AM, Gianluca Apollaro via RWP wrote:
> Hi James and list,
> I've been using Osara for a couple of weeks and Derek Lane and I are 
> working on a keymap and we would like to share it with you all. This 
> keymap overrides some actions rea-access assigned, so use it 
> exclusively with osara.
> We also mapped some sws actions to keys, and chained others to make 
> reapers behavior more familiar.
> For example, reapers default behavior when making a track is to simply 
> create it, without giving the user the ability to name it, unless you 
> choose to do so by pressing f2, But control+t chains creating and 
> renaiming together, so that you have the ability to edit the tracks 
> name, after you create it.
> Pressing alt+c brings up the reaconsole, which lets you adjust track 
> settings from a command line.
> Pressing control+i will allow you to paste a file in the clipboard in 
> to your project.  There is a bug in this action though, which makes it 
> ignore your ripple editing preference, so acts as if you have ripple 
> mode off.
> As far as osara was concerned, we started by Taking the actions 
> written in the documentation you provided and assigned them to keys we 
> were using in rea-access, for example the function keys like f7 for 
> arming the last touched track, f5 to mute and f6 to solo. We also 
> customized some actions to simulate some rea-access behaviour, like 
> shiftHome and shiftEnd keys to select to start of project or to end of 
> project, or ctrl left and right arrows to navigate to items. 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. Those are assigned to Dash and Equals 
> key if using an English keyboard, CtrlShift BackSpace resets the 
> playrate to 1.0 and shift BackSpace toggles the pitch preserve when 
> changing rate. We also mapped some sws actions like Play selected item 
> once to CtrlAlt and The space bar, and chained some others for 
> navigating to next or previous transient in item using tab and shift 
> Tab respectively.
> Differences with rea-access:
> There are some things that are different from rea-access because 
> either we thought our methods were more useful, or reaper and/or sws 
> couldn't be used to emulate the behavior of rea-access.
>   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. In 
> Osara we don't have the virtual mode we had in rea-access, so we can't 
> use it to increase or lower the item or take volume. Therefor we 
> assigned changing take volume by one db to shiftPageUp to raise it and 
> shiftPageDown to lower it.
> At the moment pressing the delete key will only delete tracks or items 
> depending on focus. To delete a time selection  we used a different 
> keys that is alt+Shift+Delete.
>
> If you want, you can download this keymap from
> http://dl.dropbox.com/u/5126017/DGKeyMap02-23.ReaperKeyMap
> To import it, go to the action list and choose import/export button.
> Hope you find it useful,
> Gianluca from Italy.
> SkypeID: gianluca8815
> Il 22/02/2015 22:47, James Teh via RWP ha scritto:
>> Hi all,
>>
>> The biggest point of contention between me and a large number of the 
>> rest of you concerning a keymap seems to be the use of function keys 
>> for mute, solo, arm, etc. I understand the argument concerning the 
>> need for a single key press. However, for such an extremely basic and 
>> common operation,
>> I really feel the function keys are counter-intuitive, difficult to 
>> remember and slow for some users to find. I don't buy the "you'll 
>> eventually get used to it" or "you can stick dots on your keys" 
>> argument. Those are both workable solutions, but not elegant ones.
>>
>> So, I have several questions:
>> 1. Can we do better? Does anyone have an idea as to how we can assign 
>> these actions to maximise efficiency and intuitive experience without 
>> making other things less functional? I'm not normally a fan of 
>> overriding built-in bindings, but we're already doing that for track 
>> navigation anyway (given the default bindings are just silly), so 
>> perhaps this is just something we need ot accept for the sake of a 
>> good user experience.
>> 2. Am I seriously the only one who has an issue with the use of 
>> function keys for this purpose? If so, I guess I can consider 
>> conceding the point and just maintaining my own separate keymap.
>> 3. If (2) is the only option, does anyone want to volunteer to 
>> maintain the keymap?
>> 4. As I understand it, the way ReaAcccess installs the keymap is to 
>> simply override the user's existing keymap completely. This isn't 
>> ideal, but it does allow for automated installation. The alternative 
>> is to provide a keymap the user must import. Have there ever been 
>> complaints from users about this keymap overriding or do people tend 
>> to just accept this is what happens? I guess this is okay for most, 
>> since they're probably new REAPER users.
>>
>> Thanks,
>> Jamie
>>
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp
>