VSTi MIDI Output bug (specifically, crosstalk into other tracks)

As per Ryan's suggestion here, I'm creating a new thread for this bug to get some clarity around it. There is a lot of confusion whether it has been fixed in X3d, how to reproduce it, etc. I'm hoping it has been fixed in X3d but from other posts it seems like it might not have been.
  
To reproduce the bug with CW only products (no 3rd party plugins), I'm copying the same steps from this 4 year old thread:
 
Reproduce steps #1 - Using [external MIDI keyboard] - Omni: 

1. Important: For this test, ensure there is only one MIDI input driver enabled. Having more than one enabled somehow prevents these steps from reproducing the bug sometimes.
2. Start with a blank project.
3. Insert an instance of Beatscape.
   Note that Beatscape is not installed by default, and I don't believe it ships with X3, however it can be installed from one of the Sonar X1 DVDs.
4. Set Beatscape's MIDI input to "None" (bonus bug - sometimes this reverts back to "Omni").  
5. Go to the synth rack, right-click on Beatscape and select "Enable MIDI Output".  
6. Insert a new MIDI track.  
7. Set the new MIDI track's input to "[Name of my external MIDI keyboard]- Omni".  
8. Put the new MIDI track into record mode, and start recording.  
9. With the Beatscape editor open, randomly click on notes on the keyboard at the bottom of the Beatscape editor.
10. Stop recording.

 
You will notice that MIDI notes were recorded into the new MIDI track, even though its input is clearly set to specifically record from the external MIDI keyboard.
 
 
Reproduce steps #2 - Using [external MIDI keyboard] – Ch. 1: 

1. Start with a blank project.
2. Insert an instance of Beatscape.
3. Set Beatscape’s input to "[Name of my external MIDI keyboard]- Ch. 1".
4. Play notes on the external keyboard and while watching the Beatscape keyboard, make a mental note of where the "Pad Trigger" keys are located.  
5. Set Beatscape's MIDI input to "None" 
6. Go to the synth rack, right-click on Beatscape and select "Enable MIDI Output".  
7. Insert a new MIDI track.  
8. Set the new MIDI track's input to "[Name of my external MIDI keyboard]- Ch. 1".  
9. Put the new MIDI track into record mode, and start recording.  
10. On the external MIDI keyboard, press and hold a chord on the same keys that were noted in step 4 (do not release the chord until step 11 is completed).
11. With the Beatscape editor open, click on the corresponding notes on the keyboard at the bottom of the Beatscape editor.  
12. Stop recording.

 
You will notice that the notes recorded on the new MIDI track have been cut short as soon as the corresponding notes in Beatscape were pressed. According to the way the MIDI has been routed, this should not happen. This is just one way to repro this bug, there are many other scenarios where it prevents simple MIDI routing setups to work properly. Essentially any VSTi that sends MIDI output is useless in Sonar since there is almost always unwanted "crosstalk" between completely unrelated channels.
 
Reproduce steps #3 - Using a 3rd party plugin:

1. Download and install the demo version of Catanya from here.
2. Configure Catanya as described here. Choose "Setup in Sonar" from the bottom left menu.
3. Ensure you have a pattern playing in Catanya and that you can hear the softsynth it is driving.
4. Create a new MIDI track and set it up to record from an external MIDI keyboard. Set MIDI input to "[Name of my external MIDI keyboard]- Omni".
5. Arm the MIDI track from step 4 and start recording.
6. Notice that the MIDI track is also recording the MIDI events from Catanya.
7. Change the input to "[Name of my external MIDI keyboard]- Ch 1".
8. Record again on the MIDI track from the external MIDI keyboard.
9. This time note that as soon as Catanya plays the same MIDI note as what is being played in from the MIDI keyboard, that note from the MIDI keyboard will be cut short.

 
So even after specifically selecting only channel 1 from only the MIDI keyboard's port, the MIDI events from Catanya is still able to interfere with the MIDI keyboard events.
 
Clarification #1:
Some people seem to believe that the "Enable MIDI Output" functionality means the MIDI events from the VSTi is then sent from Sonar out to the MIDI driver. This is not the case, instead the VSTi's generated events simply becomes available as an input to other tracks/plugins within the DAW.  The VST spec defines this functionality so that you can create plugins like ARPs etc that can drive other softsynths. Another example of this functionality is using a plugin like Jamstix to drive another drum softsynth if you prefer the sounds from a different drum module. So it is very basic MIDI routing from one plugin to another. There is nothing "bizarre" or "obscure" about doing this. It simply means you are using the part of the VST spec that enables this type of functionality. If this functionality is broken, the many ARP type plugins like Catanya can't work properly.
 
Clarification #2:
The original MIDI spec defined only 16 MIDI channels. That isn't nearly enough for a DAW, so the concept of a port was created. A MIDI port is an isolated bundle of 16 MIDI channels. Channel 1 in port A is not the same as channel 1 in port B. Just like the left audio channel in track 1 of an analog mixer is not the same as the left channel of track 2. Sending audio into the left channel of track 1 doesn't mean the left channel in track 2 will see the same signal. There should be no crosstalk. In addition, port A Omni means all 16 channels in port A only, not any other channels from any other port.
 
Clarification #3:
In Sonar when you select [external MIDI keyboard name] - Omni, it means that you want all 16 channels from that external MIDI keyboard, it doesn't mean all MIDI events floating around inside Sonar. Don't confuse this with Sonar's "confidence recording" feature. The MIDI events are permanently recorded onto the wrong track as shown in the steps.

No please don't cross reference - arghhhh!!!!!
 
(there goes my thread hijacked!   )

Yes please, and quote what he said here if you want, just trying to stop that thread turning into a MIDI discussion thread but I fear it is too late... Cheers.

Thanks for working so hard on getting this resolved, the results look promising.

Once this is all verified as fixed I'll gladly pay for the x3 upgrade. I'm on x2 currently.

What a great Christmas present!

I also followed your steps and I say #1 and #2 is fixed.
 
Another issue I came up with is that Beatscape kept disappearing, in some instances wouldn't actually move if I dragged it. I don't know if this is the Beatscape plugin itself or bitbridge. Does anybody else get this?
 
I didn't test #3
 
Cheers...
 
p.s.
 
I know what you mean, why is None and Omni treated the same? Anybody care to tell me why?

The Beatscape sounds are now the Loops and One Shots, if I got that right.
 
I don't know any more about Beatscape than that (which I hope is right)
 
Bob Bone
 

> why is None and Omni treated the same? Anybody care to tell me why?
 
Anyone?
 
Or is it a mystery? Cheers..