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

Hi JG16papa,

Please make sure to allow all your music applications to control SYNSOPOS when prompted. (SYNSOPOS is an essential part of the eLicenser Control Center).

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

Does this resolve your problem?

Best, Marnix

Hi all,

The Reason Rack Plug-in only installs as VST3, whereas Vienna Ensemble Pro can only host VST2 plug-ins at this point.

The Reason Rack AU plug-in (on Macs obviously) is recognised by VE Pro, but only opens a blank window instead of its GUI and is therefore not operational in VE Pro 7 either.

I have already notified Reason Studio about this!

@gsrokmix: I could not find a message from you in this matter - I just found one support request from 2017 in our archives, which was in fact replied to within 24 hours.

Best, Marnix

Hi,

I must confirm that all our player plug-ins by default run in real time in DP to ensure proper operation and cannot be forced into Pre Gen mode.

Best, Marnix

Hi Matt,

Sure - all our software comes with Uninstallers, please find them in the respective application folders.

Best, Marnix

Hi D´Penguin,

Unfortunately, I must confirm that LUNA is currently not compatible with our products.

LUNA would need so-called security entitlements in its code signature to enable our plug-ins to communicate with the eLicenser Control Center. The necessary entitlements, however, were obviously not included.

We have already notified UA with detailed instructions on how to fix this and hope that our colleagues there will update LUNA as soon as possible.

I am sorry that I cannot offer an immediate solution to this problem at this point.

Best, Marnix

Hi deepunair,

I am sorry to say that I have no experience yet with the LUNA system myself.

But generally, please make sure to allow the LUNA recording system (and all your other music applications!) 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)

In case LUNA does not figure in this list: I am afraid there is no way to manually add an application to the Automation tab - it is a matter of assigning Apple Event entitlements to the applications code, so this is something the UA developers will have to look into!

Here is what it should look like for an app that has assigned entitlements, in case you want to send this to UA:

<plist version="1.0">
<dict>
    <key>com.apple.security.automation.apple-events</key>
    <true/>
    <key>com.apple.security.cs.allow-jit</key>
    <true/>
    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
    <true/>
    <key>com.apple.security.cs.disable-library-validation</key>
    <true/>
    <key>com.apple.security.device.audio-input</key>
    <true/>
</dict>
</plist>

Best, Marnix

Hie Dewdman42,

Please confirm that you have updated Maschine and Komplete to their very last versions.

Then, please make sure to grant Maschine and Komplete Kontrol Full Disc Access and to allow all your music applications (incl. Maschine, Komplete Kontrol...etc...) to control SYNSOPOS. (SYNSOPOS is an essential part of eLicenser, our copy protection).

You can adjust these settings in the System Preferences - please see screenshots.

Does that resolve the problem?

Best, Marnix

Hi Dewdman42,

Try as I might, I cannot reproduce this on any of my systems - has anybody else ever stumbled over such a problem?

Best, Marnix

Hi sharonsmithmusic,

Can it be that you are trying to load a VE Pro Server project into VE Pro standalone or the free Vienna Ensemble? 

Best, Marnix

Hi fypy,

We are unable to reproduce this here, which makes it hard to find the reason for this error message...

Are you using the MAS version of the plug-in?

Best, Marnix

Hi,

I must confirm that I was able to sort of reproduce this, although the white windows (just one or two in various sizes) only sometimes pop up (randomly, let´s say every third or fourth time) when I attempt to hide VE Pro Server, which indeed does not work properly in OSX 10.11.6, as the windows only go out of focus into the background, but the application is not correctly hidden.

We will have to further investigate this.

Best, Marnix

Hi Bruno,

Do these drop outs only happen with Kontakt 6 or also with other plug-ins?

Best, Marnix

Hi Nordlicht2001,

Please make sure that you have disabled ASIO Guard specifically for Synchron Player in Cubase 10. You can do this by going to:

[Menu] > Studio > Plug-in Manager > VST Instruments > Synchron Player > Click "i" for Plug-in information > Click to set ASIO Guard to Disabled. 

Does that make a difference?

Please note that it is not enough to generally deactivate ASIO Guard in Studio Setup - this actually does not prevent ASIO Guard to still be active for the individual plug-ins!

Best, Marnix

Hi all,

We were able to reproduce the problem with the missing/vanishing IR´s in Cubase with the VST2 version of the Synchron Player plug-in (VST3 seems to be fine though) and the issue is currently being investigated - thanks for your (ongoing) patience!

Best, Marnix

Hi antcarrier and all,

This actually looks like a streaming issue to me - have you tried to raise the Preload Size for the affected instruments in Directory Manager?

Best, Marnix

Hi all,

We still cannot reproduce the problems with exporting mixdowns in Cubase here, but our developers are currently investigating what could possibly cause projects, which have been created in some VE Pro 6 builds, to take so much longer to load in VE Pro 7.

Thank you all for your patience!

Best, Marnix

Hi Shaiket,

It is crucial to check "Make this your default configuration" after setting up the Kontakt outputs , then save your project and restart VE Pro - does that make a difference?

Best, Marnix

Hi,

I could reproduce this with VE Pro 6.0.17011 (which is the version build you mentioned in your support request email!), but not with the latest Vienna Ensemble Pro 6.0.17966 from https://www.vsl.co.at/en/MyVSL/software_installers 

Best, Marnix