[Rwp] OSARA keymap

James Teh jamie at jantrid.net
Sun Feb 22 16:47:50 EST 2015


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

-- 
James Teh
Email/MSN Messenger/Jabber: jamie at jantrid.net
Web site: http://www.jantrid.net/
Twitter: jcsteh



More information about the Rwp mailing list