Vienna Symphonic Library Forum
Forum Statistics

194,355 users have contributed to 42,916 threads and 257,956 posts.

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

  1. Home
  2. Announcements
  3. NEW in 2023: VST3 Plug-in Support in VE Pro 7
  • GuinG
    GuinG

    Nice to see VEPro allowing VST3!

    Although I didn't have any crash so far with my Kontakt instances, I noticed that they seem to not be working once I reload a project file. The first time they work fine, it's only after reloading it that the issue starts - that said, it's not on every instance and/or instrument, which is really weird...

    Reapplied Kontakt VST2 version again, and they're back to normal.

    Windows 11 Pro, Cubase 12 Pro and AMD Ryzen 3700x with 64Gb RAM.

    I also noticed that EW Play engine is not recognized as a VST3.

    Now with effects, I haven't noticed any issue beside some plugins being hard to recognize the first time.

     

    In any case, it's a nice welcome to VEPro! Hope you can sort things out with time :)
  • PaulP
    VSL Team
    PaulP

    Hi Giun, 

    Thanks for your feedback!

    Can you please send us detailed instructions on how to reproduce this, including the sample libraries you load: support@vsl.co.at

    What does "seem to not be working" mean?

    Also, which plug-ins were hard to recognize?

    The more details and examples you can provide, the faster we can fix them!

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • L
    L

    I have these failures during scan and validation:

    Failed validation: (VST3) Bohemian Violin

     

    Failed validation: (VST3) iZotope BreakTweaker

     

    Failed validation: (VST3) SpectraLayers

     

    Failed validation: (VST3) ZebraHZ

     

     

    4 plug-ins failed validation and have been disabled.
    Disabled plug-ins can be rescanned in Preferences.
  • L
    L
    last edited
    last edited

    @Lofe said:

    I have these failures during scan and validation:

    Failed validation: (VST3) Bohemian Violin

     

    Failed validation: (VST3) iZotope BreakTweaker

     

    Failed validation: (VST3) SpectraLayers

     

    Failed validation: (VST3) ZebraHZ

     

     

    4 plug-ins failed validation and have been disabled.
    Disabled plug-ins can be rescanned in Preferences.

    After I manually rescan, only (VST3) iZotope BreakTweaker not seems validate.
  • PaulP
    VSL Team
    PaulP

    Hi Lofe,

    Thanks for reporting!

    So it's only izotope BreakTweaker that stays disabled after a manual scan. 

    Now the standard question: Which OS are you working on?

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • GuinG
    GuinG
    last edited
    last edited

    @Paul said:

    Hi Giun, 

    Thanks for your feedback!

    Can you please send us detailed instructions on how to reproduce this, including the sample libraries you load: support@vsl.co.at

    What does "seem to not be working" mean?

    Also, which plug-ins were hard to recognize?

    The more details and examples you can provide, the faster we can fix them!

    Best, 
    Paul

    My results are a bit random with Kontakt.

    When switching to VST3 version, I just load some multi instruments banks already preset from previous version.

    During the second time I load the template file, I noticed some libraries not having any audio ar all, although I can notice that Kontakt shows that they're loaded. At the same time, A couple of other libraries seem to work fine. This is not a random event, because it's always the same result: for example, on a Kontakt instance with 7 instruments, it handles audio only 8dio's Century solo french horn (stereo output 7, 8 and 9), and does not show any audio movement with any of the others.

    The EW Play engine is not even listed as an option on VEPro mixer. On preferences, it shows that it was recognized though.

    So far, the plugin that seems to be hard to recognize is Youlean Loudness Meter 2. When doing the Reset and Rescan All, the progress window stays on it indefinitely. A manual rescan of the plugin seems to fix it.
  • GuinG
    GuinG

    Didn't know how attaching files to the post would work, so I didn't add all info on the last post. Perhaps it's better to add them according to the results.

    The following instances are the ones that don't work the second time after converting Kontakt to VST

    Image

    Image

    Image

    Image

    Image
  • GuinG
    GuinG

    This one has quite a strange behaviour though.

    The first three instances (Gran Cassa) seems to work fine, but the other 6 don't show any audio activitiy at all.

    They're from the same library: Impact Soundworks Rhapsody Orchestral Percussion.

    That said, except the Gran Cassa, the other instruments are mostly placeholders until I get the proper VSL counterpart.

    Image
  • GuinG
    GuinG

    Finally, this instance works absolutely fine on VST3 Kontakt. It's from Impact Soundworks Bravura.

    Hope this info helps understand what sort of issues are currently showing up. I haven't tried yet to build all Kontakt instances from scratch, so I can't tell if it would bring the same problems.

    Image
  • S
    S

    Just updated to 7.2.1481.  Thankful for VST3 support.

    However, my DAW won't connect to it. I run Nuendo 12 on Mac (Big Sur 11.6.6).  

    Did a setting get flipped in the process??
  • H
    H

    There is for sure a problem with LAn today all my sever (3) disapear.... I cannot conect VEP plugin (empty window connect on plugin) and oblige to restart all sever......
  • M
    M

    This connection issue to VEP Servers started happening to me as well after updating all my computers to the latest 7.2.1481 version. Server instances window looks empty, if I restart the VEP Server while the plugin is open, it shows up. Big hassle to re-load a huge template just so it can show up again. It always worked with no problems until this very new 7.2.1481.
  • PaulP
    VSL Team
    PaulP
    Hi, Thanks for all your input! We‘re already looking into it! Best, Paul
    Paul Kopf Product Manager VSL
  • L
    L
    last edited
    last edited

    @Paul said:

    Hi Lofe, Thanks for reporting! So it's only izotope BreakTweaker that stays disabled after a manual scan. Now the standard question: Which OS are you working on? Best,Paul
    This was on Windows 10 64 bit.
  • A
    A

    Hi,

    really nice work!

    Here my fault plugins:

    - Ampeg SVT Suite 

    -arturia Comp FET -76 & VCA-65, Pre 1973 (all others Arturia plugins work ok)

    -Nugen MasterCheck

    -U-he Filterscape

    -Izotope Iris 2

    -BB Tubes, the last plugin from Waves, simply do not appear in the list (i've tried vst2 and vst3)
    It was the same with VEP6. On others vst host on the same machine it is detected.

    -Kontakt 7 has black GUI.

     

    I'm on windows 10 64bit(last update as today), nvidia quadro 400, motherboard DX79TO, core i7-3960X extreme edition, 32GB DDR3.
    All drivers updated.

    Maybe the nvidia quadro 400 is too old? (anyway Kontakt 7 is ok on others VST host on the same machine).

    Thanks a lot,

    best regards,

    Samuele
  • N
    N
    last edited
    last edited

    @Guin said:

    Although I didn't have any crash so far with my Kontakt instances, I noticed that they seem to not be working once I reload a project file. The first time they work fine, it's only after reloading it that the issue starts - that said, it's not on every instance and/or instrument, which is really weird...

    Same here on EW Opus. Also happens when disable/enabling. Sometimes Opus makes a project crash on re-loading. (VST2 version working normally).

    I'm reading reports that VE Pro is sending out blanket zero values on all CCs on a reload / enable of a VST3. That would likely explain a lot of the problems.
  • PaulP
    VSL Team
    PaulP

    Hi noiseboyuk, 

    Just checking: Are you really still on Windows 7?

    Best, 
    Paul

    Paul Kopf Product Manager VSL
  • N
    N

    Ha, no I'm not! need to update that sig now... Win 10, VEP 7, Cubase 12.
  • C
    C

    Hi Paul, congratulations on the new update. Sadly for me, now that I've updated Logic Pro X doesn't load. It gets stuck half way through going it's loading program. I was able to bypass this on my original machine (Mac Pro 2013) by 'rolling back' to an earlier version of VEP7 but I'm currently working on an alternative machine (also a MacPro 2013) and the option to do this is missing from the page on Vienna Assistant. 

    So to give you context. I launch VEP7 which loads fine. Then I launch Logic X and it gets stuck midway through loading and won't budge. Are you able to send me a link to download the previous version of VEP7 please?

    Many thanks in advance

    Chris

    MacPro Late 2013

    OS 10.14.6

    64GB Memory

     

    VEP7

    Logic X
  • I
    I

    I am facing VEP crashes with Kontakt 7 while disabling/enabling instances. Without disabling/enabling, no crashes. (VST2 version of Kontakt 6 working normally).

    I have tried Audiobro, 8dio, and Zero-G libraries so far. 

    Note: Only VEP crashes. Nuendo does not crash. All of the software has the latest updates.