I'm experiencing a similar problem, VI Pro player can't find all of my instruments, but the VI player can.

So far, two solo violin patchs, 01 vi_staccato and 02 vi_detache-short are showing in the matrix view as though they are loaded, but they are actually not available for play and no sounds can be elicited from play although other patches in the same matrix do play very well-actually the 01VI-Staccato loads but the virtual keyboard below is entirely greyed out as though the patch is not even there but the current patch display window shows it loaded and when the file is dragged from patch file browser to the matrix view, VI Pro shows it loading but then. .  nothing.

Hope a solution is available from the VSL team.

Thanks in advance for assistance

Ray Phenicie

Southfield MI USA

Actually, I'm going to break this out into a new thread.

 After various installs/reinstalls, I can get PLAYx64 to load into a completely clean vframe, but am totally unable to load either vframes or mframes which contain this plugin.

I'm aware that PLAy support has been a long drawnout saga, but as it is now officially supported, it would be good if these loose ends could finally be resolved. 

Jules

I recommend you to direct this to East West support. Also make sure you're using a Play version 2.0.18 or later, since that is the version in which VE Pro compatibility was fixed.

Hi Karel - thanks for your response.

I have investigated this issue further, and I have to say that from a completely non-technical perspective (and without wanting to be provocative), in this specific case it looks perhaps more like a VE Pro issue than a PLAY issue.  The reason I say this, is that the probelm seems to stem from VE Pro not recognizing the PLAY plugin at all, or 'forgetting' that it is in the VST list.  I have started scanning my VST folder every time I try and start work, and often after a reboot, the PLAY plugin is not seen by VE Pro.  I have to delete folders, add them again (in VE Pro options) and then rescan, and then it sees PLAY.   Sometimes I have to move the PLAY folder altogether and then rescan.

Does this not suggest that VE Pro is perhaps not retaining VST settings correctly?  It seems to be more a problem of setting/option retention in VE Pro, than a technical issue with the plugin itself, although that's obviously only an uneducated impression.    Once VE Pro 'sees' PLAY, I have no issues at all - it never crashes, there are no GUI, streaming or other problems with the plugin, it's simply that VE Pro seems to 'lose' it from time to time.

I will raise it with EW as well, but would be hugely grateful if there was any way you and your developers might have a moment to check what might be causing VST settings/plugin lists to become 'damaged' or incomplete.

Can I perhaps ask whilst writing - do the 32 and 64 bit versions of VE Pro share options settings, and specifically VST settings?  I ask because I have been trying to experimwnt with keeping 32 and 64 bit plugins separate, and directing the 32 and 64bit versions of VE Pro only to the appropriate plugin folders.  Obviously if they share VST plugin settings then this might be counter-productive.

Many thanks again for your help.

Jules

I will try to investigate this behavior with Play.

The VST folders setting is shared between 32bit/64bit, so there should be no meaningful benefit or disadvantage from having seperate folders.

Thanks Karel

Today for the first time this week, my VE Pro template loaded without issue.    Perhaps I've finally managed to get the PLAY plugin properly registered with VE Pro's VST settings (fingers crossed).

Thanks for confirmation on 32/64bit settings sharing.  Sounds like I should not try and differentiate between plugin folders in that case.

Jules

I've had this off and on. Download and install the latest Play software 2.0.21 I think it is as the VSL Pro integration is still a live issue.  As a safety measure (!) when you have a working template which includes Play, save off all the other non play instruments as a channel set and then the play ones separately. That way at least you can rebuild quicker.  

A lot of it I think is down to memory issues. I started having problems on Vista 64 because of the memory management system. Look at the task manager and check out how much free memory there is. 

Many thanks for your response Flashman.

I can see very little pattern to when VE Pro will or will not load PLAY.  I load the same template every single day - yesterday it loaded without issue, today it gave me the 'Cannot load plugin' error, even though PLAY is in the plugin list when I check.

I have 24GB RAm on the system and my template uses under 20GB - big, but plenty of space to spare.  Also, I always load it first thing, with no other apps running, nothing else using memory.

Sometimes, if the template won't load, I'm able to manually load the two VE Pro instances which contain PLAY.  Other times (like today) even that won't work and gives me the same error.  Some times, I can load PLAY in a clean vframe, other times (like today) that doesn't work either - even though it's in the plugin list.   Sometimes if I rescan my plugin folder it fixes the issue.  Other times it doesn't.  It's a constant repetitive dance of random variables trying to get these two components to work together.

The situation is certainly worse with this build than the previous one, which would always let me load my PLAY vframes separately if the full template wouldn't load.  Incidentally I'm using the 64bit versions in each case - the 32bit situation may be more reliable.

I'm running the latest PLAY version and have been for the last 4 weeks or so.  Extremely frustrating and can result in hours and hours of lost time every day, just trying to load an mframe.  Oh well, here's hoiping East West and VSL are talking to each other, but I can't help worrying that each party holds the other responsible and nobody really wants to commit the time and resources to getting this fully resolved.  I hope I'm wrong.

Jules

I have the same issues and I suspect it's down to the way Vista caches unused memory which Play can't handle.  I saved the play and Kontakt instriments as separate channel sets and then built the template so Play loads first and that seems to work. EW are aware of this issue though and it does seem to effect Vista 64 specifically. Post something on the EW forum as well to jog their memory!

Flashman - thankyou again.

I'm currently in the process of doing a complete uninstall of all PLAY and VE Pro software on the system, just to make sure I'm working from a clean start.  I will then rebuild my templates, and put the PLAY instances at the top of the list (there goes the rest of today).  As it happens, they currently load last in my 64bit mframe, so your theory could be absolutely spot-on.

I've also posted to the EW support forum, so hopefully they will take a look at this.  It's been an issue hear for as long as I can remember, so really needs to get sorted now.

I still feel there may be a plugin recognition issue with VE Pro and PLAY which may be more on the host side, as VE Pro seems to ocassionally 'lose' the PLAY plugin from its plugin list (as described above), but this may be a separate issue.

Thanks again

Jules