<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=windows-1252" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23520">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>The second option makes more sense to me, it seems
so overkill to have to write a envelope all the way to the end of a track just
to keep the volume the same.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Well, I"m on reaper 4.5 now so will be
looking.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Yes some things are a bit flakier with reaccess,
but I want to get in on the bridged separate process vst window thing, and after
making sfz with autohotkey and seeing how much easier that was, I didn't even
have to change my window title name for triggering, it's a sacrifice I'll
make.</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=patrick@pdaudio.net href="mailto:patrick@pdaudio.net">Patrick
Perdue</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 8:01
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [RWP] Reaper Accessibility
Query from New User</DIV>
<DIV><BR></DIV>There are two ways to fix that. First, there is an action to
write <BR>current track envelope from cursor to the end of the project, and
there <BR>is another option somewhere in preferences (not enabled by default)
that <BR>doesn't reset to the previous value after a new envelope is created.
<BR>I'll be damned if I can remember what that's called now though.<BR>I
actually do like the default behavior for some things, so I've left it
<BR>there and use it in conjunction with the action I mentioned previously.
<BR>It's an extra step, but for the types of stuff I edit, it makes more
<BR>sense to do it that way most of the time.<BR>But yes, you can make this
thing happen by default. Someone on this list <BR>mentioned how to do it some
months back.<BR><BR>On 9/11/2013 8:42 PM, Chris Belle wrote:<BR>> I could
live with reaper's automation if they gave me an option to leave<BR>>
things where the hell I left them instead of insisting on popping back<BR>>
to original values.<BR>> I know some have said they like this, but I can't
stand it 'grin'.<BR>> So when I become a paying member, that'll be the
first thing I ask for<BR>> is a choice in this
matter.<BR>><BR>> ----- Original Message
-----<BR>> *From:* Patrick Perdue <<A
href="mailto:patrick@pdaudio.net">mailto:patrick@pdaudio.net</A>><BR>>
*To:* Reapers Without Peepers <<A
href="mailto:rwp@reaaccess.com">mailto:rwp@reaaccess.com</A>><BR>>
*Sent:* Wednesday, September 11, 2013 7:15 PM<BR>>
*Subject:* Re: [RWP] Reaper Accessibility Query from New
User<BR>><BR>> Well, if you have a control
surface, you can do some automation stuff.<BR>>
Editing the envelopes after they exist... yeah, that's a problem.
You<BR>> can do some really basic stuff with the
keyboard, I.E. track/master<BR>> track level or
master playrate change, which is all kinds of fun in
and<BR>> of itself. I've used a Korg Nanokontrol in
some projects as both a<BR>> control surface and a
basic button/knob box for controlling effect<BR>>
parameters. You can definitely get the basics done, but any more
than<BR>> that, and there are some huge gaps in
what can be manipulated, as there<BR>> is no way
that I know of to edit automation envelopes from a
keyboard<BR>> after they've been recorded. Easiest
just to trash and redo your<BR>> automation event,
sucky as that is.<BR>> I never figured out how to
automate track sends, so I've worked around<BR>>
that by sending a folder to a track, sending that track to
another<BR>> track<BR>>
with effects on it, routing post-fader, then automating the track
that<BR>> is sent to the effects. Not at all
efficient, and surely not necessary<BR>> if you can
see stuff.<BR>><BR>> I most often do the
split/item property change/overlap items thing
for<BR>> both panning and amplitude, because you
can get very precise with it<BR>>
and<BR>> it works. Unlike automation at present,
you can non-destructively do<BR>> stuff about that
once it's been implemented.<BR>><BR>> On
9/11/2013 8:06 PM, Chris Belle wrote:<BR>>
> Well, at least with item based editing in reaper, you don't mess
up<BR>> > anything. It bothers me that we
have to split audio to do things,<BR>> >
even though it works, and reaper's crossfades are very smooth,
it's<BR>> > still technically not cool to
have to tear apart your audio just to<BR>>
> do a little automation. Or get around, in other words, to
my<BR>> > engineer's head it's better to
bend it than break it, even if you can<BR>>
> fix it prety good. Just in midi, this concept will work
better,<BR>> > because it won't be
necessary to cross-fade broken audio events.
It's<BR>> > just a matter of grouping then
more than any physical changes to the<BR>>
> actual data. Item based midi editing, ok then , this will help,
the<BR>> > other shoe drops
'grin'.<BR>>
><BR>> > ----- Original Message -----
*From:* David P Shortland<BR>> > <<A
href="mailto:dragamilov@comcen.com.au">mailto:dragamilov@comcen.com.au</A>>
*To:* Reapers Without Peepers<BR>> >
<<A href="mailto:rwp@reaaccess.com">mailto:rwp@reaaccess.com</A>>
*Sent:* Wednesday, September 11, 2013
5:55<BR>> > PM *Subject:* Re: [RWP] Reaper
Accessibility Query from New User<BR>>
><BR>> > Hi & Greetings from Down
Under... Not as far as I have been abel
to<BR>> > discover.... It always seems to
start at the beginning of the Event<BR>> >
List... You can use Page Up & Page Down keys to jump 7 events at
a<BR>> > time... However, the work around
that I do for this one is if I need<BR>> >
to edit something that is say 16 bars into a Item.... I just do
a<BR>> > split just before the section I
wish to edit and Voila when the new<BR>> >
Item is opened you are right there... The more I use REAPER ...
the<BR>> > more I am getting to know how
this Item based Editing worx... ...and<BR>>
> liking it... It does not matter to me whether a Trak has One
Item,<BR>> > several items or several
thousand items,... at any given time you
can<BR>> > Glue all the Items together and
each part retains what you have<BR>> >
edited and you can start again... Also just as a quick mention,
which<BR>> > some of us may need to get
our heads around, is the concept of not<BR>>
> having a dedicated SubGroup area.... the flexibility that
REAPER<BR>> > allows by being able to put
anything anywhere and being able to
route<BR>> > anything to anywhere is
simply in a word ... NICE!!! Anyway...
on<BR>> > with the Editing... Kind regards
David P Shortland DragonScore<BR>> >
Productions *From:* Chris Belle <<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>>
*Sent:*<BR>> > Thursday, September 12,
2013 6:17 AM *To:* Reapers Without
Peepers<BR>> > <<A
href="mailto:rwp@reaaccess.com">mailto:rwp@reaaccess.com</A>> *Subject:*
Re: [RWP] Reaper Accessibility<BR>> >
Query from New User Hey, I have done that but is there an easy way
to<BR>> > move between midi events? I mean
you can move along the time line,<BR>> >
but in sonar it jumps through all the extra time and immediately
goes<BR>> > to the next midi event. Or do
you have to go to the exact place on<BR>>
> the time like for each midi event? That was one thing killing
me.<BR>>
><BR>> > ----- Original Message -----
*From:* David P Shortland<BR>> > <<A
href="mailto:dragamilov@comcen.com.au">mailto:dragamilov@comcen.com.au</A>>
*To:* Reapers Without Peepers<BR>> >
<<A href="mailto:rwp@reaaccess.com">mailto:rwp@reaaccess.com</A>>
*Sent:* Wednesday, September 11, 2013
2:45<BR>> > PM *Subject:* Re: [RWP] Reaper
Accessibility Query from New User Hi
&<BR>> > Greetings again from Down
Under<BR>>
><BR>> > Again, just a little addendum
to Indy's post...<BR>>
><BR>> > Once you have selected the
MIDI Item you wish to Edit Control plus<BR>>
> Alt plus E opens the MIDI Editor...<BR>>
><BR>> > You only need to do this once
but you need to go to the Options Menu<BR>>
> (I think) or it might be the View Menu...(apologies not sure
which)<BR>>
><BR>> > Select Event
List...<BR>>
><BR>> > You can scroll up and down the
Event List with the cursor keys<BR>>
><BR>> > When you want to Edit an Event
Focus on it and press Control plus F2<BR>>
><BR>> > This Opens the Event Item
Dialog and yu can TAB around and change<BR>>
> whatever you wish...<BR>>
><BR>> > No need to go to the Apply or
OK buttons just hit Enter when you<BR>> >
have finished your Edit...<BR>>
><BR>> > Kind
regards<BR>>
><BR>> > David P Shortland DragonScore
Productions<BR>>
><BR>>
><BR>>
><BR>>
><BR>> > -----Original Message-----
From: Indigo Sent: Wednesday, September<BR>>
> 11, 2013 8:52 PM To: Reapers Without Peepers Subject: Re:
[RWP]<BR>> > Reaper Accessibility Query
from New User<BR>>
><BR>> > I used those ancient midi
sequencers in dos or on the Atari ST; ,<BR>>
> like Voyettra Gold, Doctor T's Keyboard Midi Sequencer, all
totally<BR>> > accessible, just punching
in numbers, then I did midi from
hardware<BR>> > sequencers, from Yamaha
and the MMT8; then I edited midi from
Sonar<BR>> > versions 4, 6, 7 and 8.5.3,
and to me all editing at the event level<BR>>
> is the most tedious, most boring thing I could
imagine.<BR>>
><BR>> > I'd rather play in a passage a
dozen times until I get it just right<BR>>
> than chase down a single midi event and type in number values.
But,<BR>> > for those who don't mind, I
think Reaper's layout for getting at<BR>>
> notes and every single note event possible at tab and arrow
keys<BR>> > couldn't be more ideal. How
could it be easier than having
everything<BR>> > neately labeled and laid
out at the taband arrow keys; where you
can<BR>> > arrow to other note values, for
instance, or type in different<BR>> >
numbers for velocity, note length, pitch, program number, yada
yada<BR>> > yada? One thing to note is
that; when finished with editing;
you<BR>> > need to tab to apply, and then
hit enter; but there can be another<BR>> >
step that might or might not be required. At certain places,
you<BR>> > might need to find an OK button
that needs to be clicked; after<BR>> >
pressing enter on Apply takes you back to the track view; so look
out<BR>> > for that one. If anyone is not
hearing their changes of values being<BR>>
> applied to their music, go to your number pad and use your PC
cursor<BR>> > slash mouse pointer slash
object navigation to find that OK
button,<BR>> > then left click it. I'll go
search my collection and repost David<BR>>
> Shortland's method of reaching the midi editor. By the way,
since<BR>> > it's a different midi editor
than the inline editor that Ivan's<BR>> >
shortcut reached, maybe reaAccess is not doing anything to
assist<BR>> > with access of David's
midi editor, it's just screenreader
friendly<BR>> > because Reaper is written
that way, using Microsoft standard menus<BR>>
> and controls. Indi<BR>>
><BR>>
><BR>>
><BR>>
><BR>> > On 9/11/2013 4:51 AM, Scott
Chesworth wrote:<BR>> >> I'm really not
a MIDI type, but sure, a repost of
David's<BR>> > steps
is<BR>> >> bound to help
someone.<BR>>
>><BR>> >> Yeah, of course MIDI
is MIDI is MIDI from DAW to DAW, but I'd<BR>>
> wager<BR>> >> there would be neat
little tips and tricks people use to speed
up<BR>> >> editing which are specific
to each one. Sometimes, just watching<BR>>
>> someone else who's got a workflow down smashing through
a<BR>> > task can
be<BR>> >> quite
inspiring.<BR>>
>><BR>> >>
Scott<BR>>
>><BR>>
>><BR>> >> On 9/11/13, Indigo
<<A
href="mailto:33indigo@charter.net">33indigo@charter.net</A><BR>>
<<A
href="mailto:33indigo@charter.net">mailto:33indigo@charter.net</A>><BR>>
> <<A
href="mailto:33indigo@charter.net">mailto:33indigo@charter.net</A>>>
wrote:<BR>> >>> I'll dig out and
post the guide to bringing up the midi<BR>>
> editor, David<BR>> >>>
Shortland style, which is step-by-step to get inside
the<BR>> > midi
editor,<BR>> >>> right down to the
event list for each note of your music<BR>>
> along the<BR>> >>> timeline.
Anyone who has the least experience with editing
midi<BR>> >>>
events<BR>> > in
every<BR>> >>> sequencer or daw ever
made should know that midi is midi;<BR>> >
and it isn't<BR>> >>> different in a
different daw. Each event is clearly labeled
in<BR>> >>> Reaper, in plain
English,<BR>> > and if
you<BR>> >>> want to shorten or
lengthen a note length, or move the note<BR>>
> up or down a<BR>> >>> list of
chromatic notes, or shift it to another octave,
or<BR>> > alter
its<BR>> >>> velocity number, or
move the note's position on the<BR>> >
timeline, or a<BR>> >>> thousand
other editing details; duh, what's so hard
about<BR>> > that to
figure<BR>> >>> out? So, it's laid
out differently from Voyettra Gold, or
Sonar,<BR>> > or
ProTools,<BR>> >>> don't we all
expect that? It's good for the health of our
brain<BR>> >>> cells to
exercise<BR>> > them,
otherwise<BR>> >>> we get to be an
old dog that can't learn new tricks. When
all<BR>> >>> note events are clearly
labeled, all laid out very<BR>> >
conveniently<BR>> >>> at the tab
keys, with edit fields at the arrow keys,
what<BR>> > more
could<BR>> >>> anyone ever hope for
in access from a screenreader? Indi<BR>>
>>><BR>>
>>><BR>> >>> On 9/10/2013
8:15 PM, Scott Chesworth wrote:<BR>>
>>>> I've dropped Roy a line to see whether he'd have time
to<BR>> > share
some<BR>> >>>> wisdom. Just hit
on the idea of spending a bit of time<BR>>
> hanging out<BR>> >>>> with
each of the people on here that are using Reaper to
do<BR>> >
cool<BR>> >>>> stuff, whatever
their stuff may be. I'd interview them
and<BR>> > record
a<BR>> >>>> bit of them in action
for an hour at most, then handle all<BR>>
> the boring<BR>> >>>> editing
uploading headache stuff so they don't have
too.<BR>> > Seems like
if<BR>> >>>> enough people are
keen to be featured it'd make a neat<BR>>
> little podcast<BR>> >>>>
series. I could justify putting the time into it seeing
as<BR>> > I'd
no<BR>> >>>> doubt learn a bunch
of stuff along the way.<BR>>
>>>><BR>> >>>> Let's
see what happens. First time I've been excited
about<BR>> > Reaper in
a<BR>> >>>> while, so I hope the
response from Roy is positive so I can<BR>>
> strike<BR>> >>>> while the
iron is hot here.<BR>>
>>>><BR>> >>>>
Scott<BR>>
>>>><BR>> >>>> On
9/11/13, Chris Belle <<A
href="mailto:cb1963@sbcglobal.net">cb1963@sbcglobal.net</A><BR>>
<<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>><BR>>
> <<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>>>
wrote:<BR>> >>>>> Roy seems to
have a leg up on some of the things we
don't,<BR>> > bet
he'd<BR>> >>>>> help out if we
approached him with a few clams.<BR>>
>>>>><BR>>
>>>>><BR>>
>>>>> ----- Original Message ----- From: Goldfinga Productions
To:<BR>> >>>>> Reapers Without
Peepers Sent: Tuesday, September 10,
2013<BR>> >>>>> 5:28 PM
Subject: Re: [RWP] Reaper Accessibility Query
from<BR>> >>>>>
New<BR>> >
User<BR>>
>>>>><BR>>
>>>>><BR>>
>>>>> ah, well that is a hole new animal… I can do some of
it,<BR>> > but
I<BR>> >>>>> would like to
better edit stuff. Is there a person
doing<BR>> >>>>>
this<BR>> > already? Are
they<BR>> >>>>> giving
lessons? lol<BR>>
>>>>><BR>>
>>>>><BR>>
>>>>> On Sep 10, 2013, at 5:16 PM, "Chris
Belle"<BR>> > <<A
href="mailto:cb1963@sbcglobal.net">cb1963@sbcglobal.net</A> <<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>><BR>>
<<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>>><BR>>
>>>>> wrote:<BR>>
>>>>><BR>>
>>>>>> I mean doing detailed editing and
such.<BR>>
>>>>>><BR>>
>>>>>> Are you down with that, I can load up and play
midi<BR>> > and
such,<BR>> >>>>> but detailed
editing and nudging notes and doing
transforms<BR>> >>>>>
or<BR>> > search
and<BR>> >>>>> replace like
the interpolate dialogue in sonar, that
sort<BR>> > of
stuff.<BR>>
>>>>>><BR>>
>>>>>><BR>>
>>>>>> ----- Original Message ----- From: Goldfinga
Productions<BR>> >>>>>> To:
Reapers Without Peepers Sent: Tuesday, September
10,<BR>> >>>>>> 2013 3:44
PM Subject: Re: [RWP] Reaper Accessibility
Query<BR>> >>>>>>
from<BR>> > New
User<BR>>
>>>>>><BR>>
>>>>>> I use midi all the time with reaper… That's why I
have been<BR>> >>>>>> all
over poise, that's one<BR>> > less piece
of<BR>> >>>>> hardware that I
have to hook up to the mixer. Now I can
leave<BR>> >>>>>
my<BR>> > npc at
the<BR>> >>>>> church.
lol.<BR>>
>>>>>><BR>>
>>>>>><BR>>
>>>>>> On Sep 10, 2013, at 4:41 PM, "Chris
Belle"<BR>> > <<A
href="mailto:cb1963@sbcglobal.net">cb1963@sbcglobal.net</A> <<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>><BR>>
<<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>>><BR>>
>>>>> wrote:<BR>>
>>>>>><BR>>
>>>>>>> yeh, reaper isn't where sonar is but definitely
useable,<BR>> >>>>>>>
especially with straight audio.<BR>>
>>>>>>><BR>>
>>>>>>> We're all gonna have to flip Roy a few
sheckles<BR>> > and get him
to<BR>> >>>>> show us how he
does midi with reaper,<BR>>
>>>>>>> I just ain't figured it out
yet.<BR>>
>>>>>>><BR>>
>>>>>>> I mean I can do basics load a osft synth and
hit<BR>> > the
midi<BR>> >>>>>
editor,<BR>> >>>>>>> and
see some events and such, but it ain't<BR>>
> anything like sonar<BR>>
>>>>> and there are no
docs,<BR>>
>>>>>>><BR>>
>>>>>>> We desperately need some serious docs shoing how
to do<BR>> >>>>>
everything.<BR>>
>>>>>>><BR>>
>>>>>>><BR>>
>>>>>>> ----- Original Message ----- From: Goldfinga
Productions<BR>> >>>>>>>
To: Reapers Without Peepers Sent: Tuesday, September
10,<BR>> >>>>>>> 2013
3:34 PM Subject: Re: [RWP] Reaper
Accessibility<BR>>
>>>>>>> Query from<BR>>
> New User<BR>>
>>>>>>><BR>>
>>>>>>> That's exactly where I was going with that. lol.
I<BR>> > use
reaper,<BR>> >>>>> hell, like
I said in my last message, I paid for
it.<BR>>
>>>>>>><BR>>
>>>>>>> On Sep 10, 2013, at 4:25 PM, "Chris
Belle"<BR>> >>>>> <<A
href="mailto:cb1963@sbcglobal.net">cb1963@sbcglobal.net</A> <<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>><BR>>
<<A
href="mailto:cb1963@sbcglobal.net">mailto:cb1963@sbcglobal.net</A>>>
wrote:<BR>>
>>>>>>><BR>>
>>>>>>>> I think GF was being
humorous.<BR>>
>>>>>>>><BR>>
>>>>>>>> I took it that way
anyhow.<BR>>
>>>>>>>><BR>>
>>>>>>>> Kind of how we get the shaft and the end of
the<BR>> >
line<BR>> >>>>> everywhere in
the world and have to fight like dogs to
not<BR>> >>>>> get left
out,<BR>> >>>>>>>>
but you know how it works in this world,
money<BR>> > talks
and<BR>> >>>>> bullshit
walks.<BR>>
>>>>>>>><BR>>
>>>>>>>> If there were 20 million blind reaper
users<BR>> > ready to
buy<BR>> >>>>> access would be
here next week 'grin'.<BR>>
>>>>>>>><BR>>
>>>>>>>> For now we just have to cowboy up and do
the<BR>> > best we
can.<BR>>
>>>>>>>><BR>>
>>>>>>>><BR>>
>>>>>>>> ----- Original Message ----- From: Scott
Chesworth To:<BR>>
>>>>>>>> Reapers Without Peepers Sent: Tuesday,
September 10,<BR>>
>>>>>>>> 2013 1:10 PM Subject: Re: [RWP] Reaper
Accessibility<BR>>
>>>>>>>> Query<BR>>
> from New User<BR>>
>>>>>>>><BR>>
>>>>>>>> Couple of points to keep in mind before you
dig<BR>> > too deep
into<BR>> >>>>>
slating<BR>> >>>>>>>>
the Reaper developers in public...<BR>>
>>>>>>>><BR>>
>>>>>>>> They are aware that a visually impaired
userbase<BR>> > exists,
and<BR>> >>>>>
have<BR>> >>>>>>>>
gradually been exposing GUI elements over time.
If<BR>> > you
need<BR>> >>>>> proof
of<BR>> >>>>>>>>
that, do some mousing around in Reaper on PC
and<BR>> > see how
much<BR>> >>>>>
NVDA<BR>> >>>>>>>>
tells you, or compare how much is visible
with<BR>> > VoiceOver
on<BR>> >>>>> Mac
now<BR>> >>>>>>>>
against a version from a couple years back.
API<BR>> > bugs
that<BR>> >>>>>
impacted<BR>>
>>>>>>>> upon ReaAccess were fixed, and there have
been a<BR>> > couple
of<BR>> >>>>>
instances<BR>>
>>>>>>>> where accessibility gets a mention in
the<BR>> > changelogs.
A<BR>> >>>>> couple
of<BR>> >>>>>>>>
people with decent track records of getting
stuff<BR>> > done are
in<BR>> >>>>>
contact<BR>> >>>>>>>>
with Justin the lead developer, all be
it<BR>> >>>>>>>>
sporadically.<BR>> >>>>>
They're not<BR>>
>>>>>>>> shouting from the rooftops about that, but
when<BR>> > the
progress<BR>> >>>>> comes,
it<BR>> >>>>>>>>
happens in fits and starts and has been largely
due<BR>> > to
nudges<BR>> >>>>>
and<BR>> >>>>>>>>
guidance from these key people. I think it's fair
to<BR>> > say
that<BR>> >>>>>
Cockos<BR>> >>>>>>>>
have demonstrated that they're happy to help,
but<BR>> > they
need<BR>> >>>>>
guidance<BR>>
>>>>>>>> and it needs to fit around their
existing<BR>> > roadmap. I
think<BR>> >>>>> it's
pretty<BR>> >>>>>>>>
unfair to say we've been shafted. If you must find
a<BR>> > home
for<BR>> >>>>>
that<BR>> >>>>>>>>
accusation, Ivan's your man. Tell him who sent
you<BR>> >>>>>>>>
lol.<BR>>
>>>>>>>><BR>>
>>>>>>>> Is the future certain? No. Then again, are
their<BR>> > other
DAW<BR>> >>>>>
developers<BR>>
>>>>>>>> showing markedly less interest? You
betcha.<BR>>
>>>>>>>><BR>>
>>>>>>>> Nice idea re the NVDA team. Last time
I<BR>> > approached
Jamie<BR>> >>>>> about
Reaper<BR>> >>>>>>>>
he was up to his ears in Sonar as his pet
project,<BR>> > but
who<BR>> >>>>>
knows,<BR>> >>>>>>>>
someone else might have better luck catching him
at<BR>> > the
right<BR>> >>>>>
time.<BR>>
>>>>>>>><BR>>
>>>>>>>> Scott<BR>>
>>>>>>>><BR>>
>>>>>>>><BR>>
>>>>>>>> On 9/10/13, Goldfinga
Productions<BR>> > <<A
href="mailto:goldfingas@gmail.com">goldfingas@gmail.com</A> <<A
href="mailto:goldfingas@gmail.com">mailto:goldfingas@gmail.com</A>><BR>>
<<A
href="mailto:goldfingas@gmail.com">mailto:goldfingas@gmail.com</A>>><BR>>
>>>>> wrote:<BR>>
>>>>>>>>> Glad I could brighten your day with that
one. lol.<BR>>
>>>>>>>>><BR>>
>>>>>>>>> On Sep 10, 2013, at 9:18 AM, Keith
Hinton<BR>> >>>>> <<A
href="mailto:keithint1234@gmail.com">keithint1234@gmail.com</A> <<A
href="mailto:keithint1234@gmail.com">mailto:keithint1234@gmail.com</A>><BR>>
<<A
href="mailto:keithint1234@gmail.com">mailto:keithint1234@gmail.com</A>>><BR>>
>>>>> wrote:<BR>>
>>>>>>>>><BR>>
>>>>>>>>>> Muhahahahahahahhahaha! Cock OS! Oh
dear! LOL<BR>> > Okay,
I'll<BR>> >>>>> stop
laughing<BR>>
>>>>>>>>>> now. But yeah, I think we've got it
for sure.<BR>>
>>>>>>>>>><BR>>
>>>>>>>>>> On 9/10/13, Goldfinga
Productions<BR>> > <<A
href="mailto:goldfingas@gmail.com">goldfingas@gmail.com</A> <<A
href="mailto:goldfingas@gmail.com">mailto:goldfingas@gmail.com</A>><BR>>
<<A
href="mailto:goldfingas@gmail.com">mailto:goldfingas@gmail.com</A>>><BR>>
>>>>> wrote:<BR>>
>>>>>>>>>>> Remember folks, the developers of
reaper<BR>> > call them
selves<BR>> >>>>> "cockos."
If<BR>>
>>>>>>>>>>> you break that down, it spells
"cock OS." lol. I<BR>> > think we
got<BR>> >>>>> the shaft
on<BR>>
>>>>>>>>>>> this
one.<BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>> On Sep 10, 2013, at 8:37 AM,
Keith Hinton<BR>> >>>>> <<A
href="mailto:keithint1234@gmail.com">keithint1234@gmail.com</A> <<A
href="mailto:keithint1234@gmail.com">mailto:keithint1234@gmail.com</A>><BR>>
<<A
href="mailto:keithint1234@gmail.com">mailto:keithint1234@gmail.com</A>>><BR>>
>>>>>>>>>>>
wrote:<BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>>> I can tel you, despite being
new myself,<BR>> > that
yes,<BR>> >>>>> ReaAccess
has<BR>>
>>>>>>>>>>>> always been (basicly) the
accessibility<BR>> > pathway
for<BR>> >>>>> screen readers
to<BR>>
>>>>>>>>>>>> interface to Reaper. The
development has die<BR>>
>>>>>>>>>>>> out-last update
was<BR>> > in
2010.<BR>>
>>>>>>>>>>>> A few folks have been able to
use Reaper 4<BR>> >
with<BR>> >>>>> ReaAccess
just<BR>>
>>>>>>>>>>>> fine-looking up workarounds
for things etc,<BR>> > but as
I<BR>> >>>>> understand
it<BR>>
>>>>>>>>>>>> your largely on your own with
Reaper anyways.<BR>>
>>>>>>>>>>>> Without ReaAccess, I do not
believe any native<BR>> >>>>>
accessibility exists in<BR>>
>>>>>>>>>>>> Reaper itself. However,
again, I could be<BR>>
>>>>>>>>>>>> utterly wrong. If others
could reply to this<BR>>
>>>>>>>>>>>> new
users<BR>> > question
as<BR>> >>>>> well, that
might<BR>>
>>>>>>>>>>>> help-but I believe I've
answered it.<BR>>
>>>>>>>>>>>><BR>>
>>>>>>>>>>>><BR>>
>>>>>>>>>>>> On 9/10/13, Daveed
Mandell<BR>> > <<A
href="mailto:daveedm@sbcglobal.net">daveedm@sbcglobal.net</A> <<A
href="mailto:daveedm@sbcglobal.net">mailto:daveedm@sbcglobal.net</A>><BR>>
<<A
href="mailto:daveedm@sbcglobal.net">mailto:daveedm@sbcglobal.net</A>>><BR>>
>>>>> wrote:<BR>>
>>>>>>>>>>>>>
Hello:<BR>>
>>>>>>>>>>>>><BR>>
>>>>>>>>>>>>> What is the status of
Reaper accessibility<BR>> > right now?
I<BR>> >>>>>
understand<BR>>
>>>>>>>>>>>>> that Reaper's developers
have shown little<BR>>
>>>>>>>>>>>>>
or<BR>> > no interest
in<BR>> >>>>> making
the<BR>>
>>>>>>>>>>>>> software accessible, and
that accessibility<BR>>
>>>>>>>>>>>>> has
been<BR>> >
provided<BR>> >>>>> through
a<BR>>
>>>>>>>>>>>>> separate bridfe produced
by blind people<BR>>
>>>>>>>>>>>>> working
from<BR>> > this
list<BR>> >>>>> and website.
I<BR>>
>>>>>>>>>>>>> also understand that the
website itself<BR>>
>>>>>>>>>>>>>
isn't<BR>> >
functioning<BR>> >>>>> anymore
due to<BR>>
>>>>>>>>>>>>> problems related to spam.
At any rate, is the<BR>>
>>>>>>>>>>>>>
latest<BR>> > version
of<BR>> >>>>> Reaper,
version<BR>>
>>>>>>>>>>>>> 4.5, accessible for blind
folks? It is<BR>> > interesting to
note<BR>> >>>>> the
difference<BR>>
>>>>>>>>>>>>> in attitude between the
developers of<BR>>
>>>>>>>>>>>>>
Reaper,<BR>> > versus
the<BR>> >>>>> developers
of<BR>>
>>>>>>>>>>>>> the free Audacity audio
software, who have<BR>>
>>>>>>>>>>>>> been
very<BR>> >>>>>
conscientiously<BR>>
>>>>>>>>>>>>> integrating accessibility
into the software.<BR>>
>>>>>>>>>>>>> Thanks
for<BR>> > any
updates<BR>> >>>>>
and<BR>>
>>>>>>>>>>>>> information regarding
Reaper accessibility.<BR>>
>>>>>>>>>>>>><BR>>
>>>>>>>>>>>>>
Regards,<BR>>
>>>>>>>>>>>>><BR>>
>>>>>>>>>>>>> Daveed
Mandell<BR>>
>>>>>>>>>>>>><BR>>
>>>>>>>>>>>>><BR>>
>>>>>>>>>>>>><BR>>
>>>>>>>>>>>>>
_______________________________________________<BR>>
><BR>>
>>>>>>>>>>>>><BR>>
>>>>>>>>>>>> RWP mailing
list<BR>>
>>>>>>>>>>>>> <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>>>>>>><BR>>
> <A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A><BR>>
>>>>>>>>>>>>><BR>>
>>>>>>>>>>>><BR>>
>>>>>>>>>>>><BR>>
>>>>>>>>>>>> --
Sincerely,<BR>>
>>>>>>>>>>>><BR>>
>>>>>>>>>>>> Keith Home Phone:
928-554-3936 Mobile Phone:<BR>>
>>>>>>>>>>>> 928-713-6370 Primary
email:<BR>>
>>>>>>>>>>>> <A
href="mailto:keithint1234@gmail.com">keithint1234@gmail.com</A> <<A
href="mailto:keithint1234@gmail.com">mailto:keithint1234@gmail.com</A>><BR>>
> <<A
href="mailto:keithint1234@gmail.com">mailto:keithint1234@gmail.com</A>><BR>>
>>>>>>>>>>>><BR>>
>>>>>>>>>>>>
_______________________________________________<BR>>
><BR>>
>>>>>>>>>>>><BR>>
>>>>>>>>>>> RWP mailing
list<BR>>
>>>>>>>>>>>> <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>>>>>><BR>>
> <A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A><BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>>
GF<BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>> Check me out on
twitter<BR>>
>>>>>>>>>>> <A
href="http://www.twitter.com/goldfingas">http://www.twitter.com/goldfingas</A><BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>>>
_______________________________________________<BR>>
>>>>>>>>>>> RWP mailing list <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>>>>> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>>>>><BR>>
> <A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A><BR>>
>>>>>>>>>>><BR>>
>>>>>>>>>><BR>>
>>>>>>>>>><BR>>
>>>>>>>>>> --
Sincerely,<BR>>
>>>>>>>>>><BR>>
>>>>>>>>>> Keith Home Phone: 928-554-3936 Mobile
Phone:<BR>>
>>>>>>>>>> 928-713-6370 Primary email: <A
href="mailto:keithint1234@gmail.com">keithint1234@gmail.com</A><BR>>
<<A
href="mailto:keithint1234@gmail.com">mailto:keithint1234@gmail.com</A>><BR>>
> <<A
href="mailto:keithint1234@gmail.com">mailto:keithint1234@gmail.com</A>><BR>>
>>>>>>>>>><BR>>
>>>>>>>>>>
_______________________________________________
RWP<BR>>
>>>>>>>>>> mailing list <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>>>> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>>>><BR>>
> <A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A><BR>>
>>>>>>>>><BR>>
>>>>>>>>><BR>>
>>>>>>>>> GF<BR>>
>>>>>>>>><BR>>
>>>>>>>>> Check me out on
twitter<BR>>
>>>>>>>>> <A
href="http://www.twitter.com/goldfingas">http://www.twitter.com/goldfingas</A><BR>>
>>>>>>>>><BR>>
>>>>>>>>><BR>>
>>>>>>>>><BR>>
>>>>>>>>>
_______________________________________________
RWP<BR>> >>>>>>>>>
mailing list <A href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>>> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>>><BR>>
> <A
href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</A><BR>>
>>>>>>>>><BR>>
>>>>>>>><BR>>
>>>>>>>>
_______________________________________________
RWP<BR>> >>>>>>>>
mailing list <A href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>> <<A
href="mailto:RWP@reaaccess.com">mailto: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 <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>>> <<A
href="mailto:RWP@reaaccess.com">mailto: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>>
>>>>>>> GF<BR>>
>>>>>>><BR>>
>>>>>>> Check me out on
twitter<BR>> >>>>>>> <A
href="http://www.twitter.com/goldfingas">http://www.twitter.com/goldfingas</A><BR>>
>>>>>>><BR>>
>>>>>>><BR>>
>>>>>>><BR>>
>>>>>>> _______________________________________________
RWP<BR>> >>>>>>> mailing
list <A href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>> <<A
href="mailto:RWP@reaaccess.com">mailto: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>>
>>>>>>> _______________________________________________
RWP<BR>> >>>>>>> mailing
list <A href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
>>>>>>> <<A
href="mailto:RWP@reaaccess.com">mailto: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>>
>>>>>> GF<BR>>
>>>>>><BR>>
>>>>>> Check me out on twitter <A
href="http://www.twitter.com/goldfingas">http://www.twitter.com/goldfingas</A><BR>>
>>>>>><BR>>
>>>>>><BR>>
>>>>>><BR>>
>>>>>> _______________________________________________ RWP
mailing<BR>> >>>>>> list <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto: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>>
>>>>>> _______________________________________________ RWP
mailing<BR>> >>>>>> list <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto: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>>
>>>>> GF<BR>>
>>>>><BR>>
>>>>> Check me out on twitter <A
href="http://www.twitter.com/goldfingas">http://www.twitter.com/goldfingas</A><BR>>
>>>>><BR>>
>>>>><BR>>
>>>>><BR>>
>>>>> _______________________________________________ RWP
mailing<BR>> >>>>> list <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto: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>> >>>>
_______________________________________________ RWP
mailing<BR>> >>>> list <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto: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>> >>>
_______________________________________________ RWP mailing
list<BR>> >>> <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto: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>> >>
_______________________________________________ RWP mailing
list<BR>> >> <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto: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>> >
_______________________________________________ RWP mailing
list<BR>> > <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto: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>> >
_______________________________________________ RWP mailing
list<BR>> > <A
href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A> <<A
href="mailto:RWP@reaaccess.com">mailto:RWP@reaaccess.com</A>><BR>>
<<A
href="mailto:RWP@reaaccess.com">mailto: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>>
><BR>>
_______________________________________________<BR>>
> RWP mailing list <A href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</A>
<<A
href="mailto:RWP@reaaccess.com">mailto: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> <<A
href="mailto:RWP@reaaccess.com">mailto: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> <<A
href="mailto:RWP@reaaccess.com">mailto: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> <<A
href="mailto:RWP@reaaccess.com">mailto: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>_______________________________________________<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>