[RWP] Reaper Accessibility Query from New User

Tue Sep 10 16:41:42 EDT 2013

yeh, reaper
isn't where sonar is but definitely useable,
especially with straight audio.

We're all gonna have to flip Roy a few sheckles and get him to show us how he does midi with reaper,
I just ain't figured it out yet.

I mean I can do basics load a osft synth and hit the midi editor,
and see some events and such, but it ain't anything like sonar and there are no docs,

We desperately need some serious docs shoing how to do everything.

  ----- Original Message ----- 
  From: Goldfinga Productions 
  To: Reapers Without Peepers 
  Sent: Tuesday, September 10, 2013 3:34 PM
  Subject: Re: [RWP] Reaper Accessibility Query from New User

  That's exactly where I was going with that. lol. I use reaper, hell, like I said in my last message, I paid for it. 

  On Sep 10, 2013, at 4:25 PM, "Chris Belle" <cb1963 at sbcglobal.net> wrote:

  > I think GF was being humorous.
  >  
  > I took it that way anyhow.
  >  
  > Kind of how we get the shaft and the end of the line everywhere in the world and have to fight like dogs to not get left out,
  > but you know how it works in this world, money talks and bullshit walks.
  >  
  > If there were 20 million blind reaper users ready to buy access would be here next week 'grin'.
  >  
  > For now we just have to cowboy up and do the best we can.
  >  
  >  
  > ----- Original Message -----
  > From: Scott Chesworth
  > To: Reapers Without Peepers
  > Sent: Tuesday, September 10, 2013 1:10 PM
  > Subject: Re: [RWP] Reaper Accessibility Query from New User
  > 
  > Couple of points to keep in mind before you dig too deep into slating
  > the Reaper developers in public...
  > 
  > They are aware that a visually impaired userbase exists, and have
  > gradually been exposing GUI elements over time. If you need proof of
  > that, do some mousing around in Reaper on PC and see how much NVDA
  > tells you, or compare how much is visible with VoiceOver on Mac now
  > against a version from a couple years back. API bugs that impacted
  > upon ReaAccess were fixed, and there have been a couple of instances
  > where accessibility gets a mention in the changelogs. A couple of
  > people with decent track records of getting stuff done are in contact
  > with Justin the lead developer, all be it sporadically. They're not
  > shouting from the rooftops about that, but when the progress comes, it
  > happens in fits and starts and has been largely due to nudges and
  > guidance from these key people. I think it's fair to say that Cockos
  > have demonstrated that they're happy to help, but they need guidance
  > and it needs to fit around their existing roadmap. I think it's pretty
  > unfair to say we've been shafted. If you must find a home for that
  > accusation, Ivan's your man. Tell him who sent you lol.
  > 
  > Is the future certain? No. Then again, are their other DAW developers
  > showing markedly less interest? You betcha.
  > 
  > Nice idea re the NVDA team. Last time I approached Jamie about Reaper
  > he was up to his ears in Sonar as his pet project, but who knows,
  > someone else might have better luck catching him at the right time.
  > 
  > Scott
  > 
  > 
  > On 9/10/13, Goldfinga Productions <goldfingas at gmail.com> wrote:
  > > Glad I could brighten your day with that one. lol.
  > >
  > > On Sep 10, 2013, at 9:18 AM, Keith Hinton <keithint1234 at gmail.com> wrote:
  > >
  > >> Muhahahahahahahhahaha! Cock OS! Oh dear! LOL Okay, I'll stop laughing
  > >> now.
  > >> But yeah, I think we've got it for sure.
  > >>
  > >> On 9/10/13, Goldfinga Productions <goldfingas at gmail.com> wrote:
  > >>> Remember folks, the developers of reaper call them selves "cockos." If
  > >>> you
  > >>> break that down, it spells "cock OS." lol. I think we got the shaft on
  > >>> this
  > >>> one.
  > >>>
  > >>>
  > >>>
  > >>> On Sep 10, 2013, at 8:37 AM, Keith Hinton <keithint1234 at gmail.com>
  > >>> wrote:
  > >>>
  > >>>> I can tel you, despite being new myself, that yes, ReaAccess has
  > >>>> always been (basicly) the accessibility pathway for screen readers to
  > >>>> interface to Reaper.
  > >>>> The development has die out-last update was in 2010.
  > >>>> A few folks have been able to use Reaper 4 with ReaAccess just
  > >>>> fine-looking up workarounds for things etc, but as I understand it
  > >>>> your largely on your own with Reaper anyways.
  > >>>> Without ReaAccess, I do not believe any native accessibility exists in
  > >>>> Reaper itself.
  > >>>> However, again, I could be utterly wrong.
  > >>>> If others could reply to this new users question as well, that might
  > >>>> help-but I believe I've answered it.
  > >>>>
  > >>>>
  > >>>> On 9/10/13, Daveed Mandell <daveedm at sbcglobal.net> wrote:
  > >>>>> Hello:
  > >>>>>
  > >>>>> What is the status of Reaper accessibility right now? I understand
  > >>>>> that
  > >>>>> Reaper's developers have shown little or no interest in making the
  > >>>>> software
  > >>>>> accessible, and that accessibility has been provided through a
  > >>>>> separate
  > >>>>> bridfe produced by blind people working from this list and website. I
  > >>>>> also
  > >>>>> understand that the website itself isn't functioning anymore due to
  > >>>>> problems
  > >>>>> related to spam. At any rate, is the latest version of Reaper, version
  > >>>>> 4.5,
  > >>>>> accessible for blind folks? It is interesting to note the difference
  > >>>>> in
  > >>>>> attitude between the developers of Reaper, versus the developers of
  > >>>>> the
  > >>>>> free
  > >>>>> Audacity audio software, who have been very conscientiously
  > >>>>> integrating
  > >>>>> accessibility into the software. Thanks for any updates and
  > >>>>> information
  > >>>>> regarding Reaper accessibility.
  > >>>>>
  > >>>>> Regards,
  > >>>>>
  > >>>>> Daveed Mandell
  > >>>>>
  > >>>>>
  > >>>>>
  > >>>>> _______________________________________________
  > >>>>> RWP mailing list
  > >>>>> RWP at reaaccess.com
  > >>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
  > >>>>>
  > >>>>
  > >>>>
  > >>>> --
  > >>>> Sincerely,
  > >>>>
  > >>>> Keith
  > >>>> Home Phone:
  > >>>> 928-554-3936
  > >>>> Mobile Phone:
  > >>>> 928-713-6370
  > >>>> Primary email:
  > >>>> keithint1234 at gmail.com
  > >>>>
  > >>>> _______________________________________________
  > >>>> RWP mailing list
  > >>>> RWP at reaaccess.com
  > >>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
  > >>>
  > >>>
  > >>> GF
  > >>>
  > >>> Check me out on twitter
  > >>> http://www.twitter.com/goldfingas
  > >>>
  > >>>
  > >>>
  > >>> _______________________________________________
  > >>> RWP mailing list
  > >>> RWP at reaaccess.com
  > >>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
  > >>>
  > >>
  > >>
  > >> --
  > >> Sincerely,
  > >>
  > >> Keith
  > >> Home Phone:
  > >> 928-554-3936
  > >> Mobile Phone:
  > >> 928-713-6370
  > >> Primary email:
  > >> keithint1234 at gmail.com
  > >>
  > >> _______________________________________________
  > >> RWP mailing list
  > >> RWP at reaaccess.com
  > >> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
  > >
  > >
  > > GF
  > >
  > > Check me out on twitter
  > > http://www.twitter.com/goldfingas
  > >
  > >
  > >
  > > _______________________________________________
  > > RWP mailing list
  > > RWP at reaaccess.com
  > > http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
  > >
  > 
  > _______________________________________________
  > RWP mailing list
  > RWP at reaaccess.com
  > http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
  > _______________________________________________
  > RWP mailing list
  > RWP at reaaccess.com
  > http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com

  GF

  Check me out on twitter
  http://www.twitter.com/goldfingas

  _______________________________________________
  RWP mailing list
  RWP at reaaccess.com
  http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bluegrasspals.com/pipermail/rwp/attachments/20130910/334e7817/attachment.html>