Vienna Symphonic Library Forum
Forum Statistics

186,187 users have contributed to 42,445 threads and 255,762 posts.

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

  • Timeframe or VST3-Plugin support

    As far as I recall it was somewhere mentioned that support for VST3 plugins would come to VEPRO.

    When will will this happen? 


  • I wonder that too. Disappointing that VSL refuses to fix this and clearly communicate about it.


  • Hi, 

    Thanks for the reminder. I know that VST3 is still not implemented, and it is still high on the list.

    I hope that we can provide this feature soon. Unfortunately I cannot offer an ETA, but I will give this another push. 

    Best,
    Paul


    Paul Kopf Product Manager VSL
  • Good to hear @Paul. Some vendors start to implement new features in VST3 only.

    As I'm a new VEP user I searched the description of VEP and found that VST3 is supported. I didn't get though it was meant for the VSL plugins in DAWs only atm.


  • Paul, just a reminder to see if the work is progressing. I've a VST3-only plugin that would like to use with VEPRO7 on my Mac, and would be very happy to see this happen.

    This plugin is supposed to support microtuning from Dorico and other VST3 plugins. Oh, how would it be wonderful if it could "stay in tune" with the VI and Synchron players…

    Paolo


  • In the meantime I think you can consider using bluecataudio patchworks inside vepro. Patchworks can host vst3 plug-ins. Plogue bidule can also. The only free solution I know of is image line mini modular which I think also can. Kushview Element might also buy I found it to be buggy and overly complicated. As long as you aren’t needing vst3 specific protocols to happen between your daw and the plugin, those solutions will work. Patchworks and plogue bidule are both handy tools to have. I have personally found plogue bidule to be more useful but unfortunately there have sometimes been stability issues with it inside vepro. Both of these solutions are using vst2 methods to communicate with vepro so if the daw needs to be able to send vst3 specific messages to the plugin for the micro tuning feature to work then it might not help you. I doubt that’s the case but just mentioning it. I’d try image lines free solution first then if that doesn’t work try the patchworks demo.

  • Is this only a VST 3 problem? I thought my VST plugs were working before in 6 on my trash can. Now some VSTs are failing scan. I found what seems to be a "track" Many of the "failed" AUs and VSTs were in a folder called "Unknown". By right clicking each plug in, I was able to successfully scan many of the failed VSTS and even some failed AUs. The VSTs that still failed are: Hand Clapper/Slate SSD5/CSR Hall/Kontakt 3/Melodyne/Ozone 3/PhilharmonikCE/Sample Tank2/Sonar Works/TH1/Trash/iZotope Alloy/RX3/. Please advise


  • last edited
    last edited

    @PaoloT said:

    This plugin is supposed to support microtuning from Dorico and other VST3 plugins. Oh, how would it be wonderful if it could "stay in tune" with the VI and Synchron players…

    Try this free subhoster (Kushview Element).  I just tested it inside VePro7 and using a VST3 plug inside that; nd it seems to work.  its free.

    https://kushview.net

    I have also tested BlueCatAudio Patchworks, which crashed the VST version but worked ok so far with AU version.  When it crashed, it caused Cubase to crash too!  That's bad, hope VSL is taking notes.  

    I also tested PlogueBidule, which causes VePro and Cubase to crash once, but worked once too.  Not sure what happened there.

    I also tested DDFM MetaPlugin, which also seemed to work.

    The last three products listed above, are not free.  Image-line MiniModular is the other free one, but it doesn't support VST3 hosting and hasn't been updated in like 5 years.

    I do not know why some of these plugins seem to crash VePro so badly, and even cause the DAW to crash along with them.

    VST3 in General

    It will be an improvement when VePro can host VST3.  Me personally I am avoiding using VST3 plugins as much as possible due to poorly designed midi implementaiton of VST3.  In almost all cases, the VST2 version of a given plugin will work better.  In fact I have removed all the VST3 versions of my plugins off the system to avoid them completely, with the exception of only one, Vienna Ensemble Pro.vst3.  The reason is because that supports 768 midi channels into VePro.  So that is definitely worth using on Cubase.  Also some Steinberg plugins came with Cubase are only in VST3 format, so I'm stuck using them.  Otherwise, its VST2 all the way for me.

    That being said, Steinberg has changed the licensing rules on their SDK for VST plugins.  New developers are now unable to legally distribute VST2 plugins unless they were grand-fathered into the old VST licensing with a signed agreement.  Older developers mostly have that license agreement and can continue to distribute VST2 plugins, but newer developers do not have a legal option to develop and distribute VST2, they must use VST3, even with the midi limitaitons that Steinberg imposed into the new SDK and is very stubborn on the issue as well I might add.  

    In any case, for that reason, in the future we may see more plugins come out that are VST3 only, due to the licensing changes.  Its a good idea for VePro to get with the times and support VST3 for that reason, but I also realize that VST3 hosting is a bit convoluted at this time due to some of the midi problems already mentioned.


  • last edited
    last edited

    @Dewdman42 said:

    Try this free subhoster

    Thank you for these hints. I admit that, however, in general, I prefer to work with stable and officially supported software. This is not for lack of will of experimenting, but for lack of time. I know it is time for me to compose, instead of configuring my software. We live in apocalyptic times, and I would like to focus on the essential things.

    The willingness of Steinberg to live in the closed garden of their VST is being a problems for many users. I'm not using PCs, so I could ignore it, wasn't it for Dorico. Can I replace Dorico with another notation program? Not really, since it is finally a notation program that is thinking in a way similar to mine.

    At the moment, for the first time after a long search, I have all the software I want – notably, Logic, Dorico, VSL, Spitfire, conTimbre, Xsample, Ircam, other specialized sounds libraries. I don't need much other. If only they could communicate between them…

    Paolo


  • another advantage of these sub hosters is they can host AU's inside Cubase and Dorico.

    Anyway I hear you....


  • last edited
    last edited

    @Paul said:

    Thanks for the reminder. I know that VST3 is still not implemented, and it is still high on the list.

    I hope that we can provide this feature soon. Unfortunately I cannot offer an ETA, but I will give this another push.

    April 1rst 2021 now and still no VST3 support. I hope this is an April fools joke.

    If not, I wonder what "high on the list", "provide this feature soon", "give another push" means for VSL. 🙄

    regards, Robert


  • Hi, 

    I'm also not happy about the missing VST3 plug-ins in VE Pro.  My apologies that this hasn't been added yet. 

    There's always something else getting in the way for our development team, I'm afraid. Sorry to have no better news.

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Just bought VE Pro, also looking forward to VST3 support. 


  • Hello, do you have an ETA on VST3 support? I need this very much! Many plugins I am using are only VST3.


  • just out of curiosity, which plugins are only VST3?  I'm just curious.  its only a matter of time before that will be the case increasingly due to Steinberg's draconian licensing politics.

    In the meantime I highly encourage you to check out Kushview Element.  For $2 you can download the latest version and use it to host VST3 plugins inside VePro.

    Believe me, VSL will get VST3 support eventually, they have to because Steinberg is slowly slitting the throat of VST2 plugins everywhere...but anyway, in the meantime...so you can get your music going...check out KushView Element:

    https://kushview.net/element/download/

    if you're handy with a compiler you can even get the source and build it for free!!  I have tested all the various sub-hosting plugins like PlogueBidule, Patchworks, DDMF, etc...and KushView element works the best inside VePro!  All the other ones mentioned, all of which I own...and all of which are NOT free......have GUI related problems inside VePro for now.  But I have had no problems at all with Kushview.  Its quite a decent product and the main developer is also super responsive and nice guy.


  • last edited
    last edited

    @toodamnhip said:

    The VSTs that still failed are: Hand Clapper/Slate SSD5/CSR Hall/Kontakt 3/Melodyne/Ozone 3/PhilharmonikCE/Sample Tank2/Sonar Works/TH1/Trash/iZotope Alloy/RX3/. Please advise.

    Some of those, maybe all, are 32-bit and if your [Mac] OS is past a certain point a no-go. Kontakt 3 I don't think was ever full 64-bit on Mac, SampleTank 2 and CSR Hall won't install here...


  • last edited
    last edited

    @Dewdman42 said:

    just out of curiosity, which plugins are only VST3?  I'm just curious.  its only a matter of time before that will be the case increasingly due to Steinberg's draconian licensing politics.

    In the meantime I highly encourage you to check out Kushview Element.  For $2 you can download the latest version and use it to host VST3 plugins inside VePro.

    Believe me, VSL will get VST3 support eventually, they have to because Steinberg is slowly slitting the throat of VST2 plugins everywhere...but anyway, in the meantime...so you can get your music going...check out KushView Element:

    https://kushview.net/element/download/

    if you're handy with a compiler you can even get the source and build it for free!!  I have tested all the various sub-hosting plugins like PlogueBidule, Patchworks, DDMF, etc...and KushView element works the best inside VePro!  All the other ones mentioned, all of which I own...and all of which are NOT free......have GUI related problems inside VePro for now.  But I have had no problems at all with Kushview.  Its quite a decent product and the main developer is also super responsive and nice guy.

    This has already been posted before! My question was to VSL. Are you from VSL?

    VSL are you suggesting after buying your product now I have to go to a third party solution to make up for the shortcomings in your product?

    VSL look at your company description in about page on your website. You claim many things and sell very expensive software. Least you can do is stand behind your product. I asked you a valid question! Can you answer my question please!

    Do you have an ETA on VST3 support?


  • I don't work for VSL, my suggestions are purely from another user that occasionally needs to run VST3 plugin inside VePro.  This is an open forum.

    VSL tech support can be reached here: support@vsl.co.at


  • Hi smde, 

    I'm afraid I cannot offer an ETA.

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    Hi, Thanks for the reminder. I know that VST3 is still not implemented, and it is still high on the list. I hope that we can provide this feature soon. Unfortunately I cannot offer an ETA, but I will give this another push. Best,Paul
    It has been almost 3 years. So sad to see this.