Vienna Symphonic Library Forum
Forum Statistics

180,742 users have contributed to 42,140 threads and 254,362 posts.

In the past 24 hours, we have 3 new thread(s), 18 new post(s) and 49 new user(s).

  • VEP Cubase problem with VST3

    Hi everyone,

    I'm currently exploring VEP with a demo licence, but I can't get it to work in Cubase as a VST 3. When choosing something like Ensemble Pro x64 in the VST rack, the server interface automatically pops up, I can connect to the server bit, and everything's great. But when loading one of the VST3 versions, this window does not appear. Instead there's a small empty Cubase window of similar format, just showing the on/off, read and write buttons along the top, with nothing actually inside it. I get the impression the server interface should be appearing below that, any idea why it isn't? Could the .dll be in the wrong place or something?

    Kind of stuck without this, thanks for any help anyone can suggest.

    Pyre

  • check 'plug-in information' to see if Vienna Ensemble Pro.vst3 is shown. it could be you don't have it installed correctly.



  • Hi Civilization 3, thanks for the screenshot, I hadn't even realised the Plug-in Information window could stretch out that wide, I've only been seeing the first two columns.

    But it's right there, Vienna Ensemble Pro x64 vst3, looking very much the same as your screenshot, so that bit appears to be working correctly.

    Many thanks,

    Pyre

  • I observed this behavior on my machine, and account it on one of the two following reasons:

    1) Do you by any chance use any VST wrapping sofware? For example, I use Novation Automap, which processes the VSTs in a certain way. I had to re-install VEP and re-enable automapped plugins to get it to work.

    2) I read somewhere on the Internet that there's apparently a problem with 64/32 bit mix of the Cubase/VEP VST3 plugin pair. This suggests trying using different combinations of both.

    Being a bit too vague above, yes, so please let us know if you find a remedy.

  • Hi Crusoe,

    No VST wrapping software, as far I know. I'm just using Cubase and VEP. I can't actually see any 32-bit plugin versions of VEP, I'm wondering if they only show up in the 32-bit version of Cubase. The non-VST3 version of VEP is fine, but all the VE VST3s are showing the same problem on my system - the interface box is empty (the box opened by clicking on 'e' next to the relevant plugin on the VST rack).

    Many thanks,

    Pyre

  • Try opening the x64 version as standalone. Then see if that makes a difference with the plugin.


  • Standalone worked for me, but I second the advice. My guesssing didn't help, so here's the hard facts. Forgot to mention that I've been struggling with Cubase 7 (trial version 7.0.2 I think), both 32-bit and 64-bit versions behaved the same. Since I didn't have a problem in Studio One with exact same VEP installation, I'm inclined to think that this is your Cubase problem. But at the same time, I *think* I didn't have a problem with Cubase 5 (not 100% sure, can't remember). Another fact is that the plugin actually works even though its window does not suggest it. I had a working project, so when I experienced the problem for the first time, VEP actually loaded the project and everything sounded the way it should. So this again suggests Cubase problem, and more specifically the displaying problem.

    So what to do? Maybe you can try some software that permits one to force window resizing, and try to enlarge the VEP VST3 window using it. You can also try using Cubase 5, if that's an option of course.


  • I saw that once with Cubase 5.  I had done something different, forgetting something. I can't be 100% from memory, but the first thing I would suggest is so basic it might be insulting. but are you sure the VEP x64 server is open?

    I notice you are demoing it. In case you don't know, this is what it looks like.


  • Hi Civilization 3,

    Good thought, but the x64 server is definitely working, and I have managed to get it working with the non-vst3 version. For now I have a work-around using the event input, but it's a bit of a pain, if a solution could be found that'd be just lovely.

    Of course I've now found that having all the tracks going into one instance means they all need to be playing for VST freezing to work - and my computer can handle no more than instruments in MIR, not the current thirtysomething. So I might be moving back to separate instances, one for each section, so I can freeze those I'm not currently editing. Sigh.

    Thanks for all your help,

    Pyre

  • I just found the solution.

    It's because Always On Top is checked for vst3 version of VEP5.

    Right-click on the small panel, uncheck Always On Top, solved!

    Check on Always On Top if you want to.