182,958 users have contributed to 42,268 threads and 254,960 posts.
In the past 24 hours, we have 7 new thread(s), 14 new post(s) and 48 new user(s).
1. please include an listing for the VST3 folders as well as the VST!!
Now, VePro seems to just scan all VST3 which is a pain. Since I still install my important VST3 in other folders than the default VST3 windows folder, I like to have the ability to exclude the default path from being scanned.
2. the SKIP button is not working. It should radically stop scanning the current plugin but it just keeps on going and going - f.e. on U-HEs Zebrify
Have just tried the latest Beta 7.2.1494 on Win 10 Pro - https://vi-control.net/community/threads/vep7-whats-new-and-improved-v7-2-1481-2023-01-19-vst3-hosting.81869/page-7#post-5280775 . I think some progress, but still some problems.
The following VST3 plugins all failed the scan:
iZotope
Tonal Balance Control 2
Neutron 3 eq/compressor
Breaktweaker
Ozone 9 eq
RX6 de-esser
RX7 monitor
RX8 voice de-noise
Korg
Polysix
VIR Harmonic
Bohemian Cello
Steinberg
Spectralayers
u-he
ZebraHZ
I'd been having problems with East West Opus (current version) on the previous build. While it scanned, it would crash sometimes on disable/enable or a project load, or if it did re-load it would be silent.
On this beta build it seems to disable/enable fine and the project loads fine if enabled. However if I load the project with Opus in a disabled state, it crashes VE Pro.
Thanks for your continued work on the problem.
Hello again!
I've tried the new VEPro version, and converted all Kontakt instances to VST3. All of the issues I mentioned before are now gone! Thank you, VSL!
That said, the EW Play engine isn't yet available to use as a VST3 plugin. It's listed on the Preferences Menu / Avaliable Plugins, but I can't assign it on the Mixer window.
Thank you for your time!
Hi,
Thanks for the feedback!
Please let us know if anything slipped through, we're confident that most reported bugs have been fixed!
Best,
Paul
Hello again,
Yes, I can report that all issues I mentioned before have been solved. Nice job! It's great to finally have the chance to load Steinberg VST instruments again on VEPro. Oh, and the EW Play VST3 engine became available after rescanning all plugins!
There's just a couple more issues that seem to have occured. Didn't notice them because these aren't currently on my template.
That's about it all. Let me know if there's anything else I can help with.
Thank you again for your time!
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.
All those issues seem to be solved by the 7.2.1495 update. Thank you, VSL.
Just updated to the latest version, but got some weird thing going on.
With the fresh plugin scan it keeps hanging on an error with the following plugins Izotope Breaktweaker or Relay VST3 ( latest versions )
VST2 loads without errors
The weird thing is that the vst3 works normal with Cubase / FL / Ableton.and StudioOne.
Someone else bumping to this challenge?
Hi,
Thanks for posting.
Can you please be so kind and add your OSs and used versions (DAW, VE Pro) with any reports? We can play detective and look for that information in all your other postings, but we are loosing time unnecessarily.
THANKS!
Paul
Sorry for the lack of info:
Another info that might help and I just noticed. I started a new blank project on Cubase. Since it's possible to see the server reference, I placed manually the info of both the server, and the instance. Once I did that, when opening the second VEPro instrument plugin, it actually showed all available instances. If I disconnect all of them, the instances can't be automatically found again.
Hi Guin,
Please get in touch with us directly: support@vsl.co.at
We have a few cases like yours, but it seems hard to pin down what's going on. Working on the next VE Pro version already, and it would be great to have a few users to test and help us this way.
Thanks,
Paul
Got some funky stuff going on here.
I was on build 1494, got the link from VI-Control. This fixed the "VST3 parameters not recalling" bug for me and worked fine, apart from a few minor things. Today, I saw that a VEP update was available that addresses most of my issues. I went online to update VEP to build 1495. After that, I got this: vepfail.png (501×208) (ibb.co)
Rolled back to 1494. Now my server project file won't open anymore, it's crashing VEP straight to the desktop while opening.
I'm not in the middle of a project right now (wouldn't have updated otherwise), but it's still an unsettling situation.
PC:
ASUS PRIME H670-Plus D4 Mainboard
Intel i7-12700K
128 GB 3200 MT/s DDR4 RAM
nVidia GeForce GT1030
System SSD: Samsung 980 250GB NVMe M.2
Content SSD: Samsung 870 EVO 4TB
Windows 10 Pro Build 19045.2364
(EDIT: And, of course, I tried everything from re-booting to a fresh install of VEP, both with builds 1494 and 1495.)
Hello
I have installed the latest versions of VE Pro and the Kontakt player. When I try to open a Sonokintic plugin (Sleigh Bells) in the Kontakt player I get a message telling me the version of Kontakt I'm using is too old for the plugin.
It works ok in Kontakt standalone player but not as a plugin in the VEPro - host or standalone version, so I'm assuming it's a VE Pro issue?
Thanks, CD
Hi, I noticed an issue similar to what someone else has described here. After a while, VEPRO in my DAW will not show any server instances to connect to (on my same network, no slave). However, when I input the specific server and instance information, it will connect with no problem, even though it doesn't show that being available. Not a huge deal I guess, since I can manually connect the instances, but worth noting.
