Hi David,

Try this:
1. Don't start VEP server at boot
2. Start Cubase but do not load a project
3. Start VEP server
4. Load Cubase project

It seems that VEP locks the eLicenser at times, I've encountered this too many times with Arturia's plugins too. However, Cubase is probably only verified at the startup, so if you can prevent VEP from being active when starting your DAW, you should be fine.

Thankfully I have moved to a master-slave system myself now, which spares me this issue (VEP runs on separate machine from the DAW).

Let me know how it works!

Regards,
CH

I've had this exact issue on two separate builds; using Win7 x64 and Win8.1 Pro x64. Only when I recently moved over from Ableton to Cubase and the latter did not start up (since it needs eLicenser) did I realize that VEP Pro is the culpit. In my previous build, Ableton would fail to open any plugins requiring eLicenser. In my current build with Cubase, Cubase simply won't load and shows the error message as reported in above posts.

All in all, over the last year, I have spent more time updating eLicenser, rebooting the computer (according to the error message), changing USB ports for the key, than what I have spent in VEP Pro and Vienna Instruments Pro!

Since VEP is the only program that seems to cause this issue, I would not be so quick to blame Steinberg, Paul.

Thanks a lot for the proposed fix, Stiltzkinz! Attempted this last night, but Win8 gave me some issues with "SeLicenser.sel" being object protected. Will try to find a way around that though. Maybe I will be able to finally use VEP Pro after a year and a half of crashes :)

Regards,

Christoffer

Ok, so the exact above issues have been consistent in ALL my versions of VI PRO, VI SUITE. They have been crasing 100% of my projects in Ableton, no matter which Ableton version, which USB port, which Win7 system, which eLicenser control center version...

However, I have managed to survive this, since the VEP server has been able to launch these successfully most of the time. Only when I have been daring enough to add any VSL plugin to Ableton has everything crashed.

Honestly, I have given this up and don't expect it to ever work. For one, it means that I will probably never purchase any Vienna product again.

Though this is probably a pure eLicenser issue, any alternative copy protection (iLOK) would have been fantastic. There really is little point in using any of the VSL products as long as they might stop working at any point in time. As mentioned above, rebooting the computer for hours and hours because one really wanted to add a VSL plugin to my project, it's not worth it.

Christoffer

True, and the answer is that my latency is usually 64-128 in the host, and 0 for VEP/MIRx. What I failed to see is that it seems VI PRO disables MIRx reverb when latency is too low. If that is the case (and I'm not sure it is) a warning would be nice :)

Thanks Paul! Will try it out, but possibly not now since I got it working, and I'm too paranoid to change anything ;)

Here is what I found: During the replacing of the various instruments, one of them actually would not get MIRx reverb whatever I did. However, by chance the MIRx-specific delay compensation got changed, and suddenly things started working.

Since I'm working in a near-zero delay environment, I suspected this might be the issue and it probably was. I will have to revert back to manuals or self-testing later on to see what the MIRx delay compensation actually does, but I suspect VI PRO disables MIRx reverb when system resources get low. Correct?

Regards, CH

Hi,

MIRx seems to have dropped out on some of my instruments, although there is nothing to indicate why. I have 2x VEP instances running (Live9->VEP server->VEP), one for Strings and one for Brass. With MIRx activated, both instances and everything is synchronized, no problems. However, in my current project, some instruments (notably solo for VI, VA, VC in Strings VEP, and all Brass instruments in Brass VEP) do not get any reverb whatsoever. Everything has been fine, but suddenly these have now dropped out in the current project.

Everything I can see in VI Pro indicates things are fine. MIRx activated along with Venue, Profile, Nat Volume, Pre-Eq, Synch, and Dry/Wet. If I change the dry/wet, nothing happens with the reverb. If I change the venue (which then synchronizes with all other VEP and VI instances), the reverb is still zero. If I change to Algo, then I get reverb. If I change back to MIRx, it disappears. I also tried Channel 15 (reverb on/off) without any effect.

I duplicated the involuntarily dry Trumpet section, to see if a new instance would be wet, but it was not. I saved the matrix, then imported it into a new VI Pro instance. Reverb worked. Then I saved the patch, imported it into a new VI Pro instance, reverb worked not. So there is probably something in the patch that is fundamentally anti-MIRx :)

Any ideas how to fix this? Is there a hidden setting somewhere that I'm missing? I've been through all the settings I can find, but I still have no clue what it is in the preset that disables the MIRx reverb.

Knowing how thing go, this will probably happen again sooner or later. And I'm not too keen on setting up 10+ new instruments when the reverb starts failing.

Interestingly, this probably happened all at once yesterday. One moment things were working, the next MIRx for 10+ instruments in two separate VEP channels got disabled.

Regards,
Chris

Hi,

Is the transport function also working now? I am currently on latest versions of Live (9.0.5) and VEPRO, and not able to get this to work for now. Not a major issue, but it does become tiresome during mixing when I have to flip back and forth between VEPRO and Live in order to playback.

Regards,
CH