<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23515">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Incorrect.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Atleast in part.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Depends on the screen-reader you are using, Patrick
is right, certain things do not show up with nvda with later versions in that
master track area.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>I'll trust someone who actually does mixes and
works in this field </FONT></DIV>
<DIV><FONT size=2 face=Arial>and my own experiences rather than someone who
means well, butspends more time perusing forums and talking than doing, no
offense.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Yes, there are work arounds, but it's a reality
that the further we get away from 3.78, </FONT></DIV>
<DIV><FONT size=2 face=Arial>the more reaccess doesn't fit, but we need to move
forward, one of the main reasons is that vst window thing for plug-ins to have a
consistant interface.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>But some are choosing to play it safe,</FONT></DIV>
<DIV><FONT size=2 face=Arial>I teach this stuff and have 35 years under my belt,
so am not in the habbit of accept so called myths so anyone making strong
statements like that better get their facts straight.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=33indigo@charter.net href="mailto:33indigo@charter.net">Indigo</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=rwp@reaaccess.com
href="mailto:rwp@reaaccess.com">Reapers Without Peepers</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, September 11, 2013 2:15
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [RWP] Reaper Accessibility
Query from New User</DIV>
<DIV><BR></DIV>I have Reaper 4.5 on this 64 bit Windows 7 machine right
this second, <BR>and it behaves just like all the other previous versions
since those few <BR>changes at version 4.0.<BR>This ledgend that nothing
beyond version 3.78 works is taking on the <BR>proportions of a classic myth,
like the feats of Hercules or some such <BR>fictional epic.<BR>People are
repeating it without ever bothering to try current Reaper
<BR>versions.<BR>Beginning with version 4.0 the applications key would not
open the <BR>extended record options menu, as it had before.<BR>Within a few
weeks Roy Shtupler discovered that if you hold ctrl and <BR>press up arrow; 3
presses of up arrow works best for me; then the <BR>applications key displays
the record options menu as usual.<BR>A little further on in version 4, the
ReaAccess shortcut for displaying <BR>the inline midi editor quit
working.<BR>David Shortland soon discovered that you can use another Reaper
midi <BR>editor instead, which is a hundred times more complete and better
laid <BR>out than the inline midi editor ever was, so that broken shortcut
turned <BR>out to be a blessing in disguise.<BR>I'm sure there will be other
changes we will need to adapt to as Reaper <BR>is updated.<BR>You know,
sighted users also constantly adapt to updates in the latest <BR>Reaper, we're
not being singled out by God for dumping on, and needing <BR>to struggle
to learn new ways to survive; believe it or not.<BR>Indi<BR><BR><BR><BR><BR>On
9/10/2013 4:14 PM, Daveed Mandell wrote:<BR>> I like that approach very
'much. Is version 4.5 now usable at all for blind folks?
Thanks.<BR>><BR>> Daveed<BR>><BR>> ----- Original Message
-----<BR>> From: Indigo <<A
href="mailto:33indigo@charter.net">33indigo@charter.net</A>><BR>> To:
Reapers Without Peepers <<A
href="mailto:rwp@reaaccess.com">rwp@reaaccess.com</A>><BR>> Date:
Tuesday, September 10, 2013 8:11 am<BR>> Subject: Re: [RWP] Reaper
Accessibility Query from New User<BR>><BR>>><BR>>><BR>>>
Hi and welcome to the list.<BR>>> Some are using reaper daily now;
solving problems as we go.<BR>>><BR>>> Some of us are better at
audio recording and editing, and others of us<BR>>> like Reaper's
approach to midi recording and editing.<BR>>> Yes, there's no manual for
access yet, but RWP has an archive.<BR>>> When I encounter a problem I
google RWP and a few words describing the<BR>>> problem, and old emails
pop up that often have the same problem and its<BR>>>
solution.<BR>>> It's an each one teach one approach.<BR>>> Just
ask questions as they arise, and someone will likely know the<BR>>>
answer, or we might discover the solution together.<BR>>>
Indi<BR>>><BR>>><BR>>><BR>>> On 9/10/2013 8:13 AM,
Daveed Mandell wrote:<BR>>>>
Hello:<BR>>>><BR>>>> 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.<BR>>>><BR>>>>
Regards,<BR>>>><BR>>>> Daveed
Mandell<BR>>>><BR>>>><BR>>>><BR>>>>
_______________________________________________<BR>>>> RWP mailing
list<BR>> @> @> <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A><BR>>>> <A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A><BR>>>><BR>>><BR>>>
_______________________________________________<BR>>> RWP mailing
list<BR>> @> <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A><BR>>> <A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A><BR>><BR>><BR>><BR>>
_______________________________________________<BR>> RWP mailing
list<BR>> <A href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A><BR>>
<A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A><BR>><BR><BR>_______________________________________________<BR>RWP
mailing list<BR><A href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A><BR><A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A></BLOCKQUOTE></BODY></HTML>