SilkTone
Important:
If you flubbed any of the steps, say accidentally select the wrong input in step 5, then changed that to the correct input, the problem will not reproduce. This is actually the workaround as well... Select an unrelated input, then back again to [Your External MIDI Controller]->OMNI.

I'll have to go hunt up the earlier thread on this where toggling the input assignment would fix the problem. As I recall, I was only able to repro the issue if I had Always Echo enabled in preferences, so that upon inserting tracks they would automatically default to 'Omni' which is actually All Inputs - Omni, but shows as 'None' in the dropdown.
 
But now, I'm unable to reproduce it with those exact steps no matter the state of 'Always Echo'.
 
EDIT: There have been so many of these threads over time with all sorts of side issues and confusion going on in them that I can't immediately find the particular one was thinking of. I did find one in which I mentioned being able to reproduce this in Platinum, but that was probably before Kingston which supposedly fixed this 'once and for all'. All I know is that I cannot currently reproduce any crosstalk issues in Manchester other than false 'confidence recording' indication on the armed track.
 
 

brundlefly
 
I'll have to go hunt up the earlier thread on this where toggling the input assignment would fix the problem. As I recall, I was only able to repro the issue if I had Always Echo enabled in preferences, so that upon inserting tracks they would automatically default to 'Omni' which is actually All Inputs - Omni, but shows as 'None' in the dropdown.
 
But now, I'm unable to reproduce it with those exact steps no matter the state of 'Always Echo'.
 
EDIT: There have been so many of these threads over time with all sorts of side issues and confusion going on in them that I can't immediately find the particular one was thinking of. I did find one in which I mentioned being able to reproduce this in Platinum, but that was probably before Kingston which supposedly fixed this 'once and for all'. All I know is that I cannot currently reproduce any crosstalk issues in Manchester other than false 'confidence recording' indication on the armed track.
 

I submitted a problem report [CWBRN-33360] for the MIDI crosstalk issue in Platinum back in June of 2015 and created forum thread: http://forum.cakewalk.com/FindPost/3231310.  My thread referenced an earlier thread created by @SilkTone from December of 2013 that discussed the Sonar X3 workaround: http://forum.cakewalk.com/FindPost/2954622.
 
Z3TA+ 2 that was used in my problem report no longer transmits MIDI in Platinum "Manchester".  The Synth Rack displays "Enable MIDI Out" as "greyed out" for Z3ta+ 2, so it is no longer possible to use my original Steps to Reproduce.
 
I tested using the free Kirnu arpeggiator and the original Z3ta+.  In both cases I also can no longer reproduce the problem in Platinum "Manchester" when setting the input for the recorded track to my external MIDI port (Gina 3G MIDI Omni).   The only way I can reproduce is to set the input to "All Inputs MIDI Omni" for the recorded MIDI track and this would be expected behavior.
 
Re: Cakewalk plugin that transmits MIDI Data
The older Z3ta+ will transmit MIDI when clicking on the gray bar at the bottom of the Z3ta+ GUI.
 
 
 
-- Ron

Thanks to everyone looking into this. It looks like there were some more fixes made in this area since fewer people can now repro it. I can definitely still repro it 100% of the time following the steps from my previous post.
 
It might be that CW thought the last remaining bugs in this area were fixed because they could no longer repro it, but maybe based on your setup, it could still repro in some cases.
 
It is interesting to me that in my steps above, there is no VSTi sending MIDI out. Only Virtual Controller is sending MIDI out, so I'm guessing maybe it is using some of the same code paths that a VSTi would use when it sends MIDI out. Of course I don't know for sure but in that regard the bug is exactly the same for me whether it is a VSTi or the virtual keyboard.
 
Ron, I know that in the past if I had multiple MIDI drivers enabled in Sonar, the problem would not reproduce. If you go to Preferences->MIDI->Devices, how many MIDI inputs do you have selected?
 
I also checked out Z3Ta+, and it does play back when clicking on the bottom gray bar. But as you said, it doesn't send MIDI notes out, only audio. I did verify that it's Enable MIDI Output is checked, and even though I can select it as an input to another MIDI track, it never seems to actually send any MIDI events.
 
So far the easiest way to repro it for me using only CW supplied software is to use Virtual Controller, even though strictly speaking it isn't a VSTi. But for me at least it seems to hit the same bug. Maybe the bug is in the input of a MIDI track as it deals with MIDI coming from somewhere inside Sonar as opposed to being in the output of a VSTi.

sharke
A little OT but I still don't understand why "none" doesn't just mean "none."

Exactly.  A major gripe of mine.  Does this honestly need to be put into a Feature Request to resolve this once and for all?
 
EDIT: Per Brundlefly's comment, I've always had difficulty with the "None" issue.  Perhaps I am doing it wrong, but it never seems to stick (i.e. remain on "none") and/or refrain from receiving MIDI and thereby triggering whatever the track's output is.

When I followed silktone's steps of post #40, I got a very bizarre result that doesn't quite fit into any of the descriptions so far. I inadvertently did things a little differently: I had a timeline loop enabled, and when I stopped recording, I did it by clicking the control bar's record button, not 'stop'. So Sonar kept playing around the loop.
 

1. As I recorded, I saw a clip shadow being animated in the midi track of step 4, but no notes (this is the known "confidence recording" bug?). I heard no notes from anywhere.
2. After I stopped recording by clicking the record button, Sonar continued to play, looping around. As it replayed the loop, the SI Strings synth of step 4 played the notes I had recorded. <-- This is weird
3. The 'confidence recording' shading was still there with no notes.
4. When I finally clicked 'stop' the confidence recording shading disappeared.
5. Clicking play again played no notes.
6. The transport controls were not working the same any more. Hitting 'play' forced the NOW time back to measure one. 'Stop' restored the NOW time to wherever it was when I hit 'play'. This condition is persistent.

Item 2 is the really weird one, and acts just like midi crosstalk, but it goes away after 'stop'. Item 6 is weird, and not part of the discussion at hand, but seems to coincide with finishing (my version of) silktone's steps.
 
Are there some preference settings that differ among the people trying these steps that could explain the variety of results?

bvideo
After I stopped recording by clicking the record button, Sonar continued to play, looping around. As it replayed the loop, the SI Strings synth of step 4 played the notes I had recorded. <-- This is weird

I reported this against X3, and I believe it was explicitly reported fixed in Kingston. If it's back, it has to do with focus being on the track that should not be recording (or echoing) that input. And, as you observed, it only happens when loop recording.
 
EDIT: My original report was that it happened on a track that was not even armed to record in addition to having an input assigned that did not match the port on which MIDI events were arriving. That issue remains fixed. BUT, if the track is armed, it still happens.

SquireBum
Z3TA+ 2 that was used in my problem report no longer transmits MIDI in Platinum "Manchester".  The Synth Rack displays "Enable MIDI Out" as "greyed out" for Z3ta+ 2, so it is no longer possible to use my original Steps to Reproduce.

 
I don't why our systems differ, but the "Enable MIDI Out" box is not grayed out on my z3ta+2 (v2.2.2) properties page.  I didn't know that z3ta+2 ever transmitted midi data.
 

SilkTone
Ron, I know that in the past if I had multiple MIDI drivers enabled in Sonar, the problem would not reproduce. If you go to Preferences->MIDI->Devices, how many MIDI inputs do you have selected?

 
Steven,
  I had 2 MIDI input devices currently enabled when I tested:
    Gina3G MIDI
    LoopBe Internal MIDI
 
Tried the following:
1.  Disabled LoopBe Internal MIDI leaving only Gina3G MIDI.
2.  Inserted Simple Instrument Track (Track #1) with the free Kirnu arpeggiator, checked "MIDI Output enabled", input set to None.
3.  Added a MIDI clip with 3 measures of chords to Track #1
3.  Inserted Simple Instrument Track (Track #2) with Dimension Pro, input set to Kirnu 1 MIDI Omni.
4.  Inserted Simple Instrument Track (Track #3) with Z3TA+2, input set to Gina3G MIDI Omni.
5.  Input monitoring disabled on all tracks.
6.  Enabled record on Track #3 only.
7.  Clicked Record and stopped after 4 bars.
 
Result:  Track #3 contains MIDI data corresponding to the MIDI output of the Kirnu arpeggiator from Track #1.
 
This confirms your conclusions about the multiple input devices.
 
If I toggle the Track #3 track input to "None" and back to "Gina3G MIDI Omni" and hit Record again, arpeggiator data is NOT recorded.  This is the Sonar X3 workaround that was previously described.
 
-- Ron
 
 

Paul P

SquireBum
Z3TA+ 2 that was used in my problem report no longer transmits MIDI in Platinum "Manchester".  The Synth Rack displays "Enable MIDI Out" as "greyed out" for Z3ta+ 2, so it is no longer possible to use my original Steps to Reproduce.

 
I don't why our systems differ, but the "Enable MIDI Out" box is not grayed out on my z3ta+2 (v2.2.2) properties page.  I didn't know that z3ta+2 ever transmitted midi data.
 

Paul,
  The "Enable MIDI Out" checkbox is not greyed out on the properties page.   The Enable MIDI Out option under Synth Connected  is greyed out in the Synth Rack drop down menu for Z3TA+2 (v2.2.2) on my system.
 
-- Ron

SquireBum
I had 2 MIDI input devices currently enabled when I tested:
    Gina3G MIDI
    LoopBe Internal MIDI

 
I just repeated Ron's setup except I started with a single device : LoopBe30 for which I enabled only Port 1.
 
Data was indeed erroneously recorded in track 3.
 
Now, instead of toggling track 3's input I (only) enabled LoopBe30 Port 2 in Preferences.
 
This also fixed the problem, no data is recorded in track 3.
 
Next, I (only) disabled LoopBe Port 2 in Preferences.
 
Data is again erroneously recorded in track 3.
 
 
[Ron, I see what you mean wrt Enable MIDI Out.  Thanks.]