Been a lot of traffic on these issues lately so I thought I would provide a separate summary to help out:
As a disclaimer - "enable midi out" here is being used only on Vsti plug ins that self generate their own midi data. There is no keyboard or any other hardware device needed to create midi data. Such VSTi are Catanya, Harmonizer, Reaktor (there a bunch of different Arps in the suite), Jamstix, (and many others). While you can turn enable midi out on any VSTi, that does not mean there will be any midi actually coming out (Dimension Pro, rapture, etc.) and therefore in these cases you would not see any issue either (unless you are trying to chain a bunch of synths together see issue 3) It should be noted that other DAWs do not have these issues and that has fueled a certain amount of heat. Also, every one of these below has a tech support case or multiple tech support cases already opened. Finally, none of these issues below trigger cakewalk problem reporter so there is nothing to send in which I think has caused some churn as well.
1) Midi X-Talk - (Basically Sonar was not keeping midi data output from the vsti's separate and was mixing it all together) this was diagnosed and reproduced in Sonar X1 and X2 (there is a youtube video showing this). Supposed to have been fixed in X3c.
And.....I think it has been fixed....Yay ! At first it looked like it had not been fixed, i think that is because I was using old projects created before X3c. Last night I started brand new test projects and inserted 3 instances of Jamstix and 1 instance of Catanya. Jamstix was triggering Battery, EZ Drummer, Addictive Drums. Catanya was triggering both Rapture and Dimension Pro. It played perfectly. And when I recorded midi on the soft synth simple instrument tracks, the midi recorded was
only the midi output supplied by the correct Jamstix and Catanya midi in. The recorded midi was not a jumbled up mix of all the midi VSTis together. So it looks like the issue is fixed, but you may have to delete all the vsti's from old projects and re-insert. Also not sure if an older vsti track template will bring the issue back with or not either, but I will try to confirm. So this is encouraging and will continue to check it out.
2) eMOFO (enable midi out freeze occurance) - this is an issue where having multiple instances of catanya or reaktor triggering a softsynth freezes Sonar to the point that you have to restart your PC. (even using task manager you cannot stop Sonarprd process) Again search the forums for this issue. Interesting thing I have noticed....Catanya and Reaktor still cause this issue in X3c. However Jamstix, which is functionally the same idea ( I think ?), does not crash Sonar X3c when you have more than 1 instance running. Last night I had 3 instances of Jamstix triggering 3 drum synths (as noted above) and 1 instance of Catanya. Stopped and started it numerous times, changed patches on the fly no issues. However, as soon as I added a second instance of Catanya, Sonar crashed hard. Maybe this is a clue as to why this happens, what does Jamstix do differently than Catanya or Reaktor when it is outputting midi data ? Maybe it is not important ? Don't know. Users have shown that other DAWs can handle unlimited instances and run no problems.
3) Enable Midi out as midi through put - This was only raised yesterday. I have no experience with this, but a user was expecting that you could daisy chain multiple vsti soft synths together using enable midi out. I confirmed that things do not work that way, but I do not know if that is a bug or designed that way or the vsti themselves that do support this. Definitely Dim Pro and Rapture do not do this. I was able to confirm that a single plug like catanya can trigger mulitple synths. And of course, you can have a single hardware device trigger multiple devices, but that is not what the user was looking to do. (at least this is how I understood things...) Again, looks like other DAWs do this but not Sonar.
Fixing 1 is great, looking to see what happens with 2 and 3.
Hope this helps....