Hi michkhol,

Your initial support request was actually related to Vienna Instruments Pro - the case was with our developers for investigation since then, but unfortunately they weren´t able to find the exact cause for this crash yet.

Now as far as Falcon is concerned, there seems indeed to be an incompatibility with VE Pro, especially when changing the output channels in Falcon - I am afraid there is not much we can do in this respect, please also contact UVI in this matter.

Generally, please send the Sentry Reports, which are generated when VE Pro crashes and which include your system ID, with a short description of what you did before the crash happened, as well as your email address, to us - our development team monitors these crash logs and we can only assign these reports to your cases, if we also have your address!

Best, Marnix

Hi, I must confirm this flaw in Synchron Pianos v1539 - this will be fixed with the next update!

Thanks for reporting and my apologies for the inconveniences!

Best, Marnix

Hi xsubs,

Vienna Ensemble Service should actually only launch when you have inserted a Vienna Ensemble plug-in in one of the tracks of your start-up project or if Logic has to scan/validate your plug-ins for some reason.

Could it be that you have multiple WaveShells in your AU and VST plug-ins folders?
If so, please move all of them out of the plug-in folders except the very newest one - does that make a difference?

Best, Marnix

Hi Cyril,

The only explanation I can think of is that you have saved version 3 while the Presets were not loaded, for example because your USB-eLicenser was not properly recognized by the eLicenser Control Center at the time.

Best, Marnix

Hi Noah,

I am sorry to say that Logic does not support freezing of multi-output multi-instruments by design - only tracks holding the stereo version of the Vienna Ensemble plug-in can be frozen.

It is not necessary to freeze tracks before you bounce them though!

Best, Marnix

Hi benjohnson2001,

The GM patches are just a subset of samples that are also contained in other Vienna Jazz Drums patches.

Best, Marnix

Hi Ben,

Generally, it is not recommended to use a single sample if it is supposed to sound natural...

The Jazz Drums were in fact designed to be loaded into Vienna Ensemble with the provided Jazz Drums projects from https://www.vsl.co.at/en/MyVSL/MyDownloads/Tutorials_Templates as described in the Jazz Drums manual, which can be found at https://www.vsl.info/en/instruments/vienna-instruments/collections#percussion

The patches in the JD_Cymbals_Brushes Matrix are actually not tempo-synched, but rather controlled by the speed you are playing. The idea behind that is that a cymbal sounds differently if it has already been hit before, depending on how long ago the last hit was. The Vienna Instruments player analyses when the last hit has occurred (i.e. the speed at which you are playing) and plays back the appropriate patch accordingly.

I hope that helps.

Best, Marnix

Hi Goldstein,

I am afraid that merging channels is indeed not possible in an VE Pro instance.

The only thing you could do is to manually load your various Kontakt patches into one Kontakt multi-instrument and create outputs accordingly, then set the MIDI Input channel to All and create corresponding Aux Input channels in VE Pro.

Best, Marnix

Hi jdk90026,

I am not sure I understand your Buss/Aux routing - would you please send a simple(!) example PT project to so I can better look into this?

Best, Marnix

Hi J.Dnp,

I have just replied to your support request Case 402258 (from last Friday...)

It had indeed been caught by our spam filter - my apologies for the delay!

Best, Marnix

Hi,

It is crucial to check "Make this your default configuration" after setting up Kontakt outputs (please see screenshot), then save your project and restart VE Pro - this should resolve your problem!

Best, Marnix

Hi Zaffer,

I can see on the Steinberg License Transfer Server that you have actually NOT yet downloaded your license for RoomPack 6 to your USB-eLicenser - please do so by entering the corresponding activation code manually in the eLicenser Control Center!

You can select the download destination in the Download Manager.

But no matter where you have downloaded the RoomPack data to, you can select where to INSTALL the files to during the actual installation process!

Best, Marnix

Hi Taylor,

You may need to delete your AU cache file first, which will force Logic to re-scan for plug-ins the next time you launch it:

1. Quit Logic Pro X.

2. Click on your Desktop wallpaper to focus the Finder.

3. Click on Go in the menu bar, hold down the Option key on your keyboard, and choose Library from the Go menu.  This will take you to the User(!) Library folder

4. Once inside the User Library folder, go to the Caches folder and then the AudioUnitCache folder.

5. Drag this file to the trash: com.apple.audiounits.cache

6. Empty the trash.

7. Restart your computer.

8. Restart Logic X.

Does that help?

Best, Marnix

Hello xazqe,

On Macs, the Vienna Suite Audio Unit plug-ins are installed by default and cannot be deselected, this is why they are not specifically listed in the Installer.

Please check in /Library/Audio/Plug-Ins/Components/ - you should be able to find the Vienna Suite AU components there!

Generally, please make sure to allow all your music applications, especially Logic, to control SYNSOPOS when prompted. (SYNSOPOS is an essential part of eLicenser, our copy protection).

You can also adjust this setting later on in the Automation tab (System Preferences > Security & Privacy > Automation - please see screenshot)

If the Vienna Suite plug-ins are still not available in Logic, you may need to delete your AU cache file, which will force Logic to re-scan for plug-ins the next time you launch it:

1. Quit Logic Pro X.

2. Click on your Desktop wallpaper to focus the Finder.

3. Click on Go in the menu bar, hold down the Option key on your keyboard, and choose Library from the Go menu.  This will take you to the User(!) Library folder

4. Once inside the User Library folder, go to the Caches folder and then the AudioUnitCache folder.

5. Drag this file to the trash: com.apple.audiounits.cache

6. Empty the trash.

7. Restart your computer.

8. Restart Logic X.

Does that make a difference?

Best, Marnix

Hi Scott,

Thanks for the update - great to hear you were able to solve the problem!

Best, Marnix

Hi scottgius,

In Cubase, please make sure you have unchecked "Release Audio Driver when Application is in background" in "Devices" => "Device Setup" => "VST Audio System"

Does that solve the problem?

Best, Marnix

Hi tigerman,

The last released build of VE Pro 6, which could be installed on OSX 10.9, was 6.0.16068 - here is a direct link to it.

I remember vaguely that this version had issues in High Sierra though - if you experience problems on your 10.13 machine with it, please drop me a line at

Best, Marnix

Hi Lionberg,

Can it be that you have multiple WaveShells in your plug-in folders? If so, please remove all of them except the very newest one - does that make a difference?

Best, Marnix

Hi Ondine,

Please click on the double-arrow next to the virtual keyboard in Synchron Player to allow adjusting the keyboard range of the currently selected slot.

Screenshot attached.

Best, Marnix

Hi All,

May I ask you to contact us directly at in this matter and please always include your system specifications, as well as screenshots of the error messages you are prompted with!

Best, Marnix

Hi JamesH,

This problem is currently under investigation - thanks for your patience!

Best, Marnix

Hi sottovoceprods,

I loaded your Nuendo project into Cubase, since I do not have Nuendo installed here at home.

No difference in Latency whatsoever, no matter wether I route the Kontakt signal into Bus 1, Bus 2 or Bus 3 in the VE Pro Server instance.

I also asked two of my colleagues with different systems to see if they could possibly reproduce your problem and they were unable to do so either.

Please review your Audio Connections routing (F4)in Nuendo, especially in the Control Room tab - this is a constant source of various latency oddities, for example when you are using listening busses or duplicate assignments...etc...

Also, please check wether "Constrain Latency Compensation" is enabled in Nuendo - this also might be causing the problems you are experiencing when not properly configured.

As for Threads per instance setting: unfortunately, there is no "one setting to rule them all", as this depends on so many factors. Please find more information about multiprocessing in VE Pro 7 at https://www.vsl.info/en/manuals/vep7/vep-server?q=multiprocessing#multiprocessing

Best, Marnix

Hallo martin240,

Der Vollständigkeit halber poste ich nach unserer Support-Email-Kommunikation von heute auch hier noch die Lösung des Problems:

Ein vollständiger erneuter Scan sollte an sich nur erfolgen, wenn der Cache-Ordner gelöscht wurde (möglicherweise durch eine Drittanbieter-Utility, die System-Caches säubert?) oder wenn ein manueller Rescan aus den Einstellungen ausgelöst wird.

Der Plugin-Cache-Ordner für VEP7 lautet:

/ Benutzer / IHR BENUTZERNAME / Bibliothek / Caches / VSL / Vienna Ensemble Pro / Cache

Kann es sein, dass Sie vielleicht mehrere WaveShell Dateien in Ihren Plug-in Ordnern liegen haben?
Wenn dem so ist, verschieben Sie bitte alle WaveShells ausser der allerneuesten aus den Plug-in Ordnern heraus.

==> Das Problem war tatsächlich eine ältere WaveShell.

Cheers, Marnix

Hi Arlanda,

That´s fantastic - thanks for sharing!

Best, Marnix

Hi Arlanda,

You may need to delete your AU cache file, which will force Logic to re-scan for plug-ins the next time you launch it:

1. Quit Logic Pro X.

2. Click on your Desktop to focus the Finder.

3. Click on Go in the menu bar, hold down the Shift key on your keyboard, and choose Library from the Go menu.  This will take you to the User(!) Library folder

4. Once inside the User Library folder, go to the Caches folder and then the AudioUnitCache folder.

5. Drag this file to the trash: com.apple.audiounits.cache

6. Empty the trash.

7. Restart your computer.

8. Restart Logic X.

Does that resolve the problem?

Best, Marnix