@Paul said:

Hi everybody, 

We're looking at this right now. Stay tuned.

Always tricky with a brandnew OS - We suggest to install on a separate partition, to be safe with all components, and then maybe wait for the .1 version. 

Best, 
Paul

Thank you Paul,

yes I know (that's why I have a sandbox mac mini 😊 ), and I'm looking forward to VSL usually great software management. 

best regards. FV

Hi everybody, 

So we have to confirm that the plug-in GUIs of all our software are broken under Monterey. We're working on a fix and will let you know asap when the new versions are available. 

Best, 
Paul

Hi all,

The same with Cubase 11 on Intel based Macs. Good luck with the fix

Best regards Stan

@Paul said:

Hi everybody, 

So we have to confirm that the plug-in GUIs of all our software are broken under Monterey. We're working on a fix and will let you know asap when the new versions are available. 

Best, 
Paul

Wow, glad I saw this I was just about to update to Monterey because all my other important stuff is reportedly fine, but if it messes up VE Pro 7, then I must wait until I get the all clear from you guys.

I'm also having the same issue on an apple silicon MacBook in Monterey and in addition I get a system overload error when playing back my project for the first time. It looks like as it tries to load multiple instances of the Synchron Player (in Logic Pro 10.7 when playing back the track for the first time it gets overloaded. After the initial error it seems to run fine and subsequent playbacks have no further issues.

EDIT: Regarding the system overload issue, in Preferences>Audio, changing the Process Buffer Range from medium to large fixed the problem in Logic, thanks to vsl support for the suggestions, leaving it here in case anyone else has the problem

All of the VSL plugins were working fine in Logic X under Monterey Beta. For now, if I need to use VSL plugins without VEP 7 in Logic, I'll boot to my Big Sur SSD until there's a fix.

Update: The VEP plugin in my template actually still works/connects to my VEP7 template. It's just the Cocoa GUI that's broken.

FWIW, all of the same plugins and their AAX GUI work fine in Pro Tools 2021.10.0 in Monterey 12.0.1. (iMac19,1)

Edit: from other users' posts, it seems I was incorrect here. It seems that the MacOs 12.0.1 was responsible for the issue, not the latest VI Pro version.

I feel so stupid. Vienna Instruments Pro was working fine for me on Montery. (Both standalone and plugin version in Mainstage).

Then I updated Vienna Instruments to the latest version and now I'm having the same problem described here. Plugin screen is black and the standalone application immediately crashes when I try to open it.

I do not remember what version of Vienna Instruments I was on prior to updating. I believe it was 2.4 something.

But when I installed the latest version (2.5.18650), everything failed.

Same issue here with VI. What I've noticed is that it was working fine yesterday, before I updated to macOS 12.0.1. 

Super mysterious, but probably some fairly minor tweak. I have noticed that the plugin asked for some kind of permission, which it didn't before, so I'm going to try disabling SIP, just in case it's just some weird security thing (highly unlikely, but might as well give it a shot).

UPDATE: No difference with SIP disabled, sadly. Wish I hadn't updated to 12.0.1 now... 

Edit: as I edited in my previous post, it doesn't seem that this is just because of the latest VI Instruments Pro.

Is there a way to install a previous version of Vienna Instruments Pro? As I said in my above post, the issue started when I downloaded the latest version.

Yeah, that's interesting. I just find that a bit mysterious because this is a fresh install on this (new) machine, so I'm not sure how I would have had an earlier version of the installer... ?? I downloaded it from here within the last couple of days for sure.. Unless it was literally just released.

Just out of curiosity I updated to the latest macOS 12.1 beta, but no difference—UI still black. Sad times...

UPDATE: Actually, the latest VI 2 installer was from back in the summer, so it can't be a VI update that broke it, in my case. I really think it was the update from 12.0 to 12.0.1 that did it. I might be able to revert relatively painlessly in recovery mode, so I may give that a shot as an interim solution while VSL works out an official fix.

Paul,

Is there any estimate on when VSL will have a fix for this?

So far my attempts to roll back my MacOS have been unsuccessful, but I will keep trying. Just trying to get a solution worked out before I'm doing some live shows this upcoming weekend, which I depend on VI Pro for.

Hi, 

I hope we can present working versions this week, but I'm afraid I can't make any promises. 

I will keep you up to date in this thread!

Best, 
Paul

Give the guy a beta test for the gig!

@Paul said:

Hi, 

I hope we can present working versions this week, but I'm afraid I can't make any promises. 

I will keep you up to date in this thread!

Best, 
Paul

Just to note, the UI problem is the same on 12.1 beta 2.

So far, except for VSL plug-ins, all other VST plug-ins I often use are working normally in Monterey 12.0.1. I look forward to the update of VSL.

Ack! I was so excited until I realized it wasn't VI Pro 2.... Can the fix implemented here apply to VI and VE Pro?

The AU plugin from v1536 (beta) crashes with segfault and doesn't load in Logic Pro X for me -- The Logic Pro X host running under rosetta2 or natively. MacOS 12.0.1 (M1; arm64).

@JoelW said:

The AU plugin from v1536 (beta) crashes with segfault and doesn't load in Logic Pro X for me -- The Logic Pro X host running under rosetta2 or natively. MacOS 12.0.1 (M1; arm64).