[Solved] East West Play problem in Sonar Platinum

This is a bit strange.
 
 I am using Play 4.3.2, now but it was an issue on the previous version too.
 
I insert an instance of Play and add a couple of instruments each driven by a MIDI track. Everything is fine and behaves as expected.
 
THEN suddenly there is no sound from Play. Restarting Sonar does not help. Play does not sound from the midi track, from external MIDI input or from its own virtual keyboard. It seems the problem can only be cured by reloading the instruments in Play.
 
Looking at the streaming settings in Play when the problem occurs I see:
Free System Memory 29476 MB
Max voices 512
Sample memory 289 MB
Samples Loaded 115
Active Streaming Voices 0
Clicking Plays "Reset Engine" button has no effect.
 
 
Other VSTi's still sound so the problem seems to be specific to Play, but does not seem to occur in the stand alone version.
 
I may have found a clue overload protection was enabled and the CPU load limit is 80%. I have disabled protection it and it seems to be more stable, however as there is a degree of randomness I can't be certain its fixed.
EDIT - Added an extra instrument to play and it stopped sounding, so its not the load limit.
 
Has anyone else run into this issue?
 

Thanks guys, it was the mod wheel.

konradh
Was this Hollywood Strings?  I find that library very confusing since volume is controlled different ways on different patches, and velocity and mod wheel do different things on different patches.  I'm not saying it's bad--just confusing.
 

Not sure which library the OP was using, but yes, agreed it is confusing. Too bad they sound so darned good...
 
I've noticed that the newer version of Play have changed the way older libraries like EWQLSO responds to mod wheel data as well. Not on every patch, but some now work with the mod wheel...unless I'm imagining it...
 
Regards,
Dan

Resonant Serpent
So, this is a work-around? Just record mod wheel movements that are tied to nothing? Sonar deficiency, or known problem with the Play engine?
 

It's by design in these libraries. For example, in Hollywood Orchestra, rather than have several tracks with different articulations, you use the mod wheel to switch from articulation to articulation, as well as raise and lower the volume. It's pretty smart what EastWest has done...
 
Regards,
Dan

FWIW the library in question was Steven Wilson's Ghost Writer, most (all?) patches in this library seem to use this method.
 
I need to look at asigning a slider on my A-PRO 800 to modulation for EW as both my keyboards have Roland type sprung mod levers.

Thanks for the explanation. I've had the subscription for months now, but haven't had time to dive in until later this month. 

note ... "Spose you could create a collection of midi files with mod cc data set for different articulations." 

I'm using Hollywood Orchestra (mostly) and my templates have the values already initialized. Otherwise I would forget! Of course if you are using CC1 to switch patches that might not work as well for you.