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.)

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.

Hello everyone,

Great that VST3 integration, thank you. Just a small detail for me, when I reset the Plugins, only one problem is VSL Powerpan. I get the following message:"Failed validation:(VST3) VSL Powerpan1 plug-in failed validation and has been disabled.Check that you are using the latest version of the disabled plug-in(s) and try another rescan.

Thank you to the whole VSL team !

Gérard

Windows 11 - 64bits - 64 Go

Cubase Pro 12 - VSL (almost complete) - MIR Pro - Native - rme-Fireface UX, etc... Dorico-Sibelieus-Finale ....

Finally bit the bullet and updated to v 7.3.3335 because I needed support for Kontakt7 (VST3-only.)  That meant moving from the old verification dongles to iLok on my two servers, but that seemed to go just fine. Installed Vienna Assistant, did the iLoc transfer to my account, down loaded and installed the new 7.3.3335 and on the SERVERS, everything looks good.  iLok shows everything is activated, my old settings came over into the new version's preferences, and all my VST3s load perfectly.

HOWEVER, my DAW machine no longer sees the two servers. I made sure Bonjour was running on everything and that none of the machines had an active firewall going. I made sure the servers were set to broadcast their addresses. The three machines can see each other fine on the network, but from within the DAW, no servers show up when I either load an existing project, or try to start a new project and connect to a VEP server.  DAW is Cakewalk, which was working fine with these two servers on version 7.0 for two years.  All machines are running Win10 Pro.

This is what I do for a living, and I'm now unable to work. Considering restoring the machines from a backup and continuing without VST3 support, but since the licenses are now sitting on iLok, I imagine that my old dongles won't be able to run the servers.

Any suggestions would be appreciated.

Hello Paul,

Soundpaint vst3 doesn´t show up in VEPro

Best

Ritchie