[Rwp] ditching ReAccess for good?

[Scott Chesworth]

If you're starting a fresh right now, OSARA is almost certainly the
right solution to learn on. There are still a few rough edges with
getting set up, but by using OSARA from the get-go you're essentially
cutting out a bunch of relearning that the ReaAccess folks will have
to tackle at some point further down the line.

Here, I'm still switching between the two of them, but it's for mainly
vanity reasons. If I'm working on something and have someone watching
over my shoulder, at this point I'm still playing it safe and using
ReaAccess, because I hate coming unstuck with company, so in that
context I'm still clinging to the workflows that've served me well for
the past couple of years. It's OSARA all the way now though when
working alone, and it won't be long before I'm confident enough with
it to be full time.

It's been a fair old while since accessibility in Reaper has had
future prospects. Enjoy.

Scott


On 3/3/15, Rusty Perez via RWP <rwp at bluegrasspals.com> wrote:
> Hi guys,
> Well, I'm diving in to Reaper.
> Just for background. I recorded a solo holiday project two years ago
> using an accessible multi-track recorder on Linux. while I love the
> idea of the freedom and availability of accessible software on Linux,
> it is clear that Reaper offers many more readily available features
> and it's a lot more accessible to the less technical--like myself--in
> more ways than just blind accessible. No disrespect meant in the least
> to the application I used before. I just think I can be more
> productive using Reaper.
>
>
> I have Reaper and reaccess which I installed last year.
> Is there ANY REASON to keep Reaccess on my system, or should I just
> ditch it and run with OSARA?
>
> thanks!
> Rusty
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp
>