Thanks a million for that Slau, I'll update on any developments.
--------------------------------------------------
From: "Slau Halatyn" <slauhala...@gmail.com>
Sent: Saturday, November 27, 2010 1:39 AM
To: <ptaccess@googlegroups.com>
Subject: Re: plugins/digi003
Yes, Brian,
The hot spot feature is great. Keep in mind that it's persistent across
boot-ups which is great. It's all based around the numbers row 1-9, maybe
0, I'm not sure. VO-Shift-(number) sets the hot spot while VO-(number
takes you directly to the hot spot. VO-Command-(number) reads the value at
the hot spot without taking you to it and VO-Command-Shift-(number)
watches the hot spot. Now, "Watching the hot spot" is sort of new to me
and I think it reports changes in the value on the fly but I don't know
how well that works with Pro Tools. Some experimentation still needs to be
done.
Anyway, just a quick note to encourage you to experiment as well.
Cheers,
Slau
On Nov 26, 2010, at 5:34 PM, Brian Casey wrote:
Thanks Slau Chuck and Sean, this is helping me to iron out some thoughts
for work flow.
I'd forgotten about hot spots, which I must explore on VO regardless.
I've a steep learning curve too because come next February in my Masters
course I'll be attempting to programme simple synthesiser interfaces that
will be VO friendly...if I make any grounds on that front I'll share
anything I happen to develop with you guys, though it probably won't be
ProTools related.
Chuck, great to know your sharing my suffering with the focus on the
plugin window,, and that I wasn't just going mad!! haha
Brian.
--------------------------------------------------
From: "Sean A. Cummins" <seanacumm...@gmail.com>
Sent: Friday, November 26, 2010 9:11 PM
To: <ptaccess@googlegroups.com>
Subject: Re: plugins/digi003
Slau,
And that is what Tim is working on. Smile!
Sean
----- Original Message ----- From: "Slau Halatyn"
<slauhala...@gmail.com>
To: <ptaccess@googlegroups.com>
Sent: Friday, November 26, 2010 12:36 PM
Subject: Re: plugins/digi003
Hi Jon,
VoiceOver doesn't automatically read selective items within a window.
Imagine this: You have a window with 20 parameters being displayed among
other things like a pop-up menu for insert, plug-in type, factory
default, etc. When you change one of the 20 parameters by using the
seventh encoder knob on the control surface which happens to coincide
with the third parameter in the plug-in, well, you can imagine that such
integral functionality can only be achieved through scripting of a
screen reader or having a purpose-written application running in the
background.
What you can do, however, is use VoiceOver to go to each subsequent
parameter while changing values and using VO-f3 to check the values. For
that matter, it's almost just as easy, once you're on a parameter, to
simply change it with VoiceOver. Where a control surface is truly fast
and efficient, however, is when you get to know the plug-in you're
working with and you can simply tweak an encoder knob to get the result
you seek. Rather than worrying about the difference between a ratio of
2.5 to 1 versus 2.6 to 1, one can use the encoder knobs the way knobs
have been used for decades on outboard gear and that's by ear. Of
course, even with outboard gear, a blind user would need to acquaint
themselves with the function of each knob, its range, etc. Using encoder
knobs on a control surface is hardly different. The difference is in the
consistency of getting the encoders to reflect the parameters rather
than pan or send values but that's a matter of knowing one's control
surface and being able to recreate steps consistently.
Slau
On Nov 26, 2010, at 11:23 AM, Jon Solitro wrote:
How does one get VoiceOver to read what each knob does when in insert
mode for a particular plugin on the 003?
