[Rwp] NVDA and Reaper
Van Schmidt
vanschmidt at comcast.net
Thu Apr 2 20:28:43 EDT 2015
Hey Scott,
Thanks for the excellent information. You guys are a great resource!
Van
-----Original Message-----
From: RWP [mailto:rwp-bounces at bluegrasspals.com] On Behalf Of
rwp-request at bluegrasspals.com
Sent: Thursday, April 02, 2015 4:23 PM
To: rwp at bluegrasspals.com
Subject: RWP Digest, Vol 3, Issue 8
Send RWP mailing list submissions to
rwp at bluegrasspals.com
To subscribe or unsubscribe via the World Wide Web, visit
http://bluegrasspals.com/mailman/listinfo/rwp
or, via email, send a message with subject or body 'help' to
rwp-request at bluegrasspals.com
You can reach the person managing the list at
rwp-owner at bluegrasspals.com
When replying, please edit your Subject line so it is more specific than
"Re: Contents of RWP digest..."
Today's Topics:
1. Re: Setting value parameters within an effect (Scott Chesworth)
2. Re: NVDA and Reaper (Scott Chesworth)
3. Re: NVDA and Reaper (Van Schmidt)
4. Wo! Yikes! BSD! (Christopher-Mark Gilland)
5. Re: Wo! Yikes! BSD! (Scott Chesworth)
6. Re: Wo! Yikes! BSD! (James Teh)
----------------------------------------------------------------------
Message: 1
Date: Thu, 2 Apr 2015 22:38:58 +0100
From: Scott Chesworth <scottchesworth at gmail.com>
To: Reapers Without Peepers <rwp at bluegrasspals.com>
Subject: Re: [Rwp] Setting value parameters within an effect
Message-ID:
<CAL7HGJQi6gzDPjtXfstkS7SN_t81QQNbyqt6HLJTwvyCMeGkMw at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi Chris,
What you'll find via Shift+P depends on what the plugin itself outputs. Some
output what I call real-world values (though I think the correct techie term
is probably formatted values), other don't. For the plugs that do, you'll
see things like attack times in MS, ratio in numbers that actually mean
something etc. For the ones that don't, pretty much everything is
represented by a number from 0.0 (all the way off) to 1.0 (all the way on).
The slider that gives values in percentages is still working with that range
from 0 to 1, so 55% on the slider will be 0.55 in the edit field. That's
useful to know if you want to key in values quickly without faffing with the
slider.
Experimentation is the key here, but yep, it's annoying. You'll find you
probably have the most consistent luck getting real-world values out of the
stock Reaper plugs. ReaComp for example should be showing you values that
you know how to work with.
There's one other technique that can come in handy when a plug doesn't show
you much useful stuff after you've hit Shift+P, and that's to try running
the plugin in bridged mode. Reaper does this automatically if you try and
run a 32-bit plug in a 64-bit environment, but you can force it to bridge
native plugs too, and sometimes that'll enable you to access settings in a
more meaningful way than Shift+P does. To force a plugin to run bridged,
before you open it, go to Preferences, then Compatibility which you'll find
just underneath Plug-ins in the tree view. Tab until you reach the "VST
bridging and firewalling"
combobox, and set that to "In dedicated process per plugin". Now when you
load Autotune, you'll find yourself in a separate window. You'll need to use
the virtual cursor of whatever screen reader you're using, but you'll find
that options for key, scale, voice type etc can be clicked on and change
there. Not everything is accessible that way, for example to use the the
humanize function of Autotune I had to go back into the parameters in the
Shift+P dialog and set the slider to 100% to turn that on, but between those
two views, you can get a lot done.
Yeah, I know, this is all a lot more of a headache than Pro Tools. The one
thing that keeps me sane about it is that between the two views, I can
usually get something usable out of most plugs, whereas in PT they either
work or flat out refuse to. The best thing is probably just to try a boat
load of plugins, and make the ones that expose good values work for you.
Over time I've built up a list of go-to plugins in both DAWs, but due to the
different methods of access on each platform, they don't tend to be the same
plugins across both DAWs.
Hth explain things a bit.
Scott
On 4/2/15, Christopher-Mark Gilland via RWP <rwp at bluegrasspals.com> wrote:
> So... I was playing around a bit with a few different plugins. I
> tried a few reverb plugs, and also tried a few compressors. They work
> well, but especially when dealing with a compressor, is this mainly
> just going to have to be a thing where I let my ears do the work
> instead of my brain? When I go into the list of parameters with
> shift+P, I notice that most of the parameters are specified in
> percentage value. So, say you're dealing with a compressor. How do
> you know exactly what your attack and release are set to in terms of
> MS? Also, take the ratio. Say you want a 3/1 ratio, I think it would
> be. (I always get the numerator and denominator confused.) Anyway,
> point is, it's reading a really weird value that I don't even know what
it's basing it off of. It doesn't look like percentages.
>
> I don't wanna write a book, and like you all've said, keep it short.
> Let me give one more practical example, then I'm done. I promise.
> Take something like say... Auto-Tune. I know a lot of you all hate
> it, but it actually
> *can!* when used correctly, serve a purpose. Anyway, you have
> different things in here like the type of voice, low male, tinner,
> etc. You can set the key the song is in, the scale between major,
chromatic, minor, etc.
> Though I can see these parameters when hitting shift+P, again, they're
> being represented with the value as percentage numbers, rather than
> the options within that parameter. So, how do you deal with that?
> Like, scale, you would see a percentage number, like 7 percent,
> instead of seeing major minor, chromatic etc. So ultimately what I'm
> saying is, how do I know what X percentage value lines up with Y
parameter? Or, do you kind a not.
>
> Chris.
------------------------------
Message: 2
Date: Thu, 2 Apr 2015 22:46:53 +0100
From: Scott Chesworth <scottchesworth at gmail.com>
To: Reapers Without Peepers <rwp at bluegrasspals.com>
Subject: Re: [Rwp] NVDA and Reaper
Message-ID:
<CAL7HGJR0eYWrMn2x8n8AQgSe9VQn3=gt9BqdsRsmEzfAePy0cg at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hey Van, welcome aboard.
You'll find that there are a high proportion of NVDA users here, probably
more so than any other DAW. Also, OSARA (a new accessibility add-on that
will soon supersede ReaAccess) is being developed by Jamie Teh, and I'm sure
you'll know who he is as an NVDA user.
Dive into the Reaper documentation and shout if you get stuck. There's not
much in the way of documentation for ReaAccess itself, but the what's new
and history files are usually enough to get people started.
Beyond that, there's also a training mode in ReaAccess. Hit F12 to start it,
and while it's running, any keystrokes you press will speak there function.
F12 stops training and keystrokes will perform as expected.
Enjoy, and shout if we can help.
Scott
On 4/2/15, Van Schmidt via RWP <rwp at bluegrasspals.com> wrote:
> Hello,
>
> I'm brand new to this list and to Reaper and ReaAccess. Before I
> invest a lot of time installing the software and reading the entire
> online user's manual, I have a couple of basic questions. Has anyone
> been able to use NVDA with Reaper-ReaAccess with any degree of
> accessibility, or is it strictly a JAWS-only setup? Also, if it does
> work with NVDA, are there any NVDA-related limitations I should be
> aware of?
>
>
>
> Thanks,
>
>
>
> Van
>
>
------------------------------
Message: 3
Date: Thu, 2 Apr 2015 15:47:49 -0600
From: "Van Schmidt" <vanschmidt at comcast.net>
To: <rwp at bluegrasspals.com>
Subject: Re: [Rwp] NVDA and Reaper
Message-ID: <009701d06d8e$ae26daf0$0a7490d0$@comcast.net>
Content-Type: text/plain; charset="us-ascii"
Thanks, Chris.
I use JAWS as well for my work PC, but I use NVDA on my personal laptop.
Looks like I'll install the programs and work my way through the
documentation. At least I know now it's doable.
Much appreciated,
Van
------------------------------
Message: 4
Date: Thu, 2 Apr 2015 17:54:43 -0400
From: "Christopher-Mark Gilland" <clgilland07 at gmail.com>
To: <rwp at bluegrasspals.com>
Subject: [Rwp] Wo! Yikes! BSD!
Message-ID: <F3654DD83A754B11B709698FA72312ED at mygateway>
Content-Type: text/plain; charset="iso-8859-1"
Oh, Gawod! I haven't seen one a these babies since the Win 9X days, and
maybe once! key word, once! in XP. I was fiddling around with a few plugins
in my effect chain while a project was playing. This way I could hear in
realtime what was going on. All a sudden, boom! I get a blue screen a
death! I hit enter, and my system rebooted, and came back up just fine,
thank God. This isn't just happenning with one particular plugin, and it's
not at all consistent. I've reproduced it now about 3 or 4 times, although
I couldn't even begin to tell you how or what conditions are doing it.
This is Windows 7 64 bit Home Premium, JAWS 16 Professional, and the most
recent version both of Reaper X64 and ReaAccess.
Does anyone have a clue what may be doing this? It's not so much got me
concerned being it's obviously not severely crashing the system permanently,
God forbid, but it does have me intrigued. That's for sure!
Chris.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://bluegrasspals.com/pipermail/rwp/attachments/20150402/cb807c93/attach
ment-0001.html>
------------------------------
Message: 5
Date: Thu, 2 Apr 2015 23:11:54 +0100
From: Scott Chesworth <scottchesworth at gmail.com>
To: Reapers Without Peepers <rwp at bluegrasspals.com>
Subject: Re: [Rwp] Wo! Yikes! BSD!
Message-ID:
<CAL7HGJT0it-Os-5X2gUKQd-7-A4z6bSLB940a3zas7tEHYe2_A at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Not a clue, sorry man. One of the things that's kept me running Reaper is
that stuff like that doesn't happen here.
Is there any info you can get from checking the system logs, event viewer or
something? Can't give you a step by step unfortunately as this is deeper
into Windows than I generally like to delve. Google could probably turn up
some good articles on how to troubleshoot such crashes though.
Keep us posted if you figure out what caused it.
On 4/2/15, Christopher-Mark Gilland via RWP <rwp at bluegrasspals.com> wrote:
> Oh, Gawod! I haven't seen one a these babies since the Win 9X days,
> and maybe once! key word, once! in XP. I was fiddling around with a
> few plugins in my effect chain while a project was playing. This way
> I could hear in realtime what was going on. All a sudden, boom! I
> get a blue screen a death! I hit enter, and my system rebooted, and
> came back up just fine, thank God. This isn't just happenning with
> one particular plugin, and it's not at all consistent. I've
> reproduced it now about 3 or 4 times, although I couldn't even begin to
tell you how or what conditions are doing it.
>
> This is Windows 7 64 bit Home Premium, JAWS 16 Professional, and the
> most recent version both of Reaper X64 and ReaAccess.
>
> Does anyone have a clue what may be doing this? It's not so much got
> me concerned being it's obviously not severely crashing the system
> permanently, God forbid, but it does have me intrigued. That's for sure!
>
> Chris.
------------------------------
Message: 6
Date: Fri, 03 Apr 2015 08:22:39 +1000
From: James Teh <jamie at jantrid.net>
To: Reapers Without Peepers <rwp at bluegrasspals.com>
Subject: Re: [Rwp] Wo! Yikes! BSD!
Message-ID: <551DC12F.70000 at jantrid.net>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
BSODs are caused by issues in kernel mode code; in other words, driver
problems, hardware problems or, far less likely, a bug in Windows itself. My
guess would be a driver bug. Unfortunately, a lot of audio drivers seem to
be fairly buggy. JAWS also uses a video intercept driver, so it could be a
bug in that, too, although that's probably far less likely these days.
In short, there's probably not much you can do about it except checking that
your drivers are all up to date.
Jamie
On 3/04/2015 7:54 AM, Christopher-Mark Gilland via RWP wrote:
> Oh, Gawod! I haven't seen one a these babies since the Win 9X days,
> and maybe once! key word, once! in XP. I was fiddling around with a
> few plugins in my effect chain while a project was playing. This way
> I could hear in realtime what was going on. All a sudden, boom! I
> get a blue screen a death! I hit enter, and my system rebooted, and
> came back up just fine, thank God. This isn't just happenning with
> one particular plugin, and it's not at all consistent. I've
> reproduced it now about 3 or 4 times, although I couldn't even begin
> to tell you how or what conditions are doing it.
> This is Windows 7 64 bit Home Premium, JAWS 16 Professional, and the
> most recent version both of Reaper X64 and ReaAccess.
> Does anyone have a clue what may be doing this? It's not so much got
> me concerned being it's obviously not severely crashing the system
> permanently, God forbid, but it does have me intrigued. That's for sure!
> Chris.
>
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp
--
James Teh
Email/MSN Messenger/Jabber: jamie at jantrid.net Web site:
http://www.jantrid.net/
Twitter: jcsteh
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://bluegrasspals.com/pipermail/rwp/attachments/20150403/d36b5f3a/attach
ment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
RWP mailing list
RWP at bluegrasspals.com
http://bluegrasspals.com/mailman/listinfo/rwp
------------------------------
End of RWP Digest, Vol 3, Issue 8
*********************************
More information about the RWP
mailing list