Vienna Symphonic Library Forum
Forum Statistics

199,069 users have contributed to 43,152 threads and 258,887 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Cubase 9 Pro

  • Cubase 9 Pro

    S
    S

    I just thought I would share that I upgraded from 8.5 to 9.0 today, and eveything appears to be working just fine. None of my plugins or VSTs were blacklisted. Cubase 9 doesnt support 32bit plugs anymore, so keep that in mind if you upgrade. Steinberg forum showed a number of people running in to that issue.

    VEP Instances seems to load much fast when I opened an old 8.5 template project. However, I have moved to just running VEP6 on local host. 

    First impression of Cubase 9... I'm liking it. 
  • B
    B

    Not so fortunate here.

    On my initial opening of cubase 9 pro.  Seems to be hung on Initializing.  All VEP plugins blacklisted on the way to being hung.  Only have 64bit versions installed.

     

    Going to reboot and try again

    NoGo

    soft elicense problem discovered.. not sure but suspect its related to Vienna Ensemble Pro 6  reloaded eLicenser software, the soft eLicense is no longer blocked.

    installing ViennaEnsemblePro 6 update 
  • S
    S

    Sorry to hear that...

    This is a help link from Steinberg to address those issues with blacklisted plugs. 

    https://helpcenter.steinberg.de/hc/en-us/articles/207348390-Plug-in-Sentinel-for-Cubase-9
  • B
    B

    thanks I'll be heading to that link!
  • S
    S

    I also downloaded the latest version of elicenser before I started.
  • B
    B

    OK.. so  turns out only VST 2 versions of plug ins were blacklisted and the related VST2.4, 3.6 and/or 3.6.6 are showing up in VST Effects.

    The elicense soft license bit seems to have been the hang up.  Start up flew by and included Vienna.  

    Sorry for the scare.
  • B
    B

    Synetos said, "I also downloaded the latest version of elicenser before I started"

    Be advised oh future reader of this thread.

    I had the current version of eLicenser installed.  It took reinstalling the current version of eLicenser so that it would recognize the valid soft eLicense.