[Rwp] some thoughts for the keymap development and things and stuff
Juan Pablo Bello
juanpisjaws at gmail.com
Fri Feb 26 08:59:08 EST 2016
I was thinking we need a better way to structure things.. on keymaps.
THere is just no way I am ever going to be able to use the numeric
keypad on this laptop, because it just does not even have an emulation
built in. Its just unacceptable, but that is theway it came I I think
i am not alone on that department. Or, I would just have to buy and
use a separate keyboard..
And, nice going with the portable installs, I think that is just a bit
unnecessary since you are able to create and automate reaper things..
its better to have just created a script and automate reaper to select
your audiod evices ETC when you first launch it... ETC because having
several installs of the program I think is a bit convoluted at best.
2016-02-26 3:22 GMT-05:00, Patrick Perdue <patrick at pdaudio.net>:
> Chris:
>
> Just so you know, control win anything is not viable in Windows 10.
> Windows does a lot more now with, go figure... the windows key.
>
>
> On 2/26/2016 3:19 AM, Chris Belle wrote:
>> There's been a lot of talk about how we are running out of room on the
>> keymap.
>> I've noticed some duplications, first we should weed those out.
>> I also have some very useful actions that I use all the time, depending
>> on what you do you may not want these but these are some of the one's I
>> bind.
>> Actions to move fx up and down in the chain.
>> I bind those to control win up and down arrows.
>> I also like the one for turning markers to regions for exporting
>> chunks of a long project, like audio books and such.
>> control win m
>> When you do that you can set your render options to export regions, very
>> useful.
>> I think reaper lends itself especially well to long spoken word and
>> audio book type projects, and I often have a couple of portable copies
>> or reaper rendering out long jobs while another reaper copy is doing
>> something else.
>> Hence my reasons for loving portable reaper because each can live on
>> the same machine,
>> \with it's own config doing tasks while your doing something else with
>> another instance.
>> You can of course, instantiate a reaper instance by just typing the
>> path to the executable in the run box with the - newinst
>> switch, but if you copy the folder to a new place with another name,
>> you can have another configuration like for dummy audio for those
>> rendering jobs,
>> or another sound card for recording, and leave it like that.
>> So I have reaper1, reaper2, and so on and so forth
>> not always that complex, but it's nice to know I can do that if I need
>> to.
>> There you go, for what it's worth.
>> \
>>
>> _______________________________________________
>> 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
>
--
Juan Pablo Bello
Cel. 313-879-2884
More information about the RWP
mailing list