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.

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

Originally Posted by: Guin

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.

Great, thanks Paul :)

Well that was a nasty shock. According to MyVSL, VI Pro and my Plus editions of SE Woodwinds vols 1 and 2 are not upgradable to iLok. Which means sooner or later these products I've bought and paid for - and integrated into my template are going to simply disappear, when eLicenser does.

Extremely disappointing, and will mark the end of any new VSL purchases from me if it stands.

Originally Posted by: J-M

Sorry for my ignorance, but if I were to do this I wouldn't be able to process, for example, my individual percussion instruments individually inside Cubase? That goes against my preferred workflow, which kinda sucks.

It depends.  If you are using single audio output instances of Kontakt (or whatever) for each instrument you wouldn't be affected. It only seems to affect it if you have multiple outs, and also (it seems) if its a version prior to VEP7.

dlpmusic's findings chime with me, I think that really narrows down the area where the problem lies (or lay).

I still haven't had this in VEP7 though, as far as I can remember. Paul (or any other VSL employee), do you think this has been definitively addressed in 7?

I've had this issue with VEP6 but AFAIK it's not happened in VEP7.

I'd reccommend Nugen's Sigmod as a hearing / equipement protector, because it really is terrifyingly loud when it happens.  I keep it in circuit all the time now.

Originally Posted by: MS

This is unfortunately not possible. Individual plug-ins allocate memory from the system directly, and we don't know anything about it.

Ah that is a great shame, but thanks for letting us know.

Perhaps one thing that would be possible is some kind of visual indication if every plugin in an instance is disabled?  Not as compreshensive as a full RAM tally, but that would really help me actually.

Just a bump for this.  Would be invaluable for those working with disabled templates in particular - just spent an eternity tracking something down which would have been trivial if I could see the instance using the most memory.

Very much enjoying VEP 7.  Great to have the CPU monitor on instances, and the tabbed side view is so much better for seeing what's going on at a glance.  Icing on the cake would be a RAM useage monitor next to the CPU, at least as an option.

Figured I can only ask....

Glad you found a way!  Yes, seems like that scanning routine is still a bit tricksy in general, hopefully VSL can track down what's causing this sort of thing.  The specifics seem to be different for everyone, but generally its a little flaky.

Just to say Play is stil fine on Windows 10 on the new update.

It sounds like there are still some glitches on the scanning routine, producing sometimes erratic results.  One thing that MAY have worked in my case - could be wrong - is to move the plugin out of the regular folder, scan for changes, move it back in again and scan for changes once more.  Worth a shot while VSL keep working on this.

Originally Posted by: civilization 3

One user reported VEP 7 won't see UVI Workstation.

Just to say that's resolved in the next build (my understanding is it was not an issue specific to the UVI Workstation, but a general problem scanning certain libraries on certain setups).

Nothng is affected re any VSL libraries, those will load as normal in VI Player or VI Pro, so no worries on that score.

Yes, hang in there for the next release.  Should be soon I think.

A huge thanks to support - fixed in the next build!  Amazingly quick response, thanks folks.

Wow, that sounds fantastic, thanks Martin!  Very quick too, amazing work.

...to add that Support are looking at it, currently unable to replicate.  Here's a video I did for them that demonstrates what is happening my end:

https://youtu.be/lWdmgjb6uag

Originally Posted by: MS

Guy,

Your bug reports are being taken care of right now.

Regarding the parameter copy - perhaps you would be helped by an alt-drag for copying the midi source to the next entry?

We also have discussed a feature to enable channels on MIDI note-on activity - I don't know if that would be of help for you?

Great news re bugs, thanks Martin!

Alt-drag - could you explain a little more?  Not sure I'm quite following.

A wake on midi would be absolutely terrific, its something I've been calling for for a long time.  In an ideal world that would be in addition to a Next button, but I guess that's pretty greedy :)

Thanks v much Martin.  #2 might be superceded with #3 if you could implement that, but one thing I do a lot is route successive midi channels to the same disable channel command, for example.  So if I could copy / paste that disable channel from one destination to many, it would save a lot of mouse clicks.

But as I say, if there was a really slick auto-increment Next feature where we could quickly set the parmeters - in my example increment midi channel number, keep the destination the same - then that would be even better :)

Just to say that tried installing today's new build 7.0.778 but no change to behaviour.  I see other users having issues with other plugins - one cannot see Omnisphere, which I can see.  Something definitely looks screwy with the plugin scanning / initialisation routine.

Originally Posted by: bbelius

"Destroying" is a technical description from the developer for the unloading process. It does not destroy your plugins. :D

I do realise that - but its a very apt description of what I see VEP doing.  One second they're there, then BAM they get destroyed.

Thanks you two.  Bill, have updated iLok Manager, restarted, rescanned all plugs.  It reported only 2 did not initialize - z3ta+ (a Cakewalk Synth) and iZotope Ozone 8.  I OK'd that box and saw UVI and a load more appear in my plugin list - HOORAY!

2 seconds later, all these vanished in a puff of smoke.  So back to square one.

bbelius, thanks for that info.  Here's the offending stretches:

---

FIRST SCAN - v3.02:

Creating VST Plugin: C:/VSTs/UVIWorkstationVSTx64.dll

2019-05-02 18:08:13.118 INFO  [13636] [VstPlugin::] Opening VST Plugin

2019-05-02 18:08:13.508 ERROR [13636] [VstLoader::] Error loading library: Cannot load library C:\VSTs\UVIWorkstationVSTx64.dll: A dynamic link library (DLL) initialization routine failed.

2019-05-02 18:08:13.508 ERROR [13636] [VstPlugin::] Could not load VST library

2019-05-02 18:08:13.510 INFO  [13636] [VstPlugin::] Destroying VST Plugin: C:/VSTs/UVIWorkstationVSTx64.dll

SECOND SCAN - v3.05

Creating VST Plugin: C:/VSTs/UVIWorkstationVSTx64.dll

2019-05-02 19:50:37.060 INFO  [9924] [VstPlugin::] Opening VST Plugin

2019-05-02 19:50:37.454 INFO  [9924] [VstPlugin::] VST version: 2400

2019-05-02 19:50:37.454 INFO  [9924] [VstPlugin::] Reading speaker arrangement information

2019-05-02 19:50:37.454 INFO  [9924] [VstPlugin::] Updating bus channel counts

2019-05-02 19:50:37.454 INFO  [9924] [VstPlugin::] Plugin opened successfully

2019-05-02 19:50:37.464 INFO  [9924] [VstPlugin::] Destroying VST Plugin: C:/VSTs/UVIWorkstationVSTx64.dll

2019-05-02 19:50:39.476 INFO  [9924] [VstLoader::] Unloading: C:/VSTs/UVIWorkstationVSTx64.dll

THIS LAST TIME:

Creating VST Plugin: C:/VSTs/UVIWorkstationVSTx64.dll

2019-05-02 21:07:00.520 INFO  [2416] [VstPlugin::] Opening VST Plugin

2019-05-02 21:07:00.955 ERROR [2416] [VstLoader::] Error loading library: Cannot load library C:\VSTs\UVIWorkstationVSTx64.dll: A dynamic link library (DLL) initialization routine failed.

2019-05-02 21:07:00.955 ERROR [2416] [VstPlugin::] Could not load VST library

2019-05-02 21:07:00.956 INFO  [2416] [VstPlugin::] Destroying VST Plugin: C:/VSTs/UVIWorkstationVSTx64.dll

---

That 2nd time is especially odd - all seemed to go swimmingly, then it destroyed it.

"Destroyed" feels like an extremely apt word to describe what VEP7 is doing to my plugins.

This is a pretty serious one - updated to the latest version of UVI Workstation, 3.05.  VEP scans it ok but then discards it.  Plugin passes normally in Cubase and AFAIK all other DAWs.  There's important stuff on this platform, this needs a fix ASAP.  Thanks.