Problems under Mac OS Sonoma 14.1

[Oli Ullmann]

Hello all,

one of my beta testers told me today that my AU PlugIn no longer works since the update to Mac OS Sonoma 14.1. Has anyone had similar experiences?

I am using HISE version 3.5.0

Many thanks for your feedback! :-)

All the best
Oli

[d.healey]

@Oli-Ullmann said in Problems under Mac OS Sonoma 14.1:

my AU PlugIn no longer works

In what way?

[Oli Ullmann]

@d-healey
Hey David,

the plug-in can no longer be loaded into Logic. Since he works with a German system, he naturally receives a German error message. The translation is as follows:

"An Audio Unit plug-in has reported a problem that could cause system instability. Quit Logic Pro and restart."

He also told me that a plug-in from "Rogue Amoeba" can no longer be loaded either. So it's not just my HISE plug-in that's affected.

@Christoph-Hart , is there something that needs to be changed in HISE?

[d.healey]

@Oli-Ullmann Does it work in Reaper?

[Oli Ullmann]

@d-healey Unfortunately, I don't know because I don't own Reaper. Do you have Reaper under Sonoma 14.1 or 14.2? If so, could you test the plug-in on your system? I would only send you the AU / VST3 file, without the sample content. This is a whole 9GB in size...

[d.healey]

@Oli-Ullmann I don't have Sonoma installed on a system yet. Just download Reaper, it's tiny - http://reaper.fm/download.php

If it works in Reaper then we know it's a Logic specific issue.

Did Apple update Logic when they updated the OS?

[Oli Ullmann]

@d-healey Ah cool, thanks to you! I'll download Reaper and give it a try. Or I'll ask my beta tester to do so, as I'm still working on Ventura myself and won't be updating my system at the moment.

Yes, Logic has also been updated to version 10.8. Therefore we do not know at the moment whether it is the Logic update or the OS update.

As soon as I have feedback from my tester, I will get back to you. Thank you very much for your support!

[Christoph Hart]

@Oli-Ullmann try cleaning the AU cache and rescanning all plugins, most likely a caching issue, but that stuff can drive you nuts...

[Oli Ullmann]

@Christoph-Hart Thank you! We will also try this!

[Oli Ullmann]

@Christoph-Hart @d-healey
Hello Christoph, hello David,

the solution was to clear the AU cache. Now the plug-in can be loaded again. Many thanks for your help! :-)

All the best
Oli