[RWP] the latest reaper is worth a look.

[Tor Tollhag]

Wow that sounds interesting.
I've recently got reaper 3.78 64 bit installed here with reaaccess
scripts on my new laptop.
Of course I have to learn to use it diferently since I don't have an
applications key, but I guess the applications key partly doesn't work
anyway in reaper 4, I still might check this latest version out.
I know they've now updated to a later version of the elastique time
stretching, I know I tried that out on my other xp machine that I now
don't have anymore and I honestly couldn't tell any diference.
But this sounds interesting.


2014-07-26 20:28 GMT+02:00, Derek Lane <derek at pdaudio.net>:
> I've been using reaper 3.78 for the last 3 years due to the ease of routing,
> and other related features of both that interface, and the working
> reaaccess.
> However, I was told that the latest version of reaper offers a
> sends/receives/hardware output dialog which one could tab through.
> The problem in reaper 4 which annoyed me was that the sends/receives menu,
> normally accessed with shift+applications, no longer worked, and that I
> didn't want to spend time messing with a screen reader if I didn't have
> too.
> Now, as I said, pressing I gives you a dialog which I find to be very easy
> to use.  Sure, in projects where lots of routing exists, tabbing through the
> options for the master  and each send could be tedious, but muscle memory
> will prevail, taking care of that issue.  Furthermore, it is possible to
> type values in the majority of the fields presented in this dialog.
> I don't know if the reaper developers actively made these changes for sake
> of accessibility, or if it was one of those accidental things, but for those
> who are in contact with the developers, encourage them to keep going in the
> direction they seem to be heading.
>
> Now the only standing issues for me are a way of editing automation, and the
> little semantic issue where the reaccess preferences are in the item menu,
> which didn't exist in reaper 3.
> I'm guessing a trip to the menu  editor would fix that problem, but I
> haven't played with that extensively.