[Rwp] OSARA key map

Mon Feb 23 05:47:54 EST 2015

Hello,
In most programs the shift key is the nullifying keystroke.
As a person who has never managed to get Reaper working thanks to the 
horrible key maps, this is a specific thing I would like to see made a 
lot more understandable.
a and a again would probably be my second idea if that is possible.
Here is what would be my key map:
a arm
m mute
s solo
ctrl + i insert track
up and down arrows, move between tracks
tab and shift + tab, move forward and back through different pains and 
when you move through each window/pain, have a message say what the new 
pain is and what it is for. Make it loop as well.
left and right arrow is move through the different options on each track 
and make it loop with a sound beeping when you get back to the name field
ctrl+ left and right, move forward and back by a little bit, I don't 
always work with music, so possibly a time increment of 1 pixel would be 
nice.
add shift to the arrows to add select. ctrl+shift+ right will select to 
the right and ctrl+shift+left will either select to the left or unselect 
what the ctrl+shift+right did.
ctrl+home and ctrl+end would be jump to the top and jump to the end and 
ctrl+shift+home would select from the current cursor to the beginning 
and ctrl+shift+end would select from the current position to the end.
ctrl+o would be open
and for inserting audio files in the current position or inserting a 
midi synth or effect you just do alternates of a modifier + i.
same goes for open, something + o.
to start and stop hit space
to loop the selected area shift + space
to record hit r
to pause hit p
to save ctrl+ s
to save as ctrl+ shift + s
to export, ctrl + e
to raise and lower the volume on the current track ctrl + up and ctrl+ down
to raise and lower the volume on the whole project, ctrl+shift + up and 
ctrl+shift+down
to change the panning on the track alt + right and left
to change the panning on the whole project alt+shift+right and left
to move by beats, page up and down
to move by measures ctrl + page up and down
new project ctrl+n
leave the function keys plus the numbers for the user to assign to bring 
up synths or effects.
delete to delete
the applications menu to simulate right-clicking and make it bring up a 
menu on an item. if there are more than one menu for an item, 
shift+applications.
enter selects items, toggles buttons and hits ok on buttons.

This is a very practical key map in my opinion and it is a mix of what 
audacity, Sonar, Pro Tools and just typical windows applications use 
already.
above this functionality, you have a lot of letters and the whole 
function row and many other keys to assign to do what you wish. I think 
the above list should be all that is said in the basic readme for new 
users and anything else should be in a different section.
When learning a new piece of software I want to know 2 things:
1. how to install it
2. how to make it work

I need to be able to record, play back, navigate and select in the first 
5 minutes. if it takes longer then that I am not happy. This includes 
reading the readme.

So the readme should have a 10 step tutorial or a 5 minute video showing 
how to download and record and edit and if there is time, how to insert 
a midi synth and effect.
any longer than 10 steps and people get lost. Any longer than 5 minutes 
and I don't want to watch it. I would rather stay with Audacity and Sonar.

another thing that should be in another section is how to change between 
using your computer's audio card and an external one. I think you can 
use reaper on your computer's internal audio card, so if that is not 
default with a reaper instal, it should be the second section of the 
readme, how to change between sound-cards.

It would be really awesome if there was a list of videos that explain 
how to do a host of different things that are no longer than 5 minutes 
each. Then they can be on the tutorial for those who wish to watch.
It is on github, so you can make a github page for the wiki that links 
to them on youtube.
thanks,

Brandon Keith Biggs <http://www.brandonkeithbiggs.com/>
On 2/23/2015 10:59 AM, Scott Chesworth via RWP wrote:
> Hi Brandon,
>
> I'm curious about something. Taking mute as an example, why would you
> want M and Shift+M to mute and unmute, when just M could act as a
> toggle, so one press mutes, the next press unmutes. My thinking is
> that if it's a toggle, it then frees up Shift+M to be used for
> something related to muting that applies to a wider range of tracks,
> but what's yours?
>
> Cheers
>
> Scott
>
>
> On 2/23/15, Brandon Keith Biggs via RWP <rwp at bluegrasspals.com> wrote:
>> Hello,
>> I agree, build the keymap for the newbies and not for the power users.
>> a and shift+a for arm and un arm, s + shift s for solo and unsolo, m +
>> shift s for mute and un mute and the right and left arrow keys for
>> moving forward and back in the key map.
>> Thanks,
>>
>> Brandon Keith Biggs <http://www.brandonkeithbiggs.com/>
>> On 2/23/2015 3:28 AM, Scott Chesworth via RWP wrote:
>>> Hey Jamie,
>>>
>>> Wouldn't worry about overwriting the default bindings. because it's
>>> widely acknowledged that they suck anyway. There are tons of forum
>>> threads about it. It seems like one of the first things sighted Reaper
>>> users do once they start trying to improve upon their productivity is
>>> build their own keymap. I haven't yet heard of a case where such a
>>> sighted power user transitions over to using Reaper with a screen
>>> reader and starts screaming blue murder about their keymap being
>>> munched.
>>>
>>> Personally, I'd vote we hash out a keymap on here however the heck
>>> that could be done productively and work toward that automated
>>> install. That way, if anybody has a little more work to do, it's the
>>> power users instead of the people picking Reaper up for the first
>>> time. Smoother entry for the newbies, and less support.
>>>
>>> Scott
>>>
>>> On 2/22/15, James Teh via RWP <rwp at bluegrasspals.com> wrote:
>>>> On 23/02/2015 8:19 AM, adriandavids404--- via RWP wrote:
>>>>> I stand to be corrected, but I do think Reaaccess does allow the user
>>>>> to
>>>>> choose if the Reaaccess key map should override the user's key map?
>>>> My apologies for being unclear. You're correct; it does. What I meant is
>>>> that (assuming I'm not incorrect) you have two options: override the
>>>> keymap *completely* or don't install it at all. That is, if you've made
>>>> changes before installing it, you can't keep those changes while also
>>>> installing the ReaAccess keymap.
>>>>
>>>> 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
>>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bluegrasspals.com/pipermail/rwp/attachments/20150223/7b60b46f/attachment.html>