I mean really, look at this. All these huge spikes even while everything is completely at rest. I even did a MIDI reset before this.
https://imgur.com/a/ibC9nb4

See video:
https://youtu.be/8wn52IZ_dB0

Oftentimes, even when there's no MIDI activity or anything happening within my DAW (Mainstage), VI Pro 2 and Synchron instances will experience huge spikes, as seen in video. 

What is causing this and how can I prevent it? I've had a number of embarrassing crashes during live shows and I think this is a huge reason for it. I'm very depressed because I just got a big NYC break and feel like I'm blowing it because of this.

----

Details:

Computer: Macbook Pro 2021, Apple M1 Max chip, 64 gig ram, MacOS 12.5.1

And here's the CPU spikes in action. Again, yikes. 
https://youtu.be/i_qJayU20bs

I've had embarrassing crashes lately during live performances and I think Vienna Synchron is the issue, which I am using inside MainStage. Very frustrating.

Look at this stratospheric CPU spike. Just wild.
https://imgur.com/a/4clwQCP

Originally Posted by: Paul

Originally Posted by: J.H.

So unless I'm missing something, Vienna Instruments is no longer useable once you make the transition to iLok. Can anyone else confirm? I don't remember reading anything from VSL about them not making VI compatible with iLok, but it's listed as such in "MyProducts."

Screenshot: https://imgur.com/a/Y1G8RjI

You're totally missing something!
Your eLicenser protected products will keep on working just like before. 
You just cannot run both eLicenser versions and iLok version side be side on the same computer. 

VI is not compatible with iLok because we added a free update to VI Pro for all VI users with iLok. 

Dig in to the extensive documentation to find out more!

Best, 
Paul

If VI Pro is compatible with iLok, then how come it's marked as "not convertible to iLok" on the MyProducts page? (as seen in the screenshot)

So unless I'm missing something, Vienna Instruments is no longer useable once you make the transition to iLok. Can anyone else confirm? I don't remember reading anything from VSL about them not making VI compatible with iLok, but it's listed as such in "MyProducts."

Screenshot: https://imgur.com/a/Y1G8RjI

This thread was started 15 months ago. Is there any estimate yet on when VI / VE Pro will be able to run natively on Apple Silicon?

Native Instruments and others have already made the transition, so right now VSL is the only thing in my setup that's still Intel-only. 

Maybe this isn't your issue, but when I started using VSL instruments, I didn't realize that many (all?) of the "legato" patches will not sustain for long. (You have to use a sustain or legato-sustain for that). So I was puzzled as to why my sustained notes were dropping suddenly. 

Just adding my voice to the chorus of how urgently native Silicon support is needed.

I am running on an M1 Max computer now and over the weekend at a live performance, VI Pro instances caused MainStage to crash. So I went completely silent onstage while the actors had to improvise around it (I work in theater). Oof. 

So now I'm scrambling to find a new (old) computer, or start migrating away from VSL instruments so I can have a stable environment during live shows. 

Well the VI Pro plugin is working now... and I have no idea why. I didn't tamper with it any further after leaving my last post. But it's a little scary because I don't know what caused it in the first place. And I can't afford to have something like that pop up out of nowhere again before/during a live show.

The VI Standalone app still is crashing every time I try to open it though. But far far far less concerned about that.

EDIT: Nevermind. It's all crashing for me again just as it was before. Anyone ever encounter a similar issue? What should I try next?

EDIT 2: Alright I figured out the problem, and I'm a little embarrassed. Turns out the eLicenser key was not plugged in properly. Man, I hate dongles...

Once I plugged it in all the way, things were loading again ok. Still, kinda weird, because in the past I'd get a warning message when it wasn't plugged in. It wouldn't completely crash Logic/MainStage like this.

And again, the standalone VI app still crashes immediately upon trying to load. Oh well.

Howdy all,

Today I was working in MainStage for awhile, where I use instances of the Vienna Instruments Pro plugin. I don't know what triggered it, but at some point, MainStage would crash completely whenever I tried to open the VI plugin on one of my channel strips. Same thing would happen if I tried inserting the VI plugin on a channel strip-- the application crashes immediately.

Again, not sure what triggered this because I wasn't really tinkering in the VI plugin itself. Just at some point it failed to respond to any MIDI input and would crash when I tried to open it / insert it.

Even though I wasn't working in Logic, when I then tested the plugin there, I got the same results.

The standalone VI Pro applicatoin also crashes immediately for me upon trying to open it, but frankly it's been that way for a month or so now. But the plugin just started crashing for me today. 

Anyone able to point me in a helpful direction?

---------
Here's what I've tried so far, but the problem still persists:

• restart the application (Mainstage/Logic)
• restart my computer
• attempt to open the plugin in a new fresh project
• rescan the plugin inside Mainstage/Logic's Plug-In Manager
• install the latest version of Vienna Instruments Pro (from Nov 15)
• erase Vienna Instruments Pro and re-install

I am running MacOS Big Sur 11.6.1. Macbook Pro 2017. 

The complete problem report from the crash can be read here.

I will add that while the VI Pro plugin is now working for me in MainStage, the standalone VI Pro application crashes upon loading. I have not investigated this yet, as I don't really need the standalone app.

I am now on MacOS 11.6.1

After a week straight of working day and night, I finally was able to revert my MacOs and data to where I needed it to be. Everything works again for me. Had literally 10 long calls with Apple Support and even had to drive out of state twice to a service center.  (We kept finding solutions that got us 80% of the way there, but then would encounter an issue that would force me to pursue a different route.) I had to take significant time off from my day job. Ooof. It's been a loooong week but I'm happy it's over and I can now perform my gig this weekend.

The funny thing is, I didn't really intentionally upgrade to Monterey in the first place (where this whole problem began). I was in the App Store and downloaded MacOS Catalina 10.15, but after it downloaded, Apple then prompted me to install Monterey (not 10.15). Which I wasn't 100% cognizant of at the time. My mistake, but it felt like Apple misdirected me there.

I encountered this same thing this past week while trying to fix all my versioning issues. When I got to the point of downloading Catalina 10.15 or Big Sur 11.0, my computer would afterwards prompt me to download Monterey. To ACTUALLY install Catalina or Big Sur, you had to take a kinda weird route.

All of this is to say is that I think a lot of people will be having this issue in VSL, because even if they know they shouldn't download the latest MacOS yet, the system itself seems to kinda push users towards it.

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.

I know that iLok Cloud wouldn't require the physical dongle, but that feels like trading a risk (losing/damaging the physical dongle) with a bigger one (potentially losing access at any given moment, due to internet behavior).

Especially for us that use VSL products while performing live, iLok Cloud is a non-starter.

For years I've been irked and bewildered that VSL requires the physical dongle. But I figured, well, that's they way they set it up at some point long ago... and it's simply never gonna be a big enough priority to go back and change it. Restructuring the licensing handling would take too much work. Oh well, too bad for us users.

But now VSL is taking the time to restructure the licensing handling... and they're still choosing to stick with the physical dongle. Oooof.

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.

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.

Software: Vienna Instruments Pro

During performances, I keep finding that the "Algo Dry/Wet" parameter has been set to "bypass" so I must accidentally be touching a button/slider on my MIDI keyboard that's doing that. Problem is, I don't know what's doing it. But I certainly don't want it to happen-- not fun having really dry sounding strings in the middle of a performance. 

1) What MIDI CC control sets "Algo Dry/Wet" to be bypassed?
2) How do I change it / unmap it entirely?

Here's a short video I just recorded of the issue in action: https://youtu.be/CWL8wfGTu6M

Just checked to see if this is happening in Logic as well. Yep-- same issue is happening in Logic.

HI all,
I have been using VI Pro 2 with Apple's MainStage for years. Just got my computer completey restored to factory setting and am now encountering an issue I don't believe I've ever come across before. When I change the settings in one instance of VI Pro, all other instances in the project are also changed.

Example: I assign CC2 (Breath) to "Expression" for my oboe. Now my harp also has CC2 mapped to "Expression" (obviously not something I want). And the same is true for all other instances.

Maybe I'm missing something simple. But again, I can't remember encountering this partciular issue before.

This is all very helpful info. I'm happy there's at least a workaround for now and that I was able to help point out a small issue.

Thanks for the great support. VSL products very much a part of my daily life so I'm very thankful that there's such an awesome support team & community around them. 

And to Dietz's question-- I am using MIR PRO within VE Pro.