"Fixed in X3" ------ well, isn't that great?!    Now I just have to pay $149 to get it!    Why can't it be fixed in X2?!!!!!  Seriously?

it's been "addressed" in x3b, i'd love to hear if it's actually fixed :)

lawp
it's been "addressed" in x3b, i'd love to hear if it's actually fixed :)

So would I.   There is not even an X3 demo to find out.   Does anyone know, for sure?   
 

I can load multiple instances of the Cream plugin (demo version) into audio tracks' FX bins and route their outputs to the inputs of MIDI tracks.  I've not got it 'up and running' yet 'cos I'm still learning how to drive the plugin.

Not stable (for me anyway), I was getting 2x instances of Kirnu Cream working and Sonar X3b crashed.
 
Fault report sent to Cakewalk.
 
Plugins-wise, the project had two instances of True Piano, two instances of Kirnu Cream, nothing else.
 
[edit]

As an aside, the routing is a real PITA.  I don't understand why Cream isn't classified as a MIDI FX plugin, rather than a soft synth.  It doesn't make sounds (does it?), it just receives and sends MIDI as far as I understand it so the MIDI FX bin would seem to be the logical place for it to live.  That'd make the routing and input echoing set-up more straightforward to arrange.

I've just tried it again with a new project and this time it's running and seems stable with 2x instances of Cream.
 
Apologies; I'd forgotten that in the previous test, there was a track from the project I used as a starting point which has some EQ plugins which occasionally do crash Sonar, so it might have been them that was causing the problem.
 
[edit]
 
OK, this project just crashed as well when using > 1 instance of Cream in Sonar X3b.  This time, definitely no other plugins other than a couple of true piano instances used for the output.

Out of curiosity and to check out X3b with Cream.
 
The following worked for me:
first instance Cream-1: sending on 3 Cream-1 -tracks midi 1 to 3 to 3 different instruments receiving midi 1 to 3 from Cream-1 respectively.
second instance Cream-2: sending on Cream-2-track 1 midi 1 to one instrument receiving midi 1 from Cream-2
 
The Cream instances have been generated as "simple instruments tracks" with "midi output" enabled. But I send the audio output not to the master but to "none".
 
After seconds running those tracks I had a crash of Sonar. But after restart and reload of the project, everything went fine.

Thanks guys for checking this out.    Seems the results are inconsistant.  Glad to know that it wasn't just me ...
 
@ston : did you get those issue with inpout echo that got -- ie, when running the track with a Cream arp, and then adding another track (withoutarp) on top (eg, a chord) - playing that new track also affects the original Cream track (because its input echo was on)?  I tried your suggestions re the MIDI channels but never got it to work - maybe I didn't do it right ...

@soundraider --- so 1 instance of Cream can run several different soft synths on different tracks, when the Midi routing is correct?   If that is so, then I think my issue of Sonar crashing with 2 instances of Cream could be solved?

ULTRABRA
@soundraider --- so 1 instance of Cream can run several different soft synths on different tracks, when the Midi routing is correct?   If that is so, then I think my issue of Sonar crashing with 2 instances of Cream could be solved?

Yes - we have 4 Cream-Tracks.
 
To get the tracks to different midi channels you can set the midi-out of each track separately in the top header area. We have also the option to set different midi-input channels per track, but I never checked this out.
Make sure, that the receiving instrument is listening to the correct Cream-output channel. It might be necessary to set not only the Sonar Track to this channel but the instrument also. I had an issue with Kontakt until each Kontakt-Instrument was set listening to the corresponding Cream-output channel.
 
Have Fun ;)