macOS High Sierra = Carbon Component Manager deprecation


#1

Just wanted to clarify. The deprecation of the Carbon Component Manager won’t affect JUCE plugins that have JUCE_SUPPORT_CARBON disabled, correct?

ie I won’t have to rebuild old plugins that never had that enabled in the first place?

In the IPLUG community they are discussing it here: https://forums.cockos.com/showthread.php?p=1884702


#2

juce has supported audiocomponent entry point for a long time. I’ve noticed some odd behaviour with au validation & apple products on 10.13 to do with this though, so it might be worth checking.


#3

Thanks Oli, when I update my aux machine to 10.13 in a few days I’m going to test all our current builds. Will report back here.


#4

I tested all our JUCE plugins after doing an update install (without erasing my drive) and a clean install (first erasing my drive). Both work fine, however I may have ran into some macOS bugs when doing the clean install. Skype and Reaper wouldn’t install, but after I restarted (where there was a really weird turquoise screen before it restarted) those programs installed fine. Could have an effect on AU plugins showing up too perhaps, as shown in that Reaper forum thread.


#5

As I’ve also replied on thread @cockos.

We have yet to see regression in support of some API (mind the yet :wink: )
One product is actually hosting AUs (using in-house code not JUCE) to allow 32-bit wrapped to 64-bit using IPC.
So far even very old plug-ins show-up and works from my tests under Logic X.

The only quirk was with plug-ins (also new ones compliant to latest standards) not showing or scanning until I restart my machine.
Even clearing caches simply made auval+LogicX scan the plug-ins that were already showing up and still ignoring the ones I’ve just installed.