Vienna Symphonic Library Forum
Forum Statistics

197,786 users have contributed to 43,083 threads and 258,670 posts.

In the past 24 hours, we have 4 new thread(s), 13 new post(s) and 57 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VE vst3 & Cubase crash

  • VE vst3 & Cubase crash

    S
    S

    I want to load VE within Cubase 64 bit now and every time Cubase crashes. It either scanns the VE file on startup and hangs forever, or it won't scan it... but VE shows up in the instrument list in Cubase, then I load it and the server interface loads but Cubase hangs forever. Is there any reason for this? Fix?

    -Sean
  • M
    M
    Same problem here... I have no problems starting new projects. But when I try to reload them everything hangs during loading instruments. Same problem with VE Pro 4 Build 9753. No problems at all until build 8861. I'd enjoy the new VE Pro 5, but I have to roll back for now.
  • D
    D
    last edited
    last edited

    @iscorefilm said:

    I want to load VE within Cubase 64 bit now and every time Cubase crashes. It either scanns the VE file on startup and hangs forever, or it won't scan it... but VE shows up in the instrument list in Cubase, then I load it and the server interface loads but Cubase hangs forever. Is there any reason for this? Fix?

    -Sean

     Do you mean VE or VE Pro?

    DG
  • S
    S

    This problem is in Vienna Ensemble, not pro.

    However, since the recent updates the 64 VE running as a plugin to the 32-bit Cubase has been crashing left and right. It didn't used to. I tried loading Cubase 64 and now I face this problem where it just crashes trying to even read the VST.

    -Sean
  • J
    J
    At my place things are even worse. Not only that Cubase 6 hanged on checking the VE(nsemble) and VI(nstrument) plugins. Now Cubase 6 does not start anymore. VI does not start anymore. The VI library installer does not start anymore. Even the e-license control center does not start anymore. Always the same thing: In the task manager the process with a very small amount of RAM used is shown, but no GUI, no application, no nothing. I deinstalled VI, VE and Cubase 6, reinstalled VE and VI. After a restart of the PC e-license control center starts, sometimes even shows my dongle. Close e-licenser control center, will not start once more. VI does nothing. Tried to reinstall Cubase 6. Does not work. Hangs at "activating MP3-trial license" and stays there until I kill it. Of course I will post this also in the Steinberg forum. This is really weird, working with earlier versions of Cubase and VSL products used to run without any problems. I am on Windows 7 64-bit, as you might have guessed. Anybody here can help?? Please. Jochen
  • civilization 3C
    civilization 3C

    as per the latter problem, cubase and I guess syncrosoft believe you have an mp3 codec you have not purchased, perhaps on the elicenser. So I would open elicenser and see if I could sort that. chances are you have a demo period and it has expired.

    coupling Cubase and VE Pro is not a great way to work. decoupling gets rid of slow loading times and slow saves, and I have seen no particular advantage reported for leaving the two hosts coupled.

    the other thing I wonder is, is the IP connection fixed or dynamic?
  • J
    J
    Hi Sean, when I posted my message on Sunday I was in great despair. But one little action solved all my problems. I put the dongle back in the USB slot where it was during the first installation of Cubase. Meanwhile I had changed the slot for easier access. Very bad idea. If you have made the same mistake: Put the dongle back where it belongs. Good luck Jochen
  • S
    S

    Thanks, I actually just reinstalled Windows and now Cubase anyway, but I'll pay attention to where I've placed the dongle to see if there are any similar behaviors.

    Another thing I forgot about. I was using Comodo firewall before. I've found that it does NOT get along with VE at all. Disabling the firewall does little... when I stopped the process entirely, VE ran much smoother. I am going to use a different firewall now to see if I face similar results. But I do remember that I experienced problems there before.

    -Sean