-
VEP 5 and preferences
-
For me - only in server mode (I dont use VE PRO standalone). Maybe the reason in two different directories of VST - 32 and 64? I have 2 VST folders in system - VST 64 and VST 32, and both servers (x32 and x64) "see" this folders simultaneously... Maybe x64 Server must see only x64 VST folder, and x32 Server only x32 VST folder? In any case x64 server don't work with x32 plug-ins
-
Same problem, VE Pro 5 server but only the 32 bit version. The 64 bit preferences window opens immediately. I don't really know if it takes 10 minutes or if it's just frozen forever, I kill the process in Task Manager. It happens every time.
-
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
-
@angel777 said:
For whose who say "server 32 bit is ok and server 64 bit is slow".....:As I said
open server 64 bit with "vst directories loaded in vst settings" click on preferences: open directly,
open server 32 bit with "vst directories loaded in vst settings" click on preferences: open in 2'20sec
Best regards
Dup
-
My guess: If you setup your VST paths in VE Pro 5, you specifiy the paths to both, x32 and x64 plugins. When you leave the paths preferences dialog, VE Pro 5 analyzes ALL of your plugins in all of your specified paths, BUT, it only SCANs plugins of the same architecture (x32/x64) as the current VE Pro 5 app... Plugins of the other architecture need about the same time to be NOT scanned due to anotehr architecture as plugins of the same architecture take to be scanned, so you might THINK VE Pro 5 scanned all plugins, but it didn't... Now, when you start a VE Pro 5 instance (server, standalone, whatever) of THE OTHER architecture, this VE Pro 5 instance again analyzes ALL of your plugins in all of your specified paths and it again SCANs only plugins of THIS architecture... Once both archicture instances of VE Pro 5 did their scanning, the app opens much quicker...
-
@TabSel said:
My guess: ... When you leave the paths preferences dialog, VE Pro 5 analyzes ALL of your plugins in all of your specified paths,....Thanks but we spoke here when we click to open the preference page not when we leave preference to scans plugin!
But not a great problem ..one the preferences has been given and the plug scanned, no need to open the preference again and again .
And no worries,I know that VSL has a good doctor : Karel
Best regards
Dup
-
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.
Forum Statistics
200,954 users have contributed to 43,220 threads and 259,157 posts.
In the past 24 hours, we have 4 new thread(s), 10 new post(s) and 67 new user(s).