It really did work, Slau. I even just tested it again with 10 over here,
and it definitely did work.
Chris.
----- Original Message -----
From: "Slau Halatyn" <slauhala...@gmail.com>
To: <ptaccess@googlegroups.com>
Sent: Friday, August 28, 2015 10:51 AM
Subject: Re: confirmed plug-in automation issue
Hi Matt,
It would be helpful to know whether it was truly working or whether it was
volume or pan automation that worked. Let me know.
Slau
On Aug 28, 2015, at 10:28 AM, Martin (Punky) Sopart <m...@cakewalker.de>
wrote:
Matt!
During your tutorials I think you only automated a fade by using the
volume slider inside the master fader.
Best! / Martin
-----Original Message-----
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
On Behalf Of Matt Diemert
Sent: Friday, August 28, 2015 4:18 PM
To: ptaccess@googlegroups.com
Subject: Re: confirmed plug-in automation issue
Actually, I believe in ProTools 10.0 it was possible to automate
plug-ins from
the keyboard. I vaguely remember doing a bid on it during the creation
process of our tutorials, and I think we decided against it for one
reason or
another but I'm going to see if I can track down the audio and listen to
it to
see if it worked. I also have an old machine around here that still has
10 on it
maybe I will fire it up when I get home tonight and just make sure that
I'm
right.
Sent from my iPhone
On Aug 28, 2015, at 9:54 AM, Slau Halatyn <slauhala...@gmail.com>
wrote:
I just got into the studio and confirmed the issue with trying to write
automation using only VoiceOver. Over the years where we've had no less
than 10 VoiceOver users beta test Pro Tools, not once has anybody
reported
this issue. That, of course, is not surprising since most of the users
have
control surfaces and would never dream of writing automation using only
VoiceOver. Those testers without a surface clearly never got around to
testing this specific aspect. From an accessibility standpoint, the
knee-jerk
reaction is to look at things that are unlabeled or invisible, etc.
Functionality
such as this is taking it a step further and so it's not inconceivable
how this
could be the case. I've confirmed the behavior in both version 11 and 12
and I
doubt it was any different going back to version 8.
Anyway, as I said earlier, this won't get fixed in the upcoming release
but I'll
submit a bug report for the future.
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.
--
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.
