So new midi data is appearing in a midi track that does not have Record armed?  Am I understanding this to be what is being reported?
 
I get phantom midi data transmitted by one of my midi controllers, but that seems to be due to an internal hardware issue related to crappy pots and such.  I have never seen midi data recorded on a track that was not armed for record.
 
Bob Bone
 

robert_e_bone
So new midi data is appearing in a midi track that does not have Record armed?  Am I understanding this to be what is being reported?
 

Bob,
  No, the MIDI data is appearing on a Record armed track.  The issue is that the MIDI data is being received from another track that is not routed to it in addition to any data that is received through the Record armed track's input port.
 
-- Ron

Thanks to everyone that confirmed the bug (and those that tried to repro it).
 
So maybe CW doesn't know about this because their test machines would usually have more than 1 MIDI input device (speculating). We have a few confirmations now that it only reproduces when there is just 1 MIDI input device.
 
The behavior that Bill mentions in post #45 is really weird. I have not seen that, but with Sonar getting its wires crossed I can't say it surprises me too much.

I recall from previous discussions that having only one external MIDI input was part of the recipe. I can repro in that special case as well.

Thanks for explaining - I am a little slow towards the part of the day that my eyes are open. :)
 
So, what is the result if you alter the midi track that is armed for recording, so that it only accepts input from the desired input midi controller?  Wouldn't that take care of whatever is happening?
 
Is it due to the enable midi out being checked?
 
Does this happen for regular midi tracks, or is it just occurring with simple instrument tracks?
 
Thanks - sorry I am being so dense thus far.
 
Bob Bone

 

robert_e_bone
Thanks for explaining - I am a little slow towards the part of the day that my eyes are open. :)
 
So, what is the result if you alter the midi track that is armed for recording, so that it only accepts input from the desired input midi controller?  Wouldn't that take care of whatever is happening?

 
Well, if you selected:
 
[My external MIDI controller]->Ch. 1-16
This will work as expected, and would record only from your external MIDI controller on the selected channel.
 
[My external MIDI controller]->OMNI
Here you would be recording not just all 16 channels from your controller, but also MIDI from any VSTi that happens to send MIDI out. And also from the Virtual Controller if you happen to click on any of its notes.
 
So to answer your question... It depends on whether you select a specific channel, or OMNI. In this context OMNI is supposed to mean only the 16 channels from that selected controller, nothing else.
  

Is it due to the enable midi out being checked?

 
By checking enable MIDI out, you complete some imaginary signal path that somehow connects back into the input of tracks where it doesn't belong. So if no VSTi has enable MIDI out checked, and you don't have the Virtual Controller onscreen, then you cannot reproduce the bug since this imaginary signal path doesn't get completed.
 

Does this happen for regular midi tracks, or is it just occurring with simple instrument tracks?

 
I just tested with a simple instrument track and it also reproduces, so yes, it happens with both.
 

Thanks - sorry I am being so dense thus far.
 
Bob Bone

 
NP, it would probably be a good idea to make a video of it one day since it tends to be a little bit confusing.
 
...
 

brundlefly
I recall from previous discussions that having only one external MIDI input was part of the recipe. I can repro in that special case as well.

 
Yes I thought that rang a bell but it was some time ago. Kind of a strange requirement to have just one external MIDI input in order to repro a bug. I don't quite get the connection.

Sorry to bring up an old thread, but this whole crosstalk issue continues to plague me since I regularly use plugins that generate MIDI. Is anyone else still suffering from crosstalk blues? 

recent midi threads that maybe related? good luck!
http://forum.cakewalk.com/Adding-Instrument-with-MIDI-output-m3546620.aspx
http://forum.cakewalk.com/Is-There-Anyway-To-Disable-Enable-MIDI-Out-When-Inserting-Softsynths-m3539913.aspx
 

I think one answer was to avoid leaving any midi track inputs set to Omni, except those you want to listen.
 
Apparently NONE defaults to Omni, so set MIDI track inputs to Virtual Controller, or something, unless you are actually using them.

pwalpwal
recent midi threads that maybe related? good luck!
http://forum.cakewalk.com/Adding-Instrument-with-MIDI-output-m3546620.aspx
http://forum.cakewalk.com/Is-There-Anyway-To-Disable-Enable-MIDI-Out-When-Inserting-Softsynths-m3539913.aspx
 

They are related, although not directly. There are some other issue associated with the problem I'm having which are outlined in those threads, like the whole MIDI omni frustration and the fact that MIDI out is enabled by default on plugins which offer it.