Vienna Symphonic Library Forum
Forum Statistics

178,856 users have contributed to 42,064 threads and 253,923 posts.

In the past 24 hours, we have 3 new thread(s), 7 new post(s) and 56 new user(s).

  • [SOLVED] VEPro 7 & Play VST

    Since last VEPro 7 update today (ver. 7.0.799) Play VST failes plug-in scan in the Server app. It cannot be found in the list of Instruments/Effects in the preferences after so it can be rescanned/re-enabled. It worked fine initially before the update.

    Any solution would be highgly appreciated since Play represents 1/3 of my orchestral template and I do not want to convert everything to the AU version which I do not trust.

    Thanks!


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


  • last edited
    last edited

    @noiseboyuk said:

    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.

    Thanks for the suggestion! It didn't work as smooth (and fast) as you've described in your case. It had to be the longer route for me, of course.

    • I moved the Play.vst out of its original VST folder and performed "Scan For Changes". Nothing siginificant happened. Moved Play.vst back into the VST folder and did "Scan For Changes" again. That didn't detect any differences. Plug-in did not show up in the list.
    • Moved Play.vst out again. This time I did a full "Reset And Rescan All" instead. Took a while. Couple of AU plug-ins failed validation but I was able to right click on them and rescan that particular plug-in which activated them.
    • Finaly, dragged Play.vst back into its proper place and did "Scan For Changes". This time around Play got properly validated!

    My template is alive! 😊

    Thanks again for the workaround!


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


  • Hi Guys,

     

    I have same problems with VEP7. I have tried all options which you have described here, but without success. The VEP can not find PLAY at all.


  • Hi Marek, 

    Did you make sure you opened the 64 bit VE Pro Server?

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Hi Paul,

    Yes, I am absolutely sure that I use 64bit version.

    (I have tried as a STAND ALONE and as a Server too)

    Today I have done some investigation:

    AMD platform with PLAY 6.1.2 -VST3

    VEP6 - 6.0.18067

    VEP7- 7.0.877

    No success.

    But when I install PLAY same version but VST2.4 this is working well.

    Same result on INTEL platform.

    So, temporary I gonna use 2.4VST version of PLAY.


  • Hi Marek, 

    True, VE Pro does not load VST3 plug-ins. I must have overlooked that information. 

    Best,
    Paul


    Paul Kopf Product Manager VSL