<!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.18702">
<STYLE></STYLE>
</HEAD>
<BODY dir=ltr bgColor=#ffffff>
<DIV><FONT size=2 face=Arial>Right. It might be that you are juhst earing
the abrupt change on gain. Any time the gain changes abruptly, you'll hear
that as a click, or a pulse. But, isn't there across fade time that you
can specify when going between items? I'm sure their is. That should
solve those issues.</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=cb1963@sbcglobal.net href="mailto:cb1963@sbcglobal.net">Chris
Belle</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 10:39
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [RWP] Reaper Accessibility
Query from New User</DIV>
<DIV><BR></DIV>
<DIV><FONT size=2 face=Arial>Well, for some reason even though reaper does a
nice job of playing back,</FONT></DIV>
<DIV><FONT size=2 face=Arial>split items especially if you use the z to get 0
crossings, it still sounds split in some cases, if you push amplitude
changes too far, where as automation doesn't.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>But for most practical purposes, it amounts to
the same thing and doesn't matter.</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=Snowman@SnowmanRadio.com href="mailto:Snowman@SnowmanRadio.com">Jim
Snowbarger</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:53 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [RWP] Reaper Accessibility
Query from New User</DIV>
<DIV><BR></DIV>
<DIV><FONT size=2 face=Arial>My guess is that, when you split an audio item,
nothing actually happens to the signal. An item is just a set of
control parameters, And, if two adjacent items refer to adjacent parts
of the audio file, I but there isn't even any cross fading going on.
It's like me telling you to count from 1 to 3, and then count from 4 to
10. I wont' hear you jump from 3 to 4. Your brain will
concatenate automatically, and you'll count from 1 to 10, and I'll believe
you.</FONT></DIV>
<DIV><FONT size=2 face=Arial>The only down side is the need to press
control+right Arrow more times to get anywhere. But, hey.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></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=cb1963@sbcglobal.net href="mailto:cb1963@sbcglobal.net">Chris
Belle</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
7:06 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [RWP] Reaper
Accessibility Query from New User</DIV>
<DIV><BR></DIV>
<DIV><FONT size=2 face=Arial>Well, at least with item based editing in
reaper, you don't mess up anything.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>It bothers me that we have to split audio to
do things, even though it works, and reaper's crossfades are very smooth,
it's still technically not cool to have to tear apart your audio just to
do a little automation.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Or get around, in other words, to my
engineer's head it's better to bend it than break it, even if you can fix
it prety good.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Just in midi, this concept will work better,
because it won't be necessary to cross-fade broken audio
events.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>It's just a matter of grouping then more than
any physical changes to the actual data.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Item based midi editing, ok then , this will
help, the other shoe drops 'grin'.</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=dragamilov@comcen.com.au
href="mailto:dragamilov@comcen.com.au">David P Shortland</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
5:55 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [RWP] Reaper
Accessibility Query from New User</DIV>
<DIV><BR></DIV>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>Hi & Greetings from Down Under...</DIV>
<DIV> </DIV>
<DIV>Not as far as I have been abel to discover....</DIV>
<DIV> </DIV>
<DIV>It always seems to start at the beginning of the Event
List...</DIV>
<DIV> </DIV>
<DIV>You can use Page Up & Page Down keys to jump 7 events at a
time...</DIV>
<DIV> </DIV>
<DIV>However, the work around that I do for this one is if I need to
edit something that is say 16 bars into a Item.... I just do a split
just before the section I wish to edit and Voila when the new Item is
opened you are right there...</DIV>
<DIV> </DIV>
<DIV>The more I use REAPER ... the more I am getting to know how this
Item based Editing worx...</DIV>
<DIV> </DIV>
<DIV>...and liking it...</DIV>
<DIV> </DIV>
<DIV>It does not matter to me whether a Trak has One Item, several items
or several thousand items,... at any given time you can Glue all the
Items together and each part retains what you have edited and you can
start again...</DIV>
<DIV> </DIV>
<DIV>Also just as a quick mention, which some of us may need to get our
heads around, is the concept of not having a dedicated SubGroup area....
the flexibility that REAPER allows by being able to put anything
anywhere and being able to route anything to anywhere is simply in a
word ... NICE!!!</DIV>
<DIV> </DIV>
<DIV>Anyway... on with the Editing...</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Kind regards</DIV>
<DIV> </DIV>
<DIV>David P Shortland</DIV>
<DIV>DragonScore Productions</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV style="FONT: 10pt tahoma">
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A
title=cb1963@sbcglobal.net href="mailto:cb1963@sbcglobal.net">Chris
Belle</A> </DIV>
<DIV><B>Sent:</B> Thursday, September 12, 2013 6:17 AM</DIV>
<DIV><B>To:</B> <A title=rwp@reaaccess.com
href="mailto:rwp@reaaccess.com">Reapers Without Peepers</A> </DIV>
<DIV><B>Subject:</B> Re: [RWP] Reaper Accessibility Query from New
User</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV><FONT size=2 face=Arial>Hey, I have done that but is there an easy
way to move between midi events?</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>I mean you can move along the time line,
but in sonar it jumps through all the extra time and immediately goes to
the next midi event.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Or do you have to go to the exact place on
the time like for each midi event?</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>That was one thing killing me.</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=dragamilov@comcen.com.au
href="mailto:dragamilov@comcen.com.au">David P Shortland</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:45 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [RWP] Reaper
Accessibility Query from New User</DIV>
<DIV> </DIV>Hi & 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<BR>Control plus 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 (I
<BR>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 whatever <BR>you
wish...<BR><BR>No need to go to the Apply or OK buttons just hit Enter
when you have <BR>finished your Edit...<BR><BR>Kind
regards<BR><BR>David P Shortland<BR>DragonScore
Productions<BR><BR><BR><BR><BR>-----Original Message----- <BR>From:
Indigo<BR>Sent: Wednesday, September 11, 2013 8:52 PM<BR>To: Reapers
Without Peepers<BR>Subject: Re: [RWP] Reaper Accessibility Query from
New User<BR><BR>I used those ancient midi sequencers in dos or on the
Atari ST; , like<BR>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 is<BR>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.<BR>But, 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.<BR>How could it be
easier than having everything neately labeled and laid<BR>out at the
taband arrow keys; where you can arrow to other note values,<BR>for
instance, or type in different numbers for velocity, note
length,<BR>pitch, program number, yada yada yada?<BR>One thing to note
is that; when finished with editing; you need to tab<BR>to
apply, and then hit enter; but there can be another step that
might<BR>or might not be required.<BR>At certain places, you might
need to find an OK button that needs to be<BR>clicked; after pressing
enter on Apply takes you back to the track view;<BR>so look out for
that one.<BR>If anyone is not hearing their changes of values being
applied to their<BR>music, go to your number pad and use your PC
cursor slash mouse pointer<BR>slash object navigation to find that OK
button, then left click it.<BR>I'll go search my collection and repost
David Shortland's method of<BR>reaching the midi editor.<BR>By the
way, since it's a different midi editor than the inline editor<BR>that
Ivan's shortcut reached, maybe reaAccess is not doing anything
to<BR>assist with access of David's midi editor, it's just
screenreader<BR>friendly because Reaper is written that way, using
Microsoft standard<BR>menus and
controls.<BR>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 steps is<BR>> bound to help
someone.<BR>><BR>> Yeah, of course MIDI is MIDI is MIDI from DAW
to DAW, but I'd 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 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>>
wrote:<BR>>> I'll dig out and post the guide to bringing up the
midi editor, David<BR>>> Shortland style, which is step-by-step
to get inside the midi editor,<BR>>> right down to the event
list for each note of your music along the<BR>>>
timeline.<BR>>> Anyone who has the least experience with editing
midi events in every<BR>>> sequencer or daw ever made should
know that midi is midi; and it isn't<BR>>> different in a
different daw.<BR>>> Each event is clearly labeled in Reaper, in
plain English, and if you<BR>>> want to shorten or lengthen a
note length, or move the note up or down a<BR>>> list of
chromatic notes, or shift it to another octave, or alter
its<BR>>> velocity number, or move the note's position on the
timeline, or a<BR>>> thousand other editing details; duh, what's
so hard about that to figure<BR>>> out?<BR>>> So, it's
laid out differently from Voyettra Gold, or Sonar, or
ProTools,<BR>>> don't we all expect that?<BR>>> It's good
for the health of our brain cells to exercise them,
otherwise<BR>>> we get to be an old dog that can't learn new
tricks.<BR>>> When all note events are clearly labeled, all laid
out very conveniently<BR>>> at the tab keys, with edit fields at
the arrow keys, what more could<BR>>> anyone ever hope for in
access from a screenreader?<BR>>>
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 share some<BR>>>> wisdom. Just hit
on the idea of spending a bit of time hanging out<BR>>>> with
each of the people on here that are using Reaper to do
cool<BR>>>> stuff, whatever their stuff may be. I'd interview
them and record a<BR>>>> bit of them in action for an hour at
most, then handle all the boring<BR>>>> editing uploading
headache stuff so they don't have too. Seems like if<BR>>>>
enough people are keen to be featured it'd make a neat little
podcast<BR>>>> series. I could justify putting the time into
it seeing as 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 Reaper in a<BR>>>> while, so I
hope the response from Roy is positive so I can 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>>
wrote:<BR>>>>> Roy seems to have a leg up on some of the
things we don't, bet he'd <BR>>>>>
help<BR>>>>> out<BR>>>>> if we approached him
with a few
clams.<BR>>>>><BR>>>>><BR>>>>>
----- Original Message
-----<BR>>>>> From: Goldfinga
Productions<BR>>>>> To: Reapers
Without Peepers<BR>>>>> Sent:
Tuesday, September 10, 2013 5:28
PM<BR>>>>> Subject: Re: [RWP]
Reaper Accessibility Query from New
User<BR>>>>><BR>>>>><BR>>>>>
ah, well that is a hole new animal… I can do some of it, but I
<BR>>>>> would<BR>>>>>
like<BR>>>>> to better edit stuff. Is there a person doing
this already? Are they<BR>>>>> giving<BR>>>>>
lessons?
lol<BR>>>>><BR>>>>><BR>>>>>
On Sep 10, 2013, at 5:16 PM, "Chris Belle" <<A
href="mailto:cb1963@sbcglobal.net">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 and such,
<BR>>>>> but<BR>>>>> detailed editing and
nudging notes and doing transforms or search and<BR>>>>>
replace like the interpolate dialogue in sonar, that sort of
stuff.<BR>>>>>
><BR>>>>>
><BR>>>>> > ----- Original
Message -----<BR>>>>> > From:
Goldfinga Productions<BR>>>>> >
To: Reapers Without
Peepers<BR>>>>> > Sent:
Tuesday, September 10, 2013 3:44
PM<BR>>>>> > Subject: Re: [RWP]
Reaper Accessibility Query from New
User<BR>>>>>
><BR>>>>> > I use midi all
the time with reaper…<BR>>>>> >
That's why I have been all over poise, that's one less piece
of<BR>>>>> hardware<BR>>>>> that I have to
hook up to the mixer. Now I can leave my npc at
the<BR>>>>> church.<BR>>>>>
lol.<BR>>>>>
><BR>>>>>
><BR>>>>> > On Sep 10, 2013,
at 4:41 PM, "Chris Belle" <<A
href="mailto:cb1963@sbcglobal.net">cb1963@sbcglobal.net</A>><BR>>>>>
wrote:<BR>>>>>
><BR>>>>> > > yeh,
reaper<BR>>>>> > > 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 and get him
to<BR>>>>> show us<BR>>>>> 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 the midi <BR>>>>>
editor,<BR>>>>> > > and see
some events and such, but it ain't anything like
sonar<BR>>>>> and<BR>>>>> there are no
docs,<BR>>>>> >
><BR>>>>> > > We
desperately need some serious docs shoing how to
do<BR>>>>>
everything.<BR>>>>> >
><BR>>>>> >
><BR>>>>> > > -----
Original Message -----<BR>>>>>
> > From: Goldfinga
Productions<BR>>>>> > > To:
Reapers Without Peepers<BR>>>>>
> > Sent: Tuesday, September 10, 2013 3:34
PM<BR>>>>> > > Subject: Re:
[RWP] Reaper Accessibility Query from New
User<BR>>>>> >
><BR>>>>> > > That's
exactly where I was going with that. lol. I use
reaper,<BR>>>>> hell,<BR>>>>> 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>><BR>>>>>
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 line
<BR>>>>> everywhere<BR>>>>>
in<BR>>>>> the world and have to fight like dogs to not
get left out,<BR>>>>> > >
> but you know how it works in this world, money talks
and<BR>>>>> bullshit<BR>>>>>
walks.<BR>>>>> > >
><BR>>>>> > > > If
there were 20 million blind reaper users ready to buy
<BR>>>>> access<BR>>>>> would be here next
week 'grin'.<BR>>>>> > >
><BR>>>>> > > > For
now we just have to cowboy up and do the best we
can.<BR>>>>> > >
><BR>>>>> > >
><BR>>>>> > > > -----
Original Message -----<BR>>>>>
> > > From: Scott
Chesworth<BR>>>>> > > >
To: Reapers Without
Peepers<BR>>>>> > > >
Sent: Tuesday, September 10, 2013 1:10
PM<BR>>>>> > > > Subject:
Re: [RWP] Reaper Accessibility Query from New
User<BR>>>>> > >
><BR>>>>> > > > Couple
of points to keep in mind before you dig too deep
into<BR>>>>>
slating<BR>>>>> > > > the
Reaper developers in
public...<BR>>>>> > >
><BR>>>>> > > > They
are aware that a visually impaired userbase exists,
and<BR>>>>>
have<BR>>>>> > > >
gradually been exposing GUI elements over time. If you
need<BR>>>>> proof<BR>>>>>
of<BR>>>>> > > > that, do
some mousing around in Reaper on PC and see how
much<BR>>>>>
NVDA<BR>>>>> > > > tells
you, or compare how much is visible with VoiceOver on
<BR>>>>> Mac<BR>>>>>
now<BR>>>>> > > > against
a version from a couple years back. API bugs that<BR>>>>>
impacted<BR>>>>> > > >
upon ReaAccess were fixed, and there have been a couple
of<BR>>>>>
instances<BR>>>>> > > >
where accessibility gets a mention in the changelogs. A
<BR>>>>> couple<BR>>>>>
of<BR>>>>> > > > people
with decent track records of getting stuff done are
in<BR>>>>>
contact<BR>>>>> > > >
with Justin the lead developer, all be it sporadically.
<BR>>>>> They're<BR>>>>>
not<BR>>>>> > > >
shouting from the rooftops about that, but when the
progress<BR>>>>> comes,<BR>>>>>
it<BR>>>>> > > > happens
in fits and starts and has been largely due to
nudges<BR>>>>>
and<BR>>>>> > > >
guidance from these key people. I think it's fair to say
that<BR>>>>>
Cockos<BR>>>>> > > > have
demonstrated that they're happy to help, but they
need<BR>>>>>
guidance<BR>>>>> > > >
and it needs to fit around their existing roadmap. I think
<BR>>>>> it's<BR>>>>>
pretty<BR>>>>> > > >
unfair to say we've been shafted. If you must find a home
for<BR>>>>>
that<BR>>>>> > > >
accusation, Ivan's your man. Tell him who sent you
lol.<BR>>>>> > >
><BR>>>>> > > > Is the
future certain? No. Then again, are their other
DAW<BR>>>>>
developers<BR>>>>> > > >
showing markedly less interest? You
betcha.<BR>>>>> > >
><BR>>>>> > > > Nice
idea re the NVDA team. Last time I approached Jamie
<BR>>>>> about<BR>>>>>
Reaper<BR>>>>> > > > he
was up to his ears in Sonar as his pet project, but
who<BR>>>>>
knows,<BR>>>>> > > >
someone else might have better luck catching him at the
right<BR>>>>>
time.<BR>>>>> > >
><BR>>>>> > > >
Scott<BR>>>>> > >
><BR>>>>> > >
><BR>>>>> > > > On
9/10/13, Goldfinga Productions <<A
href="mailto:goldfingas@gmail.com">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>><BR>>>>>
wrote:<BR>>>>> > > >
><BR>>>>> > > >
>> Muhahahahahahahhahaha! Cock OS! Oh dear! LOL Okay, I'll
<BR>>>>> stop<BR>>>>>
laughing<BR>>>>> > > >
>> now.<BR>>>>> > >
> >> But yeah, I think we've got it for
sure.<BR>>>>> > > >
>><BR>>>>> > > >
>> On 9/10/13, Goldfinga Productions <<A
href="mailto:goldfingas@gmail.com">goldfingas@gmail.com</A>><BR>>>>>
wrote:<BR>>>>> > > >
>>> Remember folks, the developers of reaper call them
selves<BR>>>>> "cockos."
If<BR>>>>> > > >
>>> you<BR>>>>> > >
> >>> break that down, it spells "cock OS." lol. I think
we got<BR>>>>> the<BR>>>>> shaft
on<BR>>>>> > > >
>>> this<BR>>>>> >
> > >>>
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>><BR>>>>>
> > > >>>
wrote:<BR>>>>> > > >
>>><BR>>>>> > >
> >>>> I can tel you, despite being new myself, that
yes,<BR>>>>> ReaAccess<BR>>>>>
has<BR>>>>> > > >
>>>> always been (basicly) the accessibility pathway for
<BR>>>>> screen<BR>>>>> readers
to<BR>>>>> > > >
>>>> interface to
Reaper.<BR>>>>> > > >
>>>> The development has die out-last update was in
2010.<BR>>>>> > > >
>>>> A few folks have been able to use Reaper 4 with
<BR>>>>> ReaAccess<BR>>>>>
just<BR>>>>> > > >
>>>> fine-looking up workarounds for things etc, but as
I<BR>>>>> understand<BR>>>>>
it<BR>>>>> > > >
>>>> your largely on your own with Reaper
anyways.<BR>>>>> > > >
>>>> Without ReaAccess, I do not believe any
native<BR>>>>> accessibility<BR>>>>> exists
in<BR>>>>> > > >
>>>> Reaper
itself.<BR>>>>> > > >
>>>> However, again, I could be utterly
wrong.<BR>>>>> > > >
>>>> If others could reply to this new users question as
<BR>>>>> well,<BR>>>>>
that<BR>>>>>
might<BR>>>>> > > >
>>>> help-but I believe I've answered
it.<BR>>>>> > > >
>>>><BR>>>>> > >
> >>>><BR>>>>> >
> > >>>> On 9/10/13, Daveed Mandell <<A
href="mailto:daveedm@sbcglobal.net">daveedm@sbcglobal.net</A>>
<BR>>>>>
wrote:<BR>>>>> > > >
>>>>>
Hello:<BR>>>>> > > >
>>>>><BR>>>>> >
> > >>>>> What is the status of Reaper
accessibility right now? I<BR>>>>>
understand<BR>>>>> > > >
>>>>> that<BR>>>>>
> > > >>>>> Reaper's developers have shown
little or no interest in<BR>>>>>
making<BR>>>>>
the<BR>>>>> > > >
>>>>>
software<BR>>>>> > > >
>>>>> accessible, and that accessibility has been
provided<BR>>>>> through<BR>>>>>
a<BR>>>>> > > >
>>>>>
separate<BR>>>>> > > >
>>>>> bridfe produced by blind people working from this
list<BR>>>>> and<BR>>>>> website.
I<BR>>>>> > > >
>>>>> also<BR>>>>>
> > > >>>>> understand that the website itself
isn't functioning<BR>>>>> anymore<BR>>>>> due
to<BR>>>>> > > >
>>>>>
problems<BR>>>>> > > >
>>>>> related to spam. At any rate, is the latest
version of<BR>>>>> Reaper,<BR>>>>>
version<BR>>>>> > > >
>>>>> 4.5,<BR>>>>>
> > > >>>>> accessible for blind folks? It is
interesting to note <BR>>>>> the<BR>>>>>
difference<BR>>>>> > > >
>>>>> in<BR>>>>>
> > > >>>>> attitude between the developers of
Reaper, versus the<BR>>>>> developers
of<BR>>>>> > > >
>>>>> the<BR>>>>>
> > > >>>>>
free<BR>>>>> > > >
>>>>> Audacity audio software, who have been
very<BR>>>>>
conscientiously<BR>>>>> > >
> >>>>>
integrating<BR>>>>> > > >
>>>>> accessibility into the software. Thanks for any
updates<BR>>>>>
and<BR>>>>> > > >
>>>>>
information<BR>>>>> > > >
>>>>> 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>>>>> > >
> >>>> --<BR>>>>>
> > > >>>>
Sincerely,<BR>>>>> > > >
>>>><BR>>>>> > >
> >>>>
Keith<BR>>>>> > > >
>>>> Home
Phone:<BR>>>>> > > >
>>>>
928-554-3936<BR>>>>> > >
> >>>> Mobile
Phone:<BR>>>>> > > >
>>>>
928-713-6370<BR>>>>> > >
> >>>> Primary
email:<BR>>>>> > > >
>>>> <A
href="mailto:keithint1234@gmail.com">keithint1234@gmail.com</A><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>>>>> >
> > >>> 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<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>>>>> > >
> >> Sincerely,<BR>>>>>
> > > >><BR>>>>>
> > > >>
Keith<BR>>>>> > > >
>> Home Phone:<BR>>>>> >
> > >>
928-554-3936<BR>>>>> > >
> >> Mobile
Phone:<BR>>>>> > > >
>> 928-713-6370<BR>>>>> >
> > >> Primary
email:<BR>>>>> > > >
>> <A
href="mailto:keithint1234@gmail.com">keithint1234@gmail.com</A><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>>>>> > >
> > 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<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>>>>>
> > > 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>>>>> > >
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<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>>>>>
> > 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>>>>> >
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<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>>>>>
> 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>>>>>
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<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>>>> 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>> 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>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>
<P>
<HR>
_______________________________________________<BR>RWP mailing
list<BR>RWP@reaaccess.com<BR>http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com<BR></DIV></DIV></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>RWP mailing
list<BR>RWP@reaaccess.com<BR>http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com<BR></BLOCKQUOTE>
<P>
<HR>
<P></P>_______________________________________________<BR>RWP mailing
list<BR>RWP@reaaccess.com<BR>http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com<BR></BLOCKQUOTE>
<P>
<HR>
<P></P>_______________________________________________<BR>RWP mailing
list<BR>RWP@reaaccess.com<BR>http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com<BR></BLOCKQUOTE>
<P>
<HR>
<P></P>_______________________________________________<BR>RWP mailing
list<BR>RWP@reaaccess.com<BR>http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com<BR></BLOCKQUOTE></BODY></HTML>