Vienna Symphonic Library Forum
Forum Statistics

196,053 users have contributed to 43,014 threads and 258,388 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Difference between the x32 and x64 VE PRO plugin (not the server)

  • Difference between the x32 and x64 VE PRO plugin (not the server)

    I
    I

    I started rebuilding my template by moving everything from FX Teleport to VE PRO. For this I had to use 32-bit Cubase 5 under Vista 64 as FX Teleport makes the Cubase BitBridge crash. Now that FX Teleport is gone I'm trying to move the template to 64-bit Cubase. Cubase 64 can see only the x64 versions of Vienna plugins at the moment.

    Question #1) When I load the template in Cubase 64 it says that it can't find Vienna Ensemble Pro (the x32 version). At the same time PLAY (which I will be moving to VE after they release the next update with official VE support) replaces the x32 version with x64 version automatically. Why doesn't this happen with VE PRO?

    Question #2) What's the difference between the 32-bit and 64-bit Vienna Ensemble Pro VST plugin? Will it affect the performance of the VE if I use the 32-bit plugin in Cubase 64 connecting to x64 VE Servers? In Cubase 32 I'm using the same x32 plugin to connect to both x32 and x64 versions of the VE Server so I assume that in Cubase 64 I should be using the x64 plugin to do the same?
  • I
    I

    Hmm. There's something fishy going on. I tried using the x32 plugin in Cubase 64. First Cubase couldn't see the x32 version before I removed the x64 version and even after that Cubase 64 says that Vienna Ensemble Pro is missing when I'm trying to load the template. Now I have the missing !!!Vienna Ensemble Pro!!! in one slot and Vienna Ensemble Pro (not x64) in the next. What's going on? I can continue using Cubase 32 right now but I need to get to the 64-bit version soon. I also don't want to corner myself by building my template further in case there's some issues that force me to rebuild it to go native 64.
  • D
    D
    1.  Have you started the 32bit server before running Cubase?
    2. 32bit loads 32bit plugs. 64bit loads 64bit plugs.
    3. VE Pro doesn't need the Steinberg VST Bridge

    DG
  • I
    I

    Thanks DG. As I said I'm not talking about the servers, I'm talking about the plugin, the small piece of software that interacts between Cubase and the VE Server. The simplified version of the question goes that should the x32 plugin be automatically substituted with the x64 plugin when opening a Cubase 32 project in Cubase 64? Because that didn't happen with VE but it happened with PLAY.
  • D
    D

    I don't understand your problem then. The 32bit/64bit is determined by the instances that you connect to in the respective servers. What is not happening that you expect to happen? The host will always load the correct connector.
  • D
    D

    Hang on a second. I think that you're mixing up 32bit/64bit with VST2 and VST3. The VST3 plug has /// next to it whereas the VST2 doesn't.

    DG
  • I
    I

    No, I meant !!!plugin!!! which is the way Cubase informs that the project includes a missing plugin.

    But anyway, the problem is that I made my template in Cubase 5 x32 and now I can't load it in Cubase 5 x64. Is that simple enough? [:D]