``````Actually, if you happen to have a braille display with whiz weels like the focus 40 blue, you can make value changes a lot quicker.
Gord

-----Original Message----- From: Slau Halatyn
Sent: Monday, March 23, 2015 9:45 AM
To: ptaccess@googlegroups.com
Subject: Re: feedback needed for Pro Tools 12

Hi Brian,

You probably won't like my answer very much but, frankly, I've never read a gain reduction meter in Pro Tools as long as I've used it and that would be since 2002. To be honest, before that, even when I could actually make out a VU meter, I always relied on my ears. That said, naturally, I think it's something that should be accessible. In other words, for most people, it's not a deal-breaker but it's an issue that needs attention. For now, exaggerate your compression, back it off and trust your ears.

Best,

Slau

On Mar 23, 2015, at 9:39 AM, Brian Howerton <bshowert...@gmail.com> wrote:

How agre folks getting around not being able to read gain reduction meters in pt?

Sent from my iPhone

On Mar 23, 2015, at 8:50 AM, David Eagle <onlineea...@googlemail.com> wrote:

Yes, being able to adjust slider values in larger increments would be massively helpful. And gain reduction feedback in compressors too. I'm a bit unsure what happens when you increase the volume on a track. If you have a compressor insert on that track, does the volume adjustment affect the level before or after the compressor? In sonar there was a trim and a volume option.
Thanks aplenty Slau.

Sent from my iPhone

On 23 Mar 2015, at 12:18, studiojay <overdriverecord...@gmail.com> wrote:

Hi Slau, Thanks again for every thing you are doing. My input. I agree with Gord, it would be cool to change plugin values in larger increments. Also, it would be nice to be able to read gain reduction meters in compressor plugins both stock and 3rd party. Also, there are 2 popup menus in the select-split notes dialog that do not work with voiceover. This dialog is accessed with option y. Regards, Jason

On Monday, March 23, 2015 at 1:53:01 AM UTC-4, Gord wrote:
                           Is there any hope for structure?  That is an
Avid virtual instrument, isn't it?  Also, it would be nice to be able to
adjust some parameter sliders in larger increments, or to type in values
directly.
Keep up the good work Slau!
Gord

-----Original Message----- From: Slau Halatyn
Sent: Sunday, March 22, 2015 6:58 PM
To: ptac...@googlegroups.com
Subject: Re: feedback needed for Pro Tools 12

Hi John,

Yep, you might have missed the previous reply. Click is definitely an issue that needs to be resolved. For now, all of the parameters are accessible via
a control surface. For those who don't have a surface, I'll see if I can
come up with a number of presets to help in the mean time. I'm leaving town
this week and will be gone for 2 weeks so it'll be a while.

The status of the Input monitor button is identified by its name. VoiceOver indicates when it's engaged but not when it's not engaged. In other words, much like a mute button that is off, you'll only hear the name of the button
as opposed to hearing that it's in its "on" state.

Hope that helps.

best,

Slau

On Mar 22, 2015, at 5:17 PM, John Gunn <gu...@tznet.com> wrote:

> Hello Slau,
>
> Great you are meeting with a programmer and here are a couple of > things I
> have.
>
> First when selecting a click sound other then the default click, I am
> unable to choose for example cowbell, stick ETC.  This of course is
> setting up a click track.
>
> Secondly and this might be user error on my part but is there a way
> finding the status of a track if it is set to input monitor? Tryied > to > bounce a session last week and message unable to bounce because of > input
> monitor.
>
> Feel free to let me know if I am way off base on any of my feedback.
>
> John
>
>
>> On Mar 16, 2015, at 9:41 AM, Slau Halatyn <slauh...@gmail.com> 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+u...@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+u...@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+u...@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.

--
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.

Reply via email to