Thanks Slau, I'll keep looking around and update what I find as well.
Have a safe trip!
Chi
On 3/26/2015 8:55 PM, Slau Halatyn wrote:
Hi Chi,
I can't think of anything else at this point. I'm not sure why it's not working
for you right now. I'll be travelling overseas tomorrow so I suppose I'll have
plenty of time to ponder this one :)
Best,
Slau
On Mar 26, 2015, at 8:21 PM, Chi Kim <chigook...@hotmail.com> wrote:
HI Slau, thanks for the help.
Yes I'm aware of the fact that the Voiceover reads the radio buttons in such
ways for that particular settings.
Peak on the left and and Clip indicator on the right
Then the related radio buttons below the labels.
I went to clip indicator label first then went down to make sure infinite is
selected. It's very mysterious why it's not working.
Can you think of any other setting that might be preventing this?
Thanks,
Chi
On 3/26/2015 10:05 AM, Slau Halatyn wrote:
Hi Chi,
I've just verified that in version 11.3 the clip indicator definitely works. I'm not sure what might be
causing your problem with the indicator. One thing I would check is that you have the correct radio button
checked in the Metering tab of the Preferences window. The way it reads is not entirely clear at first. There
are two columns, one for Peak and one for Clipping. If you read across, you might mistake the first column as
immediately following the Clip text. I'm not sure if this happened to you or not but, just to be sure, I
would check it again. Navigate to the right until you reach the first radio button that reads "3
seconds" and then continue to the second radio button that reads "3 seconds." This is the
column that pertains to Clipping. Navigate down and you'll find the "Infinite" radio button and
make sure it's check.
Hope that helps,
Slau
On Mar 26, 2015, at 5:13 AM, Chi Kim <chigook...@hotmail.com> wrote:
Hi Slau,
Just for update, Clip indicators was already set to hold for infinite, and VO
still doesn't announces when the meter is clipped.
Anything else I should check?
Thanks for your help,
Chi
On 3/22/2015 3:17 PM, Slau Halatyn wrote:
Hi Chi,
Yep, the Click plug-in's parameters don't work well right now. That's certainly
on the list of things to tackle. Incidentally, the parameters are accessible
with a control surface. So, for example, to access triplets and accent values,
etc., the encoder knobs or faders in flip mode will control those parameters
and it's possible to save those settings as presets for future use.
The clip indicators are working fine. Make sure you have your preferences set
to hold clip indicators and you should be good to go.
The subject of preset browsing in the plug-in window is clearly a much larger
issue and, regardless of its accessibility, I'm not sure that it's going to
necessarily change any time soon. Surely, it's much more of an issue for
virtual instruments and one size doesn't fit all so I wouldn't expect Avid to
come up with any solution that'll be right for every developer. Plug-in
accessibility, in general, is an important issue and its model might have to
change entirely for it to be viable for the long term. We'll all keep trying
until we get it right.
Slau
On Mar 22, 2015, at 3:09 PM, Chi Kim <chigook...@hotmail.com> wrote:
Hi Slau,
The new click plugin included in pt 11 is not accessible.
Also, getting access to warp markers would be good.
I believe clip indicator is not accessible with Voiceover anymore. When the
meter clips, Voiceover used to say clipped until you clear it, but it doesn't
say it anymore.
Lastly, I know you specifically said no new future request, but it'd be worth
while to briefly mention about creating a flexible database system that manages
all the presets for all the plugin with tagging system something like Native
Instrument Komplete. Komplete consists of many plugins with many presets (total
17,000), but you can browse all of them in one browser and load them easily.
This would save a lot of time for any composers/producers to find right sound
without going through many different plugins with many different presets.
The current preset system for Pro Tools is so old style and not that flexible,
so many developers don't even bother and create their own instead.
I'm sure this would require a lot of thought process to make it useful for
users, and easier for plugin developers to implement. However, if Avid pulls it
off well and markets it as a cool new feature, it would benefit everyone
regardless sighted or blind once the developers start taking advantage of it.
Thanks for working with Avid on this important work.
Chi
On 3/16/2015 10:41 AM, Slau Halatyn wrote:
In a couple of weeks, I'm going to have a unique opportunity to sit down with a
programmer to work on some accessibility issues in Pro Tools. Under the
circumstances of my trip, Avid has allowed for this meeting to be scheduled
barring any last minute crisis with the release of Pro Tools 12. This will be
largely driven by bug submissions already within the beta system but I wanted
to get a sense of what the user base is focused on day to day. My goal is to
address quality-of-life issues that affect the use of Pro Tools with VoiceOver.
For example, the way the inserts and, in particular, sends are displayed is
simply awful. This needs to be overhauled. There are a number of such issues
that can hopefully be taken care of in one marathon session of tweaks.
I have a clear idea of what I personally think should be addressed but I
thought I'd take the temperature of the community. What I'm asking of the list
is for people to enumerate 3 to 5 things that most affect their productivity
and would like to see improved. Now, I don't mean for people to suggest a
different method for importing files to an existing track. That's a bigger fish
to fry and the subject of a longer term solution. These are, as I said,
quality-of-life issues that can be addressed quickly. Also, don't bring up
issues in version 10. We're talking existing issues in version 11. Give me your
top 3 or top 5 items and we'll see which seem to reveal themselves as the
biggest concerns. The sooner you get those to me, the sooner I can prepare.
Thanks,
Slau
--
You received this message because you are subscribed to the Google Groups "Pro Tools
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Pro Tools
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Pro Tools
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Pro Tools
Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
