Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
[SOLVED] VEPro 7 & Play VST
Last post Thu, Jul 25 2019 by Paul, 8 replies.
Options
Go to last post
Posted on Wed, May 08 2019 04:17
by ZWaves
Joined on Mon, Dec 18 2017, Los Angeles, Ca, Posts 63

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!

Special Edition Complete (Vols.1-4), SYNCHRON-ized SE Bundle (Vols.1-4)
Single Instruments, Vienna Ensemble Pro, VI Pro 2, MIR Pro, MIRx Bundle
Cubase Pro, Logic Pro X, Pro Tools, Notion
macOS 10.15.7, Mac mini 6-Core i7, 64GB RAM
Tags: play vepro 7
Posted on Wed, May 08 2019 06:44
by noiseboyuk
Joined on Tue, Nov 17 2009, Posts 89

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.

Win 10 Pro 64 bit, i7 7820X, RME Babyface, 64gb RAM, Cubase Pro 2, PT Ultimate 2022, VE Pro 7
Posted on Wed, May 08 2019 08:45
by ZWaves
Joined on Mon, Dec 18 2017, Los Angeles, Ca, Posts 63

Originally Posted by: noiseboyuk Go to Quoted Post

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!

Special Edition Complete (Vols.1-4), SYNCHRON-ized SE Bundle (Vols.1-4)
Single Instruments, Vienna Ensemble Pro, VI Pro 2, MIR Pro, MIRx Bundle
Cubase Pro, Logic Pro X, Pro Tools, Notion
macOS 10.15.7, Mac mini 6-Core i7, 64GB RAM
Posted on Wed, May 08 2019 10:18
by noiseboyuk
Joined on Tue, Nov 17 2009, Posts 89

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.

Win 10 Pro 64 bit, i7 7820X, RME Babyface, 64gb RAM, Cubase Pro 2, PT Ultimate 2022, VE Pro 7
Posted on Tue, Jul 23 2019 20:48
by Marek
Joined on Thu, Sep 20 2007, Posts 8

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.

Posted on Thu, Jul 25 2019 04:14
by Paul
Joined on Sat, Aug 03 2002, Vienna, Posts 13811

Hi Marek, 

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

Best, 
Paul

Paul Kopf
Product Manager - Vienna Symphonic Library
Posted on Thu, Jul 25 2019 20:04
by Marek
Joined on Thu, Sep 20 2007, Posts 8

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.

Posted on Thu, Jul 25 2019 22:03
by Paul
Joined on Sat, Aug 03 2002, Vienna, Posts 13811

Hi Marek, 

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

Best,
Paul

Paul Kopf
Product Manager - Vienna Symphonic Library
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.