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

Hi,

interesting ...

What about the delay compensation? Do VSL can detect latency of a plugin loaded inside the chainer?

thanks!

Hi,

just one more question abuot this thread..

I'm using reverbs on VEP server.

In nuendo, in the FX send channel i've loaded VEP audio input. The reverb sound the return from th VEP instrument. All is ok.

But...if i put in solo the channel that sends to the server reverbs only the nuendo FX channel go in solo (the VEP instruments is muted as nuendo doesn't know that the sound come back from there...)

Any solutions?

Thanks!

PS: linking FX send and VEP instruments channels won't work.

I thinked about this solution in the meantime but studiorack is really slow to load on VEP! ..don't know why..

I hope they will fix at least the TAB issue to see all the waves plugins in the view (or at least possibility to split them in different folders ex waves1 waves2 waves3..)

 

Really no workaround for this?

Waves are the most famous plugins and i cant' see all of them for a simple TAB issue?

please let us know..

Hi,

really no solution for this? In VEP 5 there was no problem.

Hi,

i've created .dll files with waveshell2vst64 from the waves complete bundle.
All plugins are in \waves folder and they are detected from vsl (in preferences i can see all of them after a vst folder scan).
When i try to add a waves plugin i can see just one page of plugins and i can't scroll to see all. 
I've tried to separate the .dll in more than one folder (waves1, waves2..) but vsl show me just one \waves folder.

what can i do?
thanks,

regards,

Samuele

hi,

after some test i found that it seems to be related to the number of vst plugins and instruments installed.
With all plugins and instruments scanned ,EXCEPT waves plugins, it takes about 2.5 seconds to open preferences window.

I've tried so to add just 1 waves plugins to know if this problem is related to waves plugins but it takes agains 2.5 seconds to open preferences window.

If i add instead the WHOLE waves mercury bundle it takes about 10 minutes to open the preferences window.

NB: the waves plugins are "exploded" with waveshell and than wrapped with jbridge.

Please i need help, i'm still not able to use VEP5 since i've purchased it.

Now i can say that is not a general jbridge problem, if i add my vst folder with jbridged 32->64 vst Instruments all is fast..but when i add vst plugins 32->64 folder it become very slow to open.

Any ideas?
thanks!

ehm...sorry, i have to correct myself:

if i use only native 64 bit plugins the problem doesn't appear,
it seems to be related to jbridged plugins,

cheers,
Sam

In VEP 5 64 server i've tried to use only native 64 bit plugins and the problem still happens.

It is ok only if there are no vst directories loaded in vst settings.

For whose who say "server 32 bit is ok and server 64 bit is slow": are you sure that there are no vst directories loaded in 64 bit server?


I've told about 10 minutes...fist time i thinked ti was froozen...then i waited so and after 10 minutes i've discovered that preferences window appears

cheers
Sam

me too i use only server mode.

I use native 64 bit plugins and jbridged 32->64.

I'll try only with 64 bit native to see if the bug still happen.

Hi,
i have this bug: when i click on preferences it takes about 10 minutes to open that window.
If there are no vst directories added that problem doesn't appears.

Any solutions?
Cheers,
Sam

Ok but i mean 32 bit plugins in 64 bit vep 5..

try a re-scan in the preferences window after you closed the window where you've removed the vst plugin folder..

hi,

i just switched to vienna ensemble pro 5.

I was using ensemble pro 4 with jbridge but now, after switching, many j-bridged plugins are not recognized in ensemble pro 5(but they were ok in ensemble pro 4).For exemple SPL analog code plugins...