<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello,<br>
In most programs the shift key is the nullifying keystroke.<br>
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.<br>
a and a again would probably be my second idea if that is
possible.<br>
Here is what would be my key map:<br>
a arm<br>
m mute<br>
s solo<br>
ctrl + i insert track<br>
up and down arrows, move between tracks<br>
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.<br>
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<br>
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.<br>
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.<br>
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.<br>
ctrl+o would be open<br>
and for inserting audio files in the current position or inserting
a midi synth or effect you just do alternates of a modifier + i.<br>
same goes for open, something + o.<br>
to start and stop hit space<br>
to loop the selected area shift + space<br>
to record hit r<br>
to pause hit p<br>
to save ctrl+ s<br>
to save as ctrl+ shift + s<br>
to export, ctrl + e<br>
to raise and lower the volume on the current track ctrl + up and
ctrl+ down<br>
to raise and lower the volume on the whole project, ctrl+shift +
up and ctrl+shift+down<br>
to change the panning on the track alt + right and left<br>
to change the panning on the whole project alt+shift+right and
left<br>
to move by beats, page up and down<br>
to move by measures ctrl + page up and down<br>
new project ctrl+n<br>
leave the function keys plus the numbers for the user to assign to
bring up synths or effects.<br>
delete to delete<br>
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.<br>
enter selects items, toggles buttons and hits ok on buttons.<br>
<br>
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.<br>
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.<br>
When learning a new piece of software I want to know 2 things:<br>
1. how to install it<br>
2. how to make it work<br>
<br>
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.<br>
<br>
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.<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
It is on github, so you can make a github page for the wiki that
links to them on youtube.<br>
thanks,<br>
<br>
<div class="moz-signature">
<a href="http://www.brandonkeithbiggs.com/">Brandon Keith Biggs</a></div>
On 2/23/2015 10:59 AM, Scott Chesworth via RWP wrote:<br>
</div>
<blockquote
cite="mid:CAL7HGJQAn=0SAhi1uxOGckEfXXheLer75Qw+aGDMo-q6kcRc+w@mail.gmail.com"
type="cite">
<pre wrap="">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 <a class="moz-txt-link-rfc2396E" href="mailto:rwp@bluegrasspals.com"><rwp@bluegrasspals.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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 <a class="moz-txt-link-rfc2396E" href="http://www.brandonkeithbiggs.com/"><http://www.brandonkeithbiggs.com/></a>
On 2/23/2015 3:28 AM, Scott Chesworth via RWP wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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 <a class="moz-txt-link-rfc2396E" href="mailto:rwp@bluegrasspals.com"><rwp@bluegrasspals.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 23/02/2015 8:19 AM, adriandavids404--- via RWP wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap="">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: <a class="moz-txt-link-abbreviated" href="mailto:jamie@jantrid.net">jamie@jantrid.net</a>
Web site: <a class="moz-txt-link-freetext" href="http://www.jantrid.net/">http://www.jantrid.net/</a>
Twitter: jcsteh
_______________________________________________
RWP mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a>
<a class="moz-txt-link-freetext" href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
RWP mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a>
<a class="moz-txt-link-freetext" href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">_______________________________________________
RWP mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RWP@bluegrasspals.com">RWP@bluegrasspals.com</a>
<a class="moz-txt-link-freetext" href="http://bluegrasspals.com/mailman/listinfo/rwp">http://bluegrasspals.com/mailman/listinfo/rwp</a>
</pre>
</blockquote>
<br>
</body>
</html>