Hi all,
I think this situation is really dangerous for accessibility in protools!
Maybe a petition to report at Avid the problem with this new plugin format and
to remember them they still need to do more for full accessibility in protools
could be a not-so-bad idea…
Just my thought, as a blind not using protools yet, but interested in doing it
in the next future...
Vincenzo.
Il giorno 05/giu/2012, alle ore 03:56, Kevin Reeves ha scritto:
> The problem is, avid moves to a proprietary plug-in format called AA X. We've
> all noticed that these AA X plug-ins are now broken. I'm not quite sure what
> to do about this, but that is the reason that I'm not upgrading to 10 yet.
> Because I had a demo of 10, and noticed that half of the plug-ins didn't work
> that were a a x Hence why I'm sticking with nine.
>
> Sent from my iPhone
>
> On Jun 4, 2012, at 9:08 PM, "Christopher-Mark Gilland"
> <clgillan...@gmail.com> wrote:
>
>> OK, either I am doing something royally wrong, I'm just totally! profusely
>> stupid, or something...
>>
>> I! just upgraded to PT 10.2. This isn't M P like i had before. This is the
>> full PT 10.2 standard.
>>
>> I'm finding that over half the plugins that natively come with PT do not
>> read any longer hardly at all, I can't click the librarian menus in hardly
>> any of the plugins, unless I literally route my mouse pointer, then actually
>> not jsut vo+space, but full on click with vo+shift+space. Then, I can't
>> reach any of the perametors to make fine tuned ajustments, rather than
>> helping my vocals, it made them sound God aweful right out of the box, as it
>> literally cut automatically so much of the low end that not only did it just
>> naturally with no processing cut all the mud out, it cut so! much out that
>> now my vocals are ear bleeding piercing! I thought with the e q 3/7 band
>> plugin, I could maybe notch up the lows around 200hz a bit, but nope? I
>> can't get to a single one of the controls in the plugin. If I press
>> vo+space on a plugin window, it doesn't seem to close. Instead it just
>> shits there and does nothing. Routing the mouse pointer then doing
>> vo+shift+space isn't working either. If I hit command W, it closes the
>> window behind it, which generally is the mix window, instead of closing the
>> plugin. Pressing shift+R, shift+S, or shift+M on any selected tracks isn't
>> working. Within a plugin the plugin combo box window is reported the
>> incorrect plugin that is loaded. It's saying something about plugin package
>> A A something or another native. The truth! is I actually! have the 3/7
>> band e Q window up instead.
>>
>> What the hell! is the deal! This R'r'r'r'really! pisses me off something
>> fierce!
>>
>> Lookat: I got a band coming to do a real late night recording session. I
>> can't do anything! They refuse to use p t 9 as some of the gear they use
>> isn't compatible with my old m p 9 so I can't just reinstall that. Yeah? Of
>> course! I restarted Voiceover. many? Many! times. It did no good.
>>
>> I even restarted my whole macbook, with no help.
>>
>> I'm on 10.7.4 Lion.
>>
>> What! on earth!
>>
>> If this is how pt's gonna become and evolve to, then I"m gowen back to
>> Sonar! LOL! This is ridiculous!
>> Chris.
