![]() It's nowhere near 70% more CPU efficient. Also, the same USB dongle is recognized by the latest version of eLicenser on my Windows 10 machine, and Cubase 8.5 can be used normally. ![]() I had no problem with the version of eLicenser Control immediately before the latest one. Why not install VE Pro 6 on both boot volumes? 70% less CPU usage & new features! Application ‘LCC2’ has caused the following error: Connection to production device lost. Vienna Ensemble Pro 5 - build 6 – released DEC 5 16 All Vienna Ensemble Pro 4 or Vienna Ensemble Pro 5 projects are fully compatible with Vienna Ensemble Pro 6.”ĮLicenser Control Center - Version 6. The software installation of Vienna Ensemble Pro 6 will overwrite Vienna Ensemble Pro 4 or Vienna Ensemble Pro 5. “Please note that you need a valid license for Vienna Ensemble Pro 4 or Vienna Ensemble Pro 5 on your ViennaKey to apply the Vienna Ensemble Pro 6 license upgrade. Why not install VE Pro 6 on both boot volumes? "70% less CPU usage & new features!" (You mentioned you’re OK in PT10 with VE Pro 5’s 64bit Server) You can use VE Pro 6’s 32bit Server for 32bit VST/VSTi in Pro Tools 10. Go down to the 'Windows Firewall' option and click the 'OFF'. Click the 'Start' button on the bottom of the screen. I have two boot volumes, one with PT 10/VEP 5 and one with PT 12.6/VEP 6.ĭoes each drive need its own eLicenser/Vienna Key? Choose 'Boot Into Safe Mode' from the menu that appears. I can load a new instance, but, as expected, the setup associated with the coupled instance is lost. If I do this, what appears in the Insert is labeled 'Vienna Ensemble Pro' and not 'VEPro', I get a AEA error -20007 (which I cannot find in any PT docs or by Googling), and there is no sign of the coupled VEP instance. I can click on the insert with the greyed out 'VEPro' label and select the instrument option for 'Vienna Ensemble Pro (stereo)' - so the VEP 6 plugin is, in fact installed and visible to PT. If I click OK to dismiss the error and let the session open anyway, I can see the greyed out plugin assignments, all of which reference 'VEPro". When I attempt to open the same session after booting from the second volume with PT 12.6 and VEP 6 and launching VEP 6 Server 64-bit, x, I get an error saying the Vienna Ensemble Pro plugin is not found. This session opens and plays correctly after launching VEPro Server 64-bit and using the PT10/VEP 5 combo in the volume where it was originally created. I have a PT session that is coupled to VEP 5. What is not your case, if you use Cubase. I have two boot volumes, one with PT 10/VEP 5 and one with PT 12.6/VEP 6. When using eLicenser protected products (plug-ins, VST Instruments) in 3rd party host applications. Here end-users are provided with the current and previous versions of the eLicenser Control (eLC) to ensure the reliability of eLicenser-protected software. I am upgrading from ProTools 10 to ProTools 12.6, and from Vienna Ensemble Pro 5 (VEP5) to VEP 6. eLicenser Control Center is a license-management and copy-protection technology used by many software companies. I posted on the VEP Forum and members suggested I post here, suspecting this is an RTAS 32 vs AAX issue. Note: This question involves Vienna Ensemble Pro and ProTools 12.
0 Comments
Leave a Reply. |