3rd party plug-ins aren't recognized

[ashahay]

Like I said, I'm using the latest version my purchases will allow me to use.

I'd love to use Pro tools 12.6+ but I can't without paying for an upgrade. Same with Melodyne and RX.

Seems like a bloody joke that I have to pay to use a version of Pro Tools thats compatible with macs.

[Darryl Ramm]

You really need to worry about this before spending many thousands of dollars on a new Mac Pro. If you really *have* to run old software the safest approach is to try to check for sure what will run first or worse case to buy a referb Mac that can accept an old OS X/Mac OS install.

If you want to make this into a business you have to get on top of this stuff.

Like I said what you can try is quick/obvious I would not give up until you have carefully tired that, if that does not work that so are the next steps to upgrade Pro Tools.

[ashahay]

Okay so I tried deleting prefs but that didn't help.

Seems ridiculous how incompatible the new mac OS is with software, considering their slogan is "it just works!"...
I figured it'd just work considering this mac model came out before my current version of Pro Tools. I just didn't think their latest OS would be so dodgy.
It's also sorta strange that I had 3 major Pro Tools updates but it stopped at 12.3.

Seems like people are going to a lot of effort to use older OS's or hacking Sierra so its compatible with older software, while creating new problems or becoming incompatible with newer software.
I feel sorry for those guys with outdated Pro Tools HD rigs and families that have to pay so much money to upgrade while finding enough business to stay afloat is hard enough already.
I just hope people read threads like this before deciding to make the swap to mac like I did.

Anyway, I appreciate your help mate, and luckily the new version of pro tools seems justifiable with all the new features. I'm surprised they didn't just lable it PT13 lol

Another thought- i'm in the process of setting up bootcamp, so hopefully that will allow me to run Pro Tools and its plug-ins without any issues.

[Darryl Ramm]

Apple goes out of their way to force customers to run the latest major OS. It's very unlike the Windows PC OEM market. Apple rolls the OS installed on all new Macs where there is a major new release, like what happened here with Sierra, and they dink with stuff so you can't install an older release on that new Mac. It has nothing to do with the original release date of the hardware model. This is how Apple has operated for years and you got burnt by that, next time ask on DUC well before making any huge changes like what you have just gone through.

[ashahay]

True that, thanks legend.

So I installed bootcamp, then Pro Tools etc. and Hallelujah my plug-ins work!!
Guess I don't have to pay for the latest Pro Tools after all :)

[Darryl Ramm]

Brilliant. That is one brute force way to fix the problem


Sent from my iPad using Tapatalk

[musicman691]

Originally Posted by Darryl Ramm

Brilliant. That is one brute force way to fix the problem


Sent from my iPad using Tapatalk

Except it doesn't fix the root cause. For me I'd do anything not to go back to Windows.

[ashahay]

Okay, so I had a critical error on my windows partition and had to swap back to my mac in order to finish a job with a deadline of 3 days.

I immediately bought the latest subscription to Pro Tools and installed it- which should be fully compatible with my Mac OS.

So can anyone tell me why the hell Pro Tools still can't recognize any additional plug-ins?? even my newly bought Avid Pro series plug-ins aren't showing, which is absolutely essential to getting any work done.

[Darryl Ramm]

Did you trash prefs?
Uninstall and reinstall the plugins?

[ashahay]

Okay, so I figured out what the problem is.
For some reason Pro Tools doesn't read the AAX plug-ins folder, but it does read the core-plugins folder inside the Pro Tools application package.

Basically, I copied all plugins from the AAX installation folder: Macintosh HD/Library/Application Support/Avid/Audio/Plug-Ins
and pasted them into: applications/Pro Tools/Contents/PlugIns/Core Plug-Ins
Note: to open Pro Tools contents you go into applications, right click Pro Tools, and select 'Show package contents'.

When I next started Pro Tools it loaded every plug-in and it's working fine.

This had nothing to do with compatibility, but more so mac and Pro Tools miscommunication with plug-in folders