Re: Pro-tools 12 just released

[Christopher-Mark Gilland]

So then... is there any point in the first place in upgrading then?

Chris.
---
Check out my web site at:
http://www.clgproductions.net
  - Original Message - 
  From: Chris Harrington 
  To: ptaccess@googlegroups.com 
  Sent: Monday, March 23, 2015 3:18 PM
  Subject: Re: Pro-tools 12 just released


  There aren't any excess ability changes  from ProTools 11 to 12.
  Chris

  Sent from my iPhone

  On Mar 23, 2015, at 2:10 PM, Christopher-Mark Gilland  
wrote:


I wonder if the accessibility is worth the upgrade?

Chris.
---
Check out my web site at:
http://www.clgproductions.net
  - Original Message - 
  From: Nickus de Vos 
  To: ptaccess@googlegroups.com 
  Sent: Monday, March 23, 2015 2:08 PM
  Subject: Pro-tools 12 just released


  Hi all
  Just saw that Avid released PT12 
http://www.pro-tools-expert.com/home-page/2015/3/23/pro-tools-12-goes-on-sale-in-the-avid-store.html?utm_source=dlvr.it&utm_medium=twitter


  I was about to buy PT11 tomorrow, so guess I'll wait a bit.

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

Re: a word about Pro Tools 12

[Nick Gawronski]

Hi, Does anyone know if the digi 003 with the moving controls is 
supported in Pro Tools version 12?  I was mainly asking as I don't want 
to upgrade unless I can use it or if there is an option to trade it in 
for a newer interface with moving controls.  Nick Gawronski


On 3/23/2015 3:27 PM, Slau Halatyn wrote:

To my knowledge, all should be the same with the possible exception of the 
authorization which was already beginning to transition. In other words, 
neither the iLok method or the built-in method is accessible yet. Both will be 
accessible in time, probably one before the other. At any rate, I've only had 
beta experience and, to me, it looks the same as far as I can tell. Mind you, 
I'll have to purchase an upgrade like everyone else but for the HD users, the 
cost is $599 and I won't be using it on the new machine yet so I might wait 
just a little while. Apparently, there's no option for a co-install of 11 and 
12. Therefore, it would seem to me that this means no co-install of 10 and 12 
as well. There's a lot of confusion about what the real case is. This is all 
pretty new to everybody so it's probably a good idea to wait until the dust 
settles.

Slau

On Mar 23, 2015, at 3:45 PM, Nickus de Vos  wrote:


Hi Slau
So just to be clear, in terms of accessibility, nothing really new in
12 but also nothing broken?

On 3/22/15, Slau Halatyn  wrote:

I'm not going to be breaking any NDA by saying this and, besides, it's no
secret that Pro Tools 12 will be coming out soon, like, maybe even tomorrow.
Please be aware that there is essentially nothing different about its
accessibility. There's a newly designed I/O Setup but, to a VoiceOver user,
it appears much the same. If anything, there are a few extra controls.

The authorization aspect of Pro Tools will be changing and it's unclear
whether this will change right from this new release or whether it'll be
incorporated over time but it won't be any more accessible than standard
iLok authorization for now. Be assured, however, that it will be made
accessible. More info to come as it becomes clearer.

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.

Re: a word about Pro Tools 12

[Slau Halatyn]

To my knowledge, all should be the same with the possible exception of the 
authorization which was already beginning to transition. In other words, 
neither the iLok method or the built-in method is accessible yet. Both will be 
accessible in time, probably one before the other. At any rate, I've only had 
beta experience and, to me, it looks the same as far as I can tell. Mind you, 
I'll have to purchase an upgrade like everyone else but for the HD users, the 
cost is $599 and I won't be using it on the new machine yet so I might wait 
just a little while. Apparently, there's no option for a co-install of 11 and 
12. Therefore, it would seem to me that this means no co-install of 10 and 12 
as well. There's a lot of confusion about what the real case is. This is all 
pretty new to everybody so it's probably a good idea to wait until the dust 
settles.

Slau

On Mar 23, 2015, at 3:45 PM, Nickus de Vos  wrote:

> Hi Slau
> So just to be clear, in terms of accessibility, nothing really new in
> 12 but also nothing broken?
> 
> On 3/22/15, Slau Halatyn  wrote:
>> I'm not going to be breaking any NDA by saying this and, besides, it's no
>> secret that Pro Tools 12 will be coming out soon, like, maybe even tomorrow.
>> Please be aware that there is essentially nothing different about its
>> accessibility. There's a newly designed I/O Setup but, to a VoiceOver user,
>> it appears much the same. If anything, there are a few extra controls.
>> 
>> The authorization aspect of Pro Tools will be changing and it's unclear
>> whether this will change right from this new release or whether it'll be
>> incorporated over time but it won't be any more accessible than standard
>> iLok authorization for now. Be assured, however, that it will be made
>> accessible. More info to come as it becomes clearer.
>> 
>> 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.

Re: a word about Pro Tools 12

[Nickus de Vos]

Hi Slau
So just to be clear, in terms of accessibility, nothing really new in
12 but also nothing broken?

On 3/22/15, Slau Halatyn  wrote:
> I'm not going to be breaking any NDA by saying this and, besides, it's no
> secret that Pro Tools 12 will be coming out soon, like, maybe even tomorrow.
> Please be aware that there is essentially nothing different about its
> accessibility. There's a newly designed I/O Setup but, to a VoiceOver user,
> it appears much the same. If anything, there are a few extra controls.
>
> The authorization aspect of Pro Tools will be changing and it's unclear
> whether this will change right from this new release or whether it'll be
> incorporated over time but it won't be any more accessible than standard
> iLok authorization for now. Be assured, however, that it will be made
> accessible. More info to come as it becomes clearer.
>
> 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.

Re: Pro-tools 12 just released

[Nickus de Vos]

Yes, from what Slau said in a different post it sounded like there's
nothing new in terms of accessibility in 12 right now, I also hope
nothing is broken.

I'm not 100% on this yet, but from what I could find out so far it
looks like upgrading from 11 to 12 will cost $199.
So now I'm just wondering, if I baught PT11 a month or so ago, what
would have happend, what about the entire all updates free for the
year of your support plan thing? I would have kicked myself if I
baught PT11 just a week ago but luckally some things got in the way,
I'll get clarity on upgrading from 11 to 12 and whether it might be
free, then I'll decide whether to buy now or wait a bit longer.

On 3/23/15, Chris Harrington  wrote:
> There aren't any excess ability changes  from ProTools 11 to 12.
> Chris
>
> Sent from my iPhone
>
>> On Mar 23, 2015, at 2:10 PM, Christopher-Mark Gilland
>>  wrote:
>>
>> I wonder if the accessibility is worth the upgrade?
>>
>> Chris.
>> ---
>> Check out my web site at:
>> http://www.clgproductions.net
>> - Original Message -
>> From: Nickus de Vos
>> To: ptaccess@googlegroups.com
>> Sent: Monday, March 23, 2015 2:08 PM
>> Subject: Pro-tools 12 just released
>>
>> Hi all
>> Just saw that Avid released PT12
>> http://www.pro-tools-expert.com/home-page/2015/3/23/pro-tools-12-goes-on-sale-in-the-avid-store.html?utm_source=dlvr.it&utm_medium=twitter
>>
>> I was about to buy PT11 tomorrow, so guess I'll wait a bit.
>> --
>> 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.

Re: Pro-tools 12 just released

[Chris Harrington]

There aren't any excess ability changes  from ProTools 11 to 12.
Chris

Sent from my iPhone

> On Mar 23, 2015, at 2:10 PM, Christopher-Mark Gilland  
> wrote:
> 
> I wonder if the accessibility is worth the upgrade?
>  
> Chris.
> ---
> Check out my web site at:
> http://www.clgproductions.net
> - Original Message -
> From: Nickus de Vos
> To: ptaccess@googlegroups.com
> Sent: Monday, March 23, 2015 2:08 PM
> Subject: Pro-tools 12 just released
> 
> Hi all
> Just saw that Avid released PT12 
> http://www.pro-tools-expert.com/home-page/2015/3/23/pro-tools-12-goes-on-sale-in-the-avid-store.html?utm_source=dlvr.it&utm_medium=twitter
> 
> I was about to buy PT11 tomorrow, so guess I'll wait a bit.
> -- 
> 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.

Re: feedback needed for Pro Tools 12

[Scott Chesworth]

Hi Brian,

I see your question has already been answered, but it raises another
one. The way its phrased suggests that you can read gain reduction
with your current setup. I'm curious about what you're using, just
because in both of my regular DAWs it isn't doable. Feel free to drop
me a line off list so we don't stray off topic.

Cheers

Scott

On 3/23/15, Brian Howerton  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 
>> 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 
>>> 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  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  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
 >> peo

Re: Pro-tools 12 just released

[Christopher-Mark Gilland]

I wonder if the accessibility is worth the upgrade?

Chris.
---
Check out my web site at:
http://www.clgproductions.net
  - Original Message - 
  From: Nickus de Vos 
  To: ptaccess@googlegroups.com 
  Sent: Monday, March 23, 2015 2:08 PM
  Subject: Pro-tools 12 just released


  Hi all
  Just saw that Avid released PT12 
http://www.pro-tools-expert.com/home-page/2015/3/23/pro-tools-12-goes-on-sale-in-the-avid-store.html?utm_source=dlvr.it&utm_medium=twitter


  I was about to buy PT11 tomorrow, so guess I'll wait a bit.

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

Pro-tools 12 just released

[Nickus de Vos]

Hi all
Just saw that Avid released PT12 
http://www.pro-tools-expert.com/home-page/2015/3/23/pro-tools-12-goes-on-sale-in-the-avid-store.html?utm_source=dlvr.it&utm_medium=twitter

I was about to buy PT11 tomorrow, so guess I'll wait a bit.

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

Last Chance to Enter the Dynamic Range Day 2015 Competition

[Chris Smart]

Time is running out to enter the Dynamic Range Day 2015 competition, 
over $10,000 in great prizes! Plus, you'll be helping to spread the 
word that dynamic music is better music! Go to:

http://splur.gy/r/BrqcQ/r/2XDNncVTwGM

Chris

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

Re: SPL Transient Designer is fully accessible

[Keith Reedy]

Slau,

Thanks for this, exciting to think about the control.  I think I will take it 
for a spin in Logic.
kr
On Mar 21, 2015, at 9:09 PM, Slau Halatyn  wrote:

> Having used the hardware version, I had always wanted to check out the 
> plug-in. Just wanted to mention that it is, in fact, completely accessible. 
> Just like its hardware counterpart, it only has a handful of controls which 
> are all very useable. Further, there are already a bunch of presets in the 
> preset pop-up menu. Finally, although iLok authorization is supported, it's 
> not necessary and you can authorize up to three computers online without 
> using any iLok. If you purchase through a retailer, you'll still have to 
> create a Plug-in Alliance account to redeem the code for the download but 
> it's quick and easy. Better still, you can download a free trial that 
> requires no dongle. Check out more info here:
> https://www.plugin-alliance.com/en/products/spl_transient_designer.html
> 
> 
> HTH,
> 
> 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.

Re: feedback needed for Pro Tools 12

[Gordon Kent]

``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  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  
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  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  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  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 m

Re: feedback needed for Pro Tools 12

[Chris Smart]

Oh I agree regarding auto makeup gain. You want to train yourself 
using a compressor that allows you to turn auto makeup off, or 
doesn't have it at all. i.e. i fthere's a manual makeup gain control, 
leave it off while you're playing with things.


At 11:16 AM 3/23/2015, you wrote:

Using your ears is fine, However, with compressors that feature
automatic make up gain, it could be quite tricky to hear what the
compressor is actually doing, because the gain is being made up in
real time as you adjust the controls. For this reason, it would be
great to have the gain reduction meters read by voiceover. Also, I
agree with the person who said that it would be good to be able to
type in values for parameters in plugins.
Jason

On 3/23/15, Brian Howerton  wrote:
> Hi Slau,
> No, that is a great answer, and something that I needed to 
hear.  After all,

> it really is about using your ears.
> Brian
>> On Mar 23, 2015, at 9:45 AM, Slau Halatyn  wrote:
>>
>> 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 
>> 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 
>>> 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 
 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  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  wrote:
>>>

Re: feedback needed for Pro Tools 12

[Chris Smart]

it does take awhile to develop, especially if you're just talking a 
dB or two of gain reduction, and the compressor being used is very 
transparent. you might drive yourself nuts saying "ok, is it on? is 
it off? hmm i think it's on..." all part of the fun!


At 10:52 AM 3/23/2015, you wrote:

Hi Slau,
No, that is a great answer, and something that I needed to 
hear.  After all, it really is about using your ears.

Brian
> On Mar 23, 2015, at 9:45 AM, Slau Halatyn  wrote:
>
> 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  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 
 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  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  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  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 simpl

Re: feedback needed for Pro Tools 12

[Jason Dasent]

Using your ears is fine, However, with compressors that feature
automatic make up gain, it could be quite tricky to hear what the
compressor is actually doing, because the gain is being made up in
real time as you adjust the controls. For this reason, it would be
great to have the gain reduction meters read by voiceover. Also, I
agree with the person who said that it would be good to be able to
type in values for parameters in plugins.
Jason

On 3/23/15, Brian Howerton  wrote:
> Hi Slau,
> No, that is a great answer, and something that I needed to hear.  After all,
> it really is about using your ears.
> Brian
>> On Mar 23, 2015, at 9:45 AM, Slau Halatyn  wrote:
>>
>> 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 
>> 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 
>>> 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 
 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  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  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 s

Re: feedback needed for Pro Tools 12

[Brian Howerton]

Hi Slau,
No, that is a great answer, and something that I needed to hear.  After all, it 
really is about using your ears.  
Brian
> On Mar 23, 2015, at 9:45 AM, Slau Halatyn  wrote:
> 
> 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  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  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  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  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  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 marath

Re: feedback needed for Pro Tools 12

[Chris Smart]

agreed. learn to notice when a compressor is active and when it isn't.

At 09:45 AM 3/23/2015, you wrote:

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

Re: feedback needed for Pro Tools 12

[Christopher-Mark Gilland]

Brian,

Please call me at some point today.  Haven't heard from you in a while, and 
would absolutely love! to catch up.

This number is public knowledge, as it's my work desk phone, so I have no 
problem at all giving you this number on list.

704-594-2225X701

---
Check out my web site at:
http://www.clgproductions.net
  - Original Message - 
  From: Brian Howerton 
  To: ptaccess@googlegroups.com 
  Sent: Monday, March 23, 2015 9:39 AM
  Subject: Re: feedback needed for Pro Tools 12


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

Re: feedback needed for Pro Tools 12

[Slau Halatyn]

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

Re: feedback needed for Pro Tools 12

[Slau Halatyn]

Hi guys,

The issue of changing plug-in values in greater increments is one of those 
situations where a paradigm shift would need to take place for it to be 
different. That, of course, might happen at some point but not right now—not 
yet, at least. For the time being, a control surface is your friend and you can 
change parameter values at whichever rate you choose. Be assured, however, that 
plug-in issues will be looked at for the long run.

The reduction meters are also on the list. Mind you, of course, I will have one 
day to address all concerns and we simply won't get to everything. Whatever we 
gain is better than nothing and I'm hopeful that a number issues can be 
addressed. 

Cheers,

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.

Re: feedback needed for Pro Tools 12

[Brian Howerton]

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

Re: feedback needed for Pro Tools 12

[Kevin Reeves]

The faders are Post compressor.
This means that when you turn up the level, you are increasing what 
happens after compression is applied.
In the compressor plug, there's an input fader as well, so you can feed 
more into the comp if you want.


Hope this helps.

Kevin
On 3/23/2015 8:50 AM, David Eagle 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 > 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 > 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 > 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 t

Re: feedback needed for Pro Tools 12

[David Eagle]

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

Re: feedback needed for Pro Tools 12

[studiojay]

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