VST plugins not being scanned - DP11, macOS 12.5, M1

[rp88.2]

Wondering if I missed something in the setup, etc.

DP11 is not scanning VSTs (VST2 or VST3) on a M1 mac w/macOS 12.5. Even though I have the primary plugin format set as VST2, it is not finding the plugins that are in /Library/Audio/Plug-Ins/VST or VST3

It has no issue finding the AU plug-ins, but seems not to be scanning the VST directories. Enabling AU plugins individually or in groups work.

For some reason it is not finding/scanning any of the VST plugins.

Yes, I have rebooted; removed the preferences and started over. Still not working. Rosetta 2 is installed for other software.

Any ideas?? Thanks!

rich

[rp88.2]

So... it is 'partially' resolved...

Here is what I have found out:

If I start DP 11 w/Rosetta, then it scans the particular VST and it shows up as one would expect.

If I start DP 11 without Rosetta, then it doesn't scan or find this particular VST.

DP 11 without Rosetta has no issue finding the AU version of the plugin.

Will be updating my TechLink

[mikehalloran]

You don’t say what VIs you are referring to. If they are not yet Native, DP will see them only if run over Rosetta 2.

[rp88.2]

In this particular case it is Wave Arts Tube Saturator Vintage. As you are aware, this is not a Universal binary or native silicon plugin, since it is several years old.

When I open/run DP11 (and Logic Pro X) as 'native' they both scan/see the AU version of it and load it in a project with no issue.

However, for whatever reason, DP11 ONLY scans/sees the VST versions if I run DP11 "Open using Rosetta".

That is what is bewildering.

[James Steele]

I'll have to find the email I got from a developer about this VST2 thing, but as I recall that this is pretty much a normal thing with VST2 plugs. Unless perhaps they are native, they can't be recognized unless you're running your DAW in Rosetta. I'm figuring VST2 is going to be phased out in favor of VST3... which might also mean that when Native Instruments updates Komplete Kontrol for Apple Silicon, they may have to move to VST3 instead of VST2 for the format it uses to load plugins.

[rp88.2]

James -- thanks! If you find that e-mail, I would really like to read it.

Yeah, it could be how the plugin was compiled, etc. I tried some other VSTs - Serum and SerumFx; no issue with DP11 in native mode finding them and using them.

If I need to use the Wave Arts plugins on Apple Silicon, I will probably use the AU version and screenshot the settings (if I need to transfer the project to Windows).

Thanks again!

[mhschmieder]

Interestingly, I found they weren't being scanned either, even after I deleted the cache, but after a reboot, they scanned.

When I deleted all caches, AU plug-ins were scanned, but not VST. Those didn't scan until after the computer reboot.

Hopefully that's all there is to it. Sounds similar to what you experienced.

FWIW, for the past 6 to 12 months, I have been experiencing similar issues with other audio applications and wrappers.

For instance, VE Pro doesn't seem to always scan VST's, when you have new ones, and RX Advanced is a mixed bag too.

So I'm wondering if it's something about the VST toolkits, as it seems to carry across multiple products.

[mikehalloran]

Interestingly, I found they weren't being scanned either, even after I deleted the cache, but after a reboot, they scanned.

Many VIs now require a complete shut down before reboot before they will scan into DP. Kontakt and Komplete updates are two of many—even though other NI updates scan right in.

[mhschmieder]

Interesting. That explains some of the quirks then, as Kontakt indeed waited until a reboot to scan, after its most recent update.

[James Steele]

I DID find the email I received from a developer who will remain anonymous. I don't want to cause him/her any problems or embarrassment if something he/she says here is incorrect. Any bolding for emphasis is mine. This was a response regarding an issue I wrote to them about with one of their VIs in DP:

Thanks for your message. I am sorry that you've encountered an issue. I was previously unaware of [issue redacted to preserve anonymity], but I can see that you're correct. It's an odd one! This is not the case in other DAWs running those AUs in Apple Silicon native mode, and it's clearly not the case for all other plugins in DP either. So it's a bit of a head scratcher!

VST2s only showing in Rosetta mode is expected, they can't bridge to the intel code like the AUs can, so most DAWs have chosen not to display them at all.

Ultimately yes, we're planning on bringing big new revisions to both of these instruments relatively soon with VST3 and native Apple Silicon support. I'm sorry to not bring you an immediate fix. I'll look into this DP issue in more detail and hopefully get back to you if I find a way around it.

Anyway... glean from that what you will. But it seems to say that often times VSTs will not appear in some DAWs or hosting apps unless they are running in Rosetta.

[rp88.2]

@James -- thank you! That explanation makes complete sense and explains the inconsistency between certain AUs being visible and VSTs not, etc.

Thank you again!

[mhschmieder]

Holy cow, that explains a lot! Thanks for posting! Some apps don't distinguish between VST2 and VST3, so that adds to the confusion, but DP fortunately keeps them segregated. This is also helpful with troubleshooting, when quarantining one or the other.

[gjensse]

I´ve been struggling with the same problem all day. The VST plugins are not showing up in DP 11 on my MacMini M1. They do show up on my MacBook Air M1 though, also running DP 11. Finally I deleted DP, including the preferences folder "com.motu.DigitalPerformer". I was hoping that DP would rescan my plugins after reinstalling, but it did not. It still has the same settings as before, like the preference file was not deleted...
Running DP in Rosetta didn´t help either.

[CharlzS]

I´ve been struggling with the same problem all day. The VST plugins are not showing up in DP 11 on my MacMini M1. They do show up on my MacBook Air M1 though, also running DP 11. Finally I deleted DP, including the preferences folder "com.motu.DigitalPerformer". I was hoping that DP would rescan my plugins after reinstalling, but it did not. It still has the same settings as before, like the preference file was not deleted...
Running DP in Rosetta didn´t help either.

The plugin caches are in /Library/Prefernces/com.motu.MotuAudioSystem. If you remove those files, it will rescan all plugs. If you remove the file /Library/Preferences/com.motu.DgitalPerformer/MOTU Audio System Prefs, it will reset your preferred plugin format.

[pencilina]

I've had the same issues. Try:

Open plugin settings
Select VST as primary plugin format Quit and restart DP
Open plugin prefs select all unchecked VSTs and hit re-examine (hopefully they're in the list, if not maybe quit and restart DP again).
Try this a couple/few times.

Good luck. You're not alone! Plug in handling is a ridiculous flaw in DP. We shouldn't be having to deal with this buggy bulls*&%t

Also consider switching whatever plug ins possible to AUs which tend to be more stable.