I have a collection of DSP plug-ins such as Clariphonic II, Electra, Omega 458a, etc. These worked in previous versions of Audirvana+. I don’t remember when they stopped working, probably about a year ago. I have recently updated all of them to be Catalina compatible, yet none of them work in Audirvana 3.5.41. Why is that?
Btw, the same plug-ins do work in Windows 10 version of Audirvana (VST3). Yet, nether the AU, VST or VST3 plug-ins work in the Mac version. Please help, these plug-ins were not cheap.
Are you using MacOs Catalina 15.7? We use a tool to determine if an audio unit plugin is compatible with the version of MacOS we use and it couldn’t find the Omega 458a plugin in the list which is quite odd since it is installed in the proper folder in MacOs.
I am using the latest version of Catalina. As I said, other applications, including the older Audirvana+, see the plugins and they can be configured and they work. It appears the problem is with Audirvana.
If the plugin works in Audirvana 2 this means taht it’s using the older version of the Apple version of the viewing controller of MacOs.
We use - (void)requestViewControllerWithCompletionHandler:(void (^)(AUViewControllerBase *viewController))completionHandler; when we start the plugin in Audirvana, this is where our crash started, are you using this Instance Method in your plugin?
Based on the information you provided, you must think I am a developer, I am not. Kush UBK plugins are professional plugins that musicians and producers use in various professional audio applications, on the Mac in Catalina. I use them as well. If it works in other applications, why would it not work in Audirvana?
Can you please update the way AU plugins are accessed in the next release of Audirvana, to also include the method Audirvana+ was using? It seems your current parameters are too strict.
It’s exactly this, the plugin you are using is not adapted to the latest version framework of Apple. When you use the older version of Audirvana, it has been coded based on the older version of this framework, this is why you can see it in Audirvana 2 but not in 3.5 as we are constantly evolving the app when there is a new version of the framework.
I know you are not a developer, what I gave you in my previous message is what you need to say to Kush support team so they can transmit the information to the development team.
Hi, I finally was able to get a response from Kush Audio, which is pretty much what I had expected.
From Kush Audio: “I’ll be honest. I don’t think we’ve ever received any reports with Audirvana. In fact, I’ve never heard of that program until now. I have no idea what the devs use regarding the latest Apple framework. I can pass along your report to our dev but because it’s one report with a program that isn’t a DAW, I highly doubt it will be looked at. Kush plugins are developed to work in DAW’s. If they don’t work in other applications that can open plugins, it certainly will be very low priority of things Kush is working on.”
Oh well, I was able to enjoy these plug-ins for at least a little bit while they worked in older versions of Audirvana. It was good while it lasted. Now I feel a little bit like I’m stuck between two developers who are pointing fingers at one another, and there is nothing I can do about it.