Vienna Symphonic Library Forum
Forum Statistics

202,324 users have contributed to 43,284 threads and 259,412 posts.

In the past 24 hours, we have 2 new thread(s), 5 new post(s) and 77 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. external plugins no longer recognized ??

  • external plugins no longer recognized ??

    R
    R
    Hey, Somewhat of a drama is happening here if i can not find a solution for this. So please help! I changed the server settings of VEP5. I lowered the number of midi ports so that the unused midi ports were removed. When i reload the viframes, in fact any of the viframes i made, they refuse to load any external plugin. So any non VI plugin does not load any more in VEP5. (these are the main developers: kontakt, spectrasonics, steinberg, ...) I changed everything back to the previous settings. I can load the viframes, but still every non VI plugin refuses to load. I get an error message of VEP5: can´t load the plugin and then it´s name. For the rest, everything is ok in the system, dongles are running, codes are ok, etc... This means i am virtually out of bussiness if that remains the fact. :-/ What can i do to solve this ?? Kind regards in advance for helping me through this. R.
  • R
    R
    further addition to the problem: I was investigating this, and in VEP PRO 5, and i am shure it is the VEP pro 5, there is no longer a possibility to load a non VI plugin. I can only choose: add VI pro add instrument add inpu add bus Should i reinstall the program ? Can i do this without losing my Viframes ?
  • R
    R
    ok, think i got it solved. For some reason the server lost all its settings of the locations where the vsts were installed. The server just located the VI instruments and the rest was gone. Adding the paths again and rescanning the database does seem to do the trick. Fieuw, this was close to big big trouble. Is there any reason that can be given why this is happening: the server is losing the paths ? Because this is dangerous when you are not cool enough to investigate it step by step if this happens. Many thanks for any answer. kind regards, R.
  • R
    R
    and to end the info on the topic: - i had to do the rescan for both the 32 and the 64 bit servers. - rescanning one (the 64 bit) did not solve the paths for the other server (32 bit) - when this was done, and i checked the vipresets i needm then i noticed that i did use more then the lowered number of midi ports on some of my main vipresets, so they were still getting errors - after raising it back to the 16 i had before, everything went back to normal so in the end i guess it is as follows: stick to the number you have assigned and never lower it. kind regards, R.