MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
https://www.motunation.com/forum/
Yeah... strange that AU doesn't work. That's one of the PSP plugs I don't own. But yeah... as I said to Michael previously, I wasn't aware that developers were releasing VST2 as UB2... thought (wrongly) only VST3 could be UB2. Learn something every day. Cubase (again, I just dabble with it) does not AFAIK recognize VST2 that are UB2 since I think Steinberg is probably all about pushing VST3 so they're not going to support it in the flagship DAW. I know this caused a lot of consternation with UAD-2 plugin users as they were forced to run Cubase in Rosetta (2) to keep using their DSP plugins.mikehalloran wrote: ↑Fri Apr 05, 2024 5:17 pm This package installs an AU, VST2 and VST3. The AU does not work on my system but the others do. Only the AAX requires Rosetta 2.
The plugin developing SDKs are OK I guess, but everything is different, they left out MIDI entirely etc. They all pretty much hate it. Even worse is hosting, it's why it took so long to adopt. I think DP beat Live to VST3 for instance because they more or less had to for the Windows version. It's taken 15 years for 99% of the plugins out there to have VST3, that says everything. I was moving to VST before this, but I think going forward my strategy is AU and VST3 for plugins like Blue Arp, Reason Rack, MPC, Melodyne obviously etc.James Steele wrote: ↑Fri Apr 05, 2024 5:02 pm Seems many developers now are releasing only in AU, VST3 and AAX... all UB2. I guess VST2 will be with us for a while, but maybe after more developers get the hang of it, VST2 will go away except for legacy plugs. I wonder why Steinberg's APK and documentation (from everything I heard) is so horrendous that developers had a hard time. I know I read someone say aspects of it had to be reverse engineered by plugin developers. If Steinberg's documentation is THAT bad, it kinda borders on criminal. How can you expect developers to support a standard under those conditions?
That's what I've been doing for a while now: using primary AU and then VST3 for Melodyne obviously, and also VST3 for Console 1 since VST3 is the required format in DP to support full integration with the hardware controller. Not sure why DP requires that because I think Logic has full support (perhaps more extensively than DP) and it uses AU obviously. Although I think Logic can use AU3, which I don't think DP is fully on board with?Michael Canavan wrote: ↑Fri Apr 05, 2024 9:52 pm...but I think going forward my strategy is AU and VST3 for plugins like Blue Arp, Reason Rack, MPC, Melodyne obviously etc.
The whole thing is insane, I really wish CLAP had been introduced 15 years ago when Steinberg decided to flush a perfectly good architecture in VST2 and Apple decided to make a one OS only plugin format. Could have saved a lot of grief, but VST2 worked back then, and AU assured a working plugin format on Mac OS.James Steele wrote: ↑Fri Apr 05, 2024 10:15 pmThat's what I've been doing for a while now: using primary AU and then VST3 for Melodyne obviously, and also VST3 for Console 1 since VST3 is the required format in DP to support full integration with the hardware controller. Not sure why DP requires that because I think Logic has full support (perhaps more extensively than DP) and it uses AU obviously. Although I think Logic can use AU3, which I don't think DP is fully on board with?Michael Canavan wrote: ↑Fri Apr 05, 2024 9:52 pm...but I think going forward my strategy is AU and VST3 for plugins like Blue Arp, Reason Rack, MPC, Melodyne obviously etc.
The remaining cases where I use VST3 are when the AUs have serious issues. Right now I have an issue with Blue Cat Audio PatchWork. If I add it to my Component folder it shows up TWICE in DP's Audio Plugins prefs. I have to enable BOTH to get anything to happen and if I do, instantiating it causes it to crash.
I also do something weird with Komplete Kontrol. I run both AU and VST3. I run the last Intel-only version of Komplete Kontrol (2.7.2) as an AU. This way it's forced to use Rosetta for that instance. I instantiate that version when I want to use NKS with an older VST2 instrument. I use the VST3 version of Komplete Kontrol (2.9.6) for all other NKS VST3 instruments. They appear with the same name in the menu when creating a new Instrument Track... but the second one is the older one. It's a lot of trouble I know. To make it easier, I edited the plugin thumbnail graphics that appear on my S88 Mk2's screens to include a little red box and the lower left with white letters that says "VST2" so that I don't attempt to open it when I'm running the Apple Silicon version of Kontakt, else I'll get an error. I haven't adopted Komplete Kontrol 3 yet. Not in a hurry there.
Oh... as VST3 becomes more robust though many of them are becoming redundant on my Mac. I'm planning to go on a seek and destroy mission and delete some more soon. One thing to be careful of though is with the Korg Collection... some of their older plugs depend on the presence of the VST2 to function. The other formats are wrappers.
I just made a very quick and dirty iPhone video which should answer those questions. But yes... Hybrid 3.0.7 (VST2) as well as AIR Music's Xpand! 2.2.11 (VST2) and NI Absynth 5.3.4 (VST2) all work for me inside of Komplete Kontrol AU 2.7.2 inside of DP 11.31 running AS native on (for me) Sonoma 14.5 Public Beta. As I mentioned, using the 2.7.2 version of KK, will make the plug run in Rosetta2 and thus be able to open the VIs I mentioned and they all seem to work well. I also opened iZotope Iris 2 VST2 inside Komplete Kontrol 2.7.2. It will also run directly in DP 11.31.Michael Canavan wrote: ↑Fri Apr 05, 2024 11:54 pmI'm really curious about trying the Rosetta KK trick? There are a few VSTs that work in Bitwigs own wrapper for Intel VSTs, and they work a hell of a lot better than they do in Apples Rosetta AU format. Namely Absynth, Loom II, and Hybrid 3. I wonder how well they would work in Rosetta AU KK?
To be clear here, that's not the case at all. I have Live, and Reaper installed here and both can run AU, VST2 and VST3 plugins all in the same project, and all three formats are available for Diva etc. etc.James Steele wrote: ↑Sat Apr 06, 2024 12:55 pm What just occurred to me is that AFAIK, DP is the only Mac DAW that can pull off this trick, because it's the only Mac DAW that can use both VST3 *and* AU at the same time. AU is the only format that can use Rosetta 2 per plugin without needing to launch the DAW itself in Rosetta. So use KK 2.7.2 AU to load VST2 VIs.... use KK 2.9.6 VST3 to load VST3 VIs
I don't have the installer anymore, but I think you can just drop in the component file. I will attach it to this post and you can try it. I don't know anything about the backend. I had to restore this machine once so it has no residual of KK 3 on it. What I would do is archive the 2.7.2 AU before running the 2.9.6 installer so when it overwrote the AU, I could delete 2.9.6 and replace it with 2.7.2.Michael Canavan wrote: ↑Sat Apr 06, 2024 2:35 pm Hey one thing I'm curious about is how you got the Applications fro 2.72 and 2.9 in the same machine? or is it just that the Komplete Kontrol AU plugin for 2.7.2 can use the back end of the 2.9 KK application and runs in Rosetta natively? Currently I have the latest 3.2.1 AU and VST 3 and the 2.9.4 VST 2. I'm not sure how I could get ahold of the 2.7.2 AU for KK?
To be clear here, that's not the case at all. I have Live, and Reaper installed here and both can run AU, VST2 and VST3 plugins all in the same project, and all three formats are available for Diva etc. etc. [/quote]James Steele wrote: ↑Sat Apr 06, 2024 12:55 pm What just occurred to me is that AFAIK, DP is the only Mac DAW that can pull off this trick, because it's the only Mac DAW that can use both VST3 *and* AU at the same time. AU is the only format that can use Rosetta 2 per plugin without needing to launch the DAW itself in Rosetta. So use KK 2.7.2 AU to load VST2 VIs.... use KK 2.9.6 VST3 to load VST3 VIs
Just checked Absynth... and it was pretty good. Did some clicking around just now in Hybrid 3 and one of the menus shut down the MOTU engine. Just took a look again and the presets menu works fine and seems stable, but if you click the Parts Presets and scroll it shuts down MAS with this error:Last question if you don't mind. I'm currently able to run Absynth, Hybrid 3 and Loom II in AU as Rosetta plugins in DP, Live and Reaper etc. but they do not respond GUI wise, mostly Hybrid 3 and Loom II do not allow you to change setting via drop down menus, which of course is far from ideal. The only DAW or situation here that works is Bitwig, which only uses VST and came up with their own non Apple Silicon VST2 plugin hosting solution, the drop down menus work there. I have Unify and although it can also host non Apple Silicon native VST2's, they still have the drop down menu issue. Anyway long way of asking if the VST2 plugins hosted in KK as an AU are capable of using their drop down menus? Hybrid 3 for example?
Oops... attachment was too large. Here's the KK 2.7.2 component:Michael Canavan wrote: ↑Sat Apr 06, 2024 2:35 pmCurrently I have the latest 3.2.1 AU and VST 3 and the 2.9.4 VST 2. I'm not sure how I could get ahold of the 2.7.2 AU for KK?
Jim, you have to enable them by hand, Enable all just enables whatever main choice you made, VST2 or VST3. that's another question, are you able to see in the DP preferences plugin chooser MAS, VST and VST3 as separate choices? if you are, then again, you have to select them in the list then enable them, otherwise again, it will enable only the choice you made in the chooser, look at this window, do you have that chooser for the main VST type? See the three greyed out buttons labled Enable, Disable and Reexamine? they're greyed out because there's no selection in the plugins to operate on. If the Windows plugin chooser is working correctly you should see a list with MAS, VST2 and VST3 plugins, whatever is your Primary plugin choice will likely already be selected, you need to select the plugins individually and likely you can use shift to select ranges, then Enable them, and Reexamine them if they failed evaluation etc.Westlyn wrote: ↑Sat Apr 06, 2024 4:27 pm Hey Guys:
The thread has gone off in another direction - more Apple/Mac oriented - and I'm a Windows 10 guy.
So, I thought I would start again.
I can find no way to get both VST2's and VST3's to work together. With all your helpful advice, I'm getting nowhere.
Each time, I make any change in the Primary all the other VST's are unavailable. It keeps inventing more Enable All's.
I haven't done anything intentionally, but I've got Enable All.2.2.2.2.2.2...
There's no reason this should be so complicated. I spend all my time fighting the software and no time WRITING Music.
Do I need to talk to Tech Support at MOTU?
I'm not investing any more time in this.
You guys have been Great!
Jim Westlyn
Stop changing the Primary. Just enable all the plugins you have, and leave the Primary preference alone. It doesn’t matter what you set it to until you install a new plugin. Then you’ll have to go back to preferences and enable all the versions of that plugin that you migth want to use.