[Rwp] OSARA, an open-source ReaAccess replacement in development

Thu Feb 5 01:37:29 EST 2015

I hope Jamie and I can converge our efforts  sooner than later, but both
projects are a labor of love and time, so you know how those go!

On Wed, Feb 4, 2015 at 4:49 AM, Scott Chesworth via RWP <
rwp at bluegrasspals.com> wrote:

> One thing to keep in mind is that the approach CakeTalking and JSonar
> both use loosely represents Sonars GUI. Bringing the same layout over
> to Reaper could probably be done, but it'd mean we were using a
> totally different layout to anyone who's using Reaper without a screen
> reader. I wouldn't be keen on this, mostly because there are people
> out there who use magnification alongside their screen reader, and
> they wouldn't know whether they were coming or going.
>
> On a vaguely related note, does anyone here make heavy use of that
> virtual view thingy you get when you press tab with a track or item
> selected? Personally I haven't ever seen the point of it, but I've
> never been sure whether that's because I'm being reluctant to use an
> alternative interface.
>
> On 2/4/15, Jayson Smith via RWP <rwp at bluegrasspals.com> wrote:
> > You won't get any argument from me on those points. Not to mention that
> > CakeTalking requires probably the most expensive screen reader on the
> > market, and unless something recent has happened, hasn't been updated in
> > a while, because of major changes made to Sonar itself. However, for my
> > DAW, that is what I use, but I always welcome alternatives. When Reaper
> > and ReaAccess first came on the scene, I played with it, but really
> > couldn't get into it. Hopefully that will change.
> > Jayson
> >
> > On 2/4/2015 7:13 AM, Hrvoje Katić via RWP wrote:
> >> Yep, but CakeTalking costs too much as well as Sonar. Reaper is far
> >> more cheap and accessibility solution is freeware.
> >>
> >>
> >>
> >> LP,
> >> Hrvoje
> >>
> >> Private email: hrvoje.katic at yandex.com <mailto:hrvoje.katic at yandex.com>
> >>
> >> Web site: Click here <http://hrvix.wordpress.com/>
> >>
> >> Facebook: Click here <http://www.facebook.com/hrvix>
> >>
> >> Twitter: Click here <http://www.twitter.com/hrvix>
> >>
> >> Skype Id: hrvojekatic
> >>
> >> Mobile: 095/585-7034
> >>
> >> 4.2.2015. u 13:04, Jayson Smith via RWP je napisao/la:
> >>> Hi,
> >>>
> >>> I, too, would be in favor of single-key commands for the most common
> >>> actions. Cake Talking for Sonar, which is for me the gold standard of
> >>> DAW accessibility, uses single-key commands for the most common
> >>> actions. Mute, solo, arm, etc. And it has a standard view where you
> >>> use up/down to move between tracks, and left/right to move between
> >>> parameters on a track such as name, mute, solo, arm, volume, pan, etc.
> >>>
> >>> Jayson
> >>>
> >>> On 2/4/2015 3:37 AM, Hrvoje Katić via RWP wrote:
> >>>> Well, personally I don't like default Reaper keymap. Some important
> >>>> actions are not assigned to any keystroke by default (move by beats
> >>>> and bars is a good example), and you have to hold control and alt
> >>>> while navigating tracks with up and down arrow, and also
> >>>> control+alt+arrow keys have a conflict with some graphics drivers
> >>>> where these keystrokes are assigned to rotate screen.
> >>>>
> >>>>
> >>>> LP,
> >>>> Hrvoje
> >>>>
> >>>> Private email: hrvoje.katic at yandex.com <mailto:
> hrvoje.katic at yandex.com>
> >>>>
> >>>> Web site: Click here <http://hrvix.wordpress.com/>
> >>>>
> >>>> Facebook: Click here <http://www.facebook.com/hrvix>
> >>>>
> >>>> Twitter: Click here <http://www.twitter.com/hrvix>
> >>>>
> >>>> Skype Id: hrvojekatic
> >>>>
> >>>> Mobile: 095/585-7034
> >>>>
> >>>> 4.2.2015. u 0:44, Zack Benton via RWP je napisao/la:
> >>>>> Agreed, I admit that the re access keymap is a bit harder to learn.
> >>>>> On 2/3/2015 18:16, James Teh via RWP wrote:
> >>>>>> Anyway, I didn't mean to start a debate on what is "best";
> >>>>>> everyone has their preferences. My point is that if even I (as the
> >>>>>> primary author) am using something different to the ReaAccess key
> >>>>>> map, I'd be very reluctant to include a ReaAccess based key map as
> >>>>>> the default. At the very least, that key map is harder to learn
> >>>>>> initially. This is why I haven't included a key map at all at this
> >>>>>> point. Perhaps we could include a ReaAccess key map as an option,
> >>>>>> but I'm reluctant to make it a "default".
> >>>>>>
> >>>>>> Jamie
> >>>>>>
> >>>>>> On 4/02/2015 7:19 AM, Scott Chesworth via RWP wrote:
> >>>>>>> I have alien length fingers, so this might not work for everyone,
> >>>>>>> but
> >>>>>>> I've found non-separated F keys a lot easier since I started
> >>>>>>> treating
> >>>>>>> them as an extra row rather than counting along them. The
> experience
> >>>>>>> is a little different from laptop to laptop, but with a wee bit of
> >>>>>>> practice to get the muscle memory locked in I can comfortably hit
> >>>>>>> mute, solo, arm, phase etc without leaving the touch typing
> position
> >>>>>>> or counting. This is coming from someone who fought pretty hard
> >>>>>>> against those keys being used for those functions in the first
> >>>>>>> place,
> >>>>>>> so I guess you could say I'm converted now.
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> 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/20150204/bcc12df1/attachment.html>