I have had this problem as well, can you point me to that article or
whatever the equivalent procedure should be used with vo?
On Sun, 06 Aug 2017 11:41:57 -0400,
Tim Burgess wrote:
> [1 <multipart/alternative (7bit)>]
> [1.1 <text/plain; UTF-8 (7bit)>]
> [1.2 <text/html; UTF-8 (quoted-printable)>]
> I've just set up a Mac Mini with the latest PT and FT. However, if I create a
> new session from any of the stock templates, I get an error indicating that
> some required AAX plugs are missing. I've found an article that describes
> steps for
> solving this as a sighted user (i.e. check the inserts for each track to see
> what they're trying to use, then validate that the plug-in is where it is
> supposed to be), but I want to check that my FT method is correct. If I query
> inserts for each track, I hear the name of the plug-in, which is great.
> However, I have one track using an organ instrument where the plug-in is
> described as "disabled". Obviously, this looks like my bad plug-in, but I
> wanted to check
> that "disabled" means that there's a problem and not that it means something
> like "frozen", etc.. I'd greatly appreciate any advice on this, so thanks in
> 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.
Your life is like a penny. You're going to lose it. The question is:
you spend it?
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
For more options, visit https://groups.google.com/d/optout.