Just in case any of this is useful:
http://global.novationmusic.com/support/product-downloads?product=Launchkey
 
And Presonus :
http://www.presonus.com/products/StudioLive-24.4.2/downloads
 

Thank you for your help. The Novation link wont open, and Presonus- I do not see any firmware- mostly PDF manuals... They probably already discontinue my model.

Sorry edited previous post.. Probably not much use anyway but just in case..

dcumpian
This sounds more like input echo was enabled on the Kontakt track while the AD track was selected. Just toggle it off.
 
I use the same basic setup as you and this never happens to me.
 
Regards,
Dan

HA! This post just solved something that was confusing me quite literally a couple hours ago. I had inserted Zeta and when messing around with the virtual keys to try out patches it was triggering the instance of AD in the project. I thought maybe I had just screwed up some MIDI channel weirdness (which still confuses me but I'm starting to get it) but after reading this post I remembered yesterday that I had activated the MIDI Echo on the AD track to play around with some live input. Just turned it off and now AD is keeping its filthy mouth shut when Zeta is talking. lol
 
Thanks.

 
 

vladasyn
Dcumpian, thank you for the input. This is obviously what first comes in mind. Midi echo is definitely involved in to an issue but on deeper level than you describing.
 
Yes, Input echo on Kontact MIDI track was enabled. I may not understand midi echo, but to me- it has to be enabled to be able to make any sound. It is always enabled on selected track and if MIDI track assigned output to Kontact, it should trigger Kontact, and not Addictive Drums (AD). I do not go and unselect each tracks MIDI echo every time. The way Sonar used to work was that MIDI echo would get itself on when track is selected. Not sure if this function is still there.
 
You saying- "input echo was enabled on the Kontakt track while the AD track was selected."
 
No. Input echo was enabled on Kontact midi track, and Kontact midi track was selected, and it was playing sound from Kontact and AD at the same time. It was supposed to play Kontact only. How does it get an idea to play AD, and not several other plugins that were available I dont know. I also had to disable NORA arpeggiator because that thing was sending MIDI notes in to Kontact. Do not ask me why Kontact and not AD.
 
In the MIDI options on the synth rack view (what ever it is called- on the right side of the screen), there is an option saying, "Force MIDI input through..." or something in this nature. It was checked when issue was happening. So I unchecked it and it did not change anything. The input echo on each track was impossible to disable. It would only stay lit blue or lit blue with "A" on it. What does it mean, by the way? The point is- it would not let me turn echo off by pressing on it. So this is when I restarted Sonar (not computer). When it loaded back project, midi echo buttons were not active. I assume that is because I unchecked it in the options previous session that I had to restart. Conclusion: this "Force midi something" option requires Sonar restart to change its settings. When it selected, everything goes anywhere it wants. Input echo is impossible to disable. So I can say that it is reproducible- I have to try it at another time. I am not convinced that this is an issue or that it is the only issue.
 
 

Then it may be one of the setting that you are enabling when you launch a new VST instance. I'll be the first to say that the dialog for this is not an easy read. Definitely isn't normal.
 
I always add new VST's directly into the synth rack, then add midi tracks that point to the VST manually. I know it can all be automated, but I want to know what's going on. Call me old-fashioned.
 
Regards,
Dan
 
 

I have had the same problem very frequently in X3, input echo on  on the track I am recording and off on AD2 but still playing the drums. I am able to stop it by setting the track being recorded to a midi channel instead of Omni. I am not saying that is a solution for you ,just saying that I have had a very similar problem for a while. If I remember correctly the same thing happens with Session Drummer 3. Have not had a chance to check it out in Platinum yet.
 

vladasyn
The input echo on each track was impossible to disable. It would only stay lit blue or lit blue with "A" on it. What does it mean, by the way?
 

See "Always Echo Current MIDI Track" in preferences; it's enabled by default. The A is for Auto. If the track has focus, you will be toggling between Auto-Echo and (forced) Echo On. If you move the focus to another track, you can click the Echo button on a track that doesn't have focus, and it will turn off.

brundlefly

vladasyn
The input echo on each track was impossible to disable. It would only stay lit blue or lit blue with "A" on it. What does it mean, by the way?
 

See "Always Echo Current MIDI Track" in preferences; it's enabled by default. The A is for Auto. If the track has focus, you will be toggling between Auto-Echo and (forced) Echo On. If you move the focus to another track, you can click the Echo button on a track that doesn't have focus, and it will turn off.

That's what it was? I LOVE IT!  

vladasynNo. Input echo was enabled on Kontact midi track, and Kontact midi track was selected, and it was playing sound from Kontact and AD at the same time. It was supposed to play Kontact only. How does it get an idea to play AD, and not several other plugins that were available I dont know. I also had to disable NORA arpeggiator because that thing was sending MIDI notes in to Kontact. Do not ask me why Kontact and not AD.

 
To clarify... If you rely on the MIDI output of one VST being fed into the MIDI input of another track, you have to toggle the MIDI track's echo button to stay permanently selected. If you don't, the MIDI will stop playing once you select another track.
 
And once again, this is the bug you most likely ran into, and is a leftover bug from when Noel mostly fixed the MIDI crosstalk bug and the crash when using more than one VST sending MIDI out. You just happened to initiate the "workaround" mentioned in that thread when you restarted Sonar.
 
Below are the steps to reproduce the issue. It should be obvious that it is incorrect behavior.
 

1. Start with a blank Sonar project.
2. Drag n Drop an instance of Jamstix. Make sure the "Enable MIDI Output" option is checked.
3. In the Jamstix wizard, click on "Create Song".
4. In Jamstix, go to Options and check the "Enable MIDI Output" option.
5. Go back to Sonar and Drag n Drop any synth, like SI-String Section or similar, making sure to select MIDI Source and First Synth Output, not Simple Instrument Track.
6. On the synth MIDI track, change the input to [your MIDI keyboard] Omni.
7. Put the synth track in record mode, start recording.
8. Record a few bars while Jamstix plays drum notes, then stop recording.
9. Notice the MIDI events from Jamstix on the synth track.
10. On the synth MIDI track, change the input to None, and then back to [your MIDI keyboard] Omni.
11. Delete the previously recorded clip on the synth track.
12. Put the synth track in record mode, start recording.
13. Record a few bars while Jamstix plays, then stop recording.
14. Notice this time that there are no longer Jamstix MIDI events recorded on the synth MIDI track.

SilkTone
And once again, this is the bug you most likely ran into, and is a leftover bug from when Noel mostly fixed the MIDI crosstalk bug and the crash when using more than one VST sending MIDI out.

Hi, Silktone. I'm not so sure that issue is applicable here. The problem there is that a track receives/records input from a virtual MIDI Out that is not selected as Input.
 
In this case, a track is reportedly echoing MIDI to its Output when it shouldn't be. There was no indication of a problem with the input assignment. Even if it was somehow receiving MIDI from Kontakt (which the OP indicated did not have MIDI Out enabled in the synth rack), it shouldn't have been echoed to AD if Input Echo was not enabled.
 
In summary, this was an Output problem not an Input problem. It's possible the OP encountered some other bug I haven't seen, but I don't see how it could be the bug you've referenced, though I've confirmed that bug persists in Platinum.