We are looking into this. Unfortunately the main problem is the inability of Kontakt to change samplerate without reloading the plugin. No other plugin does this, so we'll have to make an exception for it probably.

Thanks Karel

It would be really terrific if somethinig could be done, maybe soon?. Preloading and keeping open all day my Meta Ensemble Templates is not practical for me due to this instability, very, very frustrating.

Kind Regards

Calculus

HI
After further investigation:
My System Sample rate is now set to external sync at 48KHZ (by syncing RME Fireface as slave(autosync) to external soundcard set at 48KHZ. This totally eliminates 44.1KHZ behaviour 'ping' at Cubase startup. 48KHZ permanently on!.

This now totally highlights (having got Cubase ping of the way) the problem with VSL/Kontakt limitation.

Before starting cubase:
1.Create new metaframe instance with Kontakt and LASS
2. Open new Cubase project set at 48KHZ (never pings 44.1KHZ)
3.Connect to Metaframe that was newly created.
4. Play some notes, LASS legato is fine and works correctly
5. Go to the connected Slave VSL Ensemble and turn audio engine power button off then on again.
6. LASS is now corrupted as the Sample rate in VSL has switched from its 'default' 44.1KHZ to the desired 48KHZ. The corruption level can vary but it always happens. The same thing will happen by saving the cubase project.

This clearly shows that when loading a VSL Metaframe (without Cubase 48KHZ project open) it will always load at 44.1KHZ as there is no way of setting a fixed sample rate in Ensemble Server or choose the current system clock setting.

You can see the default sample rate in VSL Server by loading a new empty metaframe instance (without cubase open) and turning on the Audio engine power button. Instead of the sample rate being set to the current system setting of 48KHZ it ignores this and opens at 44.1.

If VSL Server (on starting up) was modified to adopt the 48KHZ current system sample rate there would be no corruption. This is as long as the Cubase ping is eliminated with the hardware solution. Maybe Steinberg will get rid of this behaviour but this cannot be waited for.

Finally, a temporary workaround:
1. start Cubase project at desired 48KHZ
2. Connect to all ensemble slaves with VSL ensembles in VSTi rack.
3. Load kontakt and LASS sample instruments on slaves.
4. preserve Ensemble slave instances and save metaframe
3. Make sure decouple is not enabled as this new project needs to load at the start of next days work to get all ready for connecting to projects.
4. Save Project as default Cubase project!
Cubase can now be closed and restarted at will and all slaves remain fixed at 48KHZ enabling connection to any 48KHZ project that has the project saved with Ensemble decoupled.

@AndrewW said:

Fletchtown,
You may want to go back to VEPro built 4881.  I ran across the same problem with hanging notes with the newest version. Yes there are few very interesting features, like force disconnect from the VEPro server, but not having hainging notes is more crushal.

I've experienced this also on MacPro, Logic, VEPro combination. 

Try the earlier version of VEPro and see if it solves your issues. 

Best of luck.