@swamptooth ... it seems that you want to keep me busy, don't you?
 
I don't think that I get your point about the voices, because both tracks are one octave apart only and both share enough key range for the demo. It's not an artifact of "missing" notes!
 
I generated two tracks - each having notes and rests at different timings. A crosstalk between the tracks should have generated notes in both tracks, where the rests should have been. Didn't happen.
 
My demo has the follwing setting:
- Cream-1: output midi-2 --> track "keys"
- Cream-2: output midi 1 --> track "Kontakt 5"
You can see this in the video, lower part, in the mixer section ...
 
I will check with synths later, just to be shure that this is not special to "Kontakt". Can you explain what you mean with "recording"? During playback I let the Creams run and do the arpeggios ... ?

arm the midi tracks that are going into kontakt to record, and record the input from cream.
any chance you can email me that test project?  i'll shoot you a message with my email address.

lawp

satyatunes
This is THE best arpeggiator plugin. I saw a similar thread in their official forum in KVR. I am sure Arto must be working on a fix as we speak.

sorry ULTRABRA, should've quoted the above, was trying to put focus on sonar rather than cream for the fix :)

I should have worded my sentence carefully. I shouldn't have used "Fix" here. Anyway, my apologies. I have been away from Sonar quite some time, returned recently with X3 so wasn't aware of long standing midi out issue. Has anyone tried the same situation in another DAW? I have Reaper and will definitely try it out but that will happen only after Wednesday or over the coming weekend.

works fine in live 9 & studio one 2.6 ;)

swamptooth
arm the midi tracks that are going into kontakt to record, and record the input from cream.
any chance you can email me that test project?  i'll shoot you a message with my email address.

Here is a short update ... in the case of recording I have crossing over of Cream outpus as you reported.
 
This is my set up:
Track 1: Cream-1 sending on midi 1 with a two-notes chord and a slow arp pattern
Track 2: Synth-1 listening to Cream-1
Track 3: Cream-2 sending on midi 1 with a two-notes chord (a minor third shifted) and a fast arp pattern
Track 4: synth-2 listening to Cream-2
 
Track 2 and 4 recorded - as you stated - both patterns. Either I have missjugded my doing yesterday, because I thought I heard the voices playing different patterns, or the "recording" changes something.
 
If only one of Track 2 or 4 is recording, it reads both Cream outputs.
 
It doesn't matter what midi outpus the Creams use - I have tried variations but had allways the mix in the recording.
 
I will dig my nose deeper to this issue now. So stay tuned... ;)
 
Edit: The synths are two instances of Z3TA+ 2

swamptooth
arm the midi tracks that are going into kontakt to record, and record the input from cream.
any chance you can email me that test project?  i'll shoot you a message with my email address.

Next update - and I pray that you will not think I am going mad - guys it's weird ... really weird ...
 
Why, I have seen a ghost in Sonar - fumbling with the buttons.
 
After some unsuccessful experimenting with Sonar setups I recognized that my synths did not longer "listen" to the Creams? The mixer channel showed up with the keyboard to be the midi input - what???
 
I switched each track-input back to it's dedicated Cream output, disarmed - rearmed the recording for each synth track - did a recording - just to check - and - NO CROSSRECORDING - CLEAN TRACKS - UNBELIEVABLE :D
 
Well - this had to be checked and done again. So I deleted the recordings, and after rewinding to zero I hit the recording button. Result: Cross recording as before - okay - here we are again ... :(
 
But than I recognized, that my synth tracks again "listened" to the keyboard???
 
And this is very very weird. The button on the track/mixing channel showed clearly my keyboard as the input - but the check-symbol on the drop down, where you set the input channel, was set to Cream??? After switching the synths back to Cream again the tracks recorded without cross-over.
 
Could anybody be nice to try to repeat this and tell me that he also has a "ghost"? Otherwise I should consider a visit at the doctor ;)
 
EDIT:
 
Now I am very sure - it's a SONAR issue. Why, I played a little with my ghost.
 
First: If a synth track is armed for recording than the ghost switches the midi-input (as described above) if I delete the recorded midi content of this track. Delete --> Switch. If a synth track is not armed and the midi content is deleted, the ghost does nothing.
 
Second: Now, after recording at this state I get cross-over recording in the "switched track" and clean recording in the "unswitched" track.
 
Doesn't solve the problem, but should shade some light on it. At least we have a hint for a workaround...

SoundRaider,
 
The reason why this is unstable is that using more than one VST with Midi Out enabled can cause a deadlock in Sonar - so crashes and other weird behaviour happens, without it being 100% repeatable. I very much doubt you will be able to find a reliable work around - using more than one VST with midi out will always result in a crash at some point.
 
This issue has been around since Sonar 8.5, but has never been addressed. It seems basic Midi routing is just not a priority for Sonar.
 
Noel talked about the deadlock issue in post 42 on the thread in the link below, saying it was a known issue and would be addressed in the future. Given that we're now on X3b, guess he meant a very long time in the future..  
 
Edit: Link was removed, and not sure how to link to a post, add http:// to the below
forum.cakewalk.com/MIDI-Cross-Talk-fixed-m2260480.aspx

@soundraider - 
i had a duh moment last night about why cream was working well in kontakt.  i forgot that you need to specify the midi channel for each instrument in a kontakt plugin, which would act as a filter against the other instances of cream on other channels.  even though the midi tracks in sonar are picking up all the cream data from both instances, they are being filtered through kontakt's channel input options and not being heard.  silly me. *facepalm*

@ MattyBoy
I hope Sonar S/W engineers are watching this discussion.
 
When I played with the issue (post #46) the "switching" happended "each time that I deleted a midi track" of a Cream connected instrument. And each time there was the discrepancy between the mixer-channel input and the selection in the drop down menu - two different midi sources! I repeated the process several times before posting the result. It seems not to be accidental but - as you say - weird.
 
IMHO this points to a bug that is related to the software architecture itself. Why does a simple deletion of content have to switch midi-input setups if there is more than one midi-out plug in activated? It just doesn't make any sense from a functional perspective. Like smashing your room door and it starts raining outside :D
 
Reminds me of some kind of automatically processed "garbage collection" and resetting of parameters by a default initializing process, which is faulty.
 
After the automatic switching had happened I could reset the switching and there was no cross-over recording. This sayed, the "manual correction" is something like a "workaround" - but not suited for everyday practical use, of cause.
 
At least this behaviour should give the softies of Sonar something to think about ;) And Cakewalk - this issue is important. To have some instances of arps running in parallel is quite normal in electronc music, isn't it? So give this a high priority please!

@ swamptooth
 
did you receive the files? Yes - the trick with the Kontakt midi input filters took my some time also - but this was the reason that I mentioned it before in post #20. Sorry for not having pointed out this more obviously.