I think i will go make a peanut butter and jelly sandwich

I will go and make a shark sandwich.

CakeAlexS
I will go and make a shark sandwich.

never tried that in sandwich form.  hmmmmm

 
I must say, SilkTone, I'm pretty impressed by your perseverance.
 
I hope things are eventually resolved to your liking.  Please keep us informed of any progress you achieve.
 

Paul P
 
I must say, SilkTone, I'm pretty impressed by your perseverance.
 
I hope things are eventually resolved to your liking.  Please keep us informed of any progress you achieve.
 

+1

As Ryan indicated there were issues fixed with MIDI out. There was a well defined deadlock that *was* fixed in X3 as well as crashes related to MIDI out. So saying nothing was done in this area is grossly inaccurate.
There is a residual issue still on our radar with how MIDI echo is handled in combination with MIDI out VST's. I'm assuming that that is the residual problem that you still see and we will continue to investigate it.
 
 

maybe we're assuming that the process goes
bug identified/reported --> bug reproduced --> bug fixed
when there's actually one or more additional steps before "bug fixed "?

Having worked in software tech support for the last 16 years, I can only echo one aspect that Ryan stated above that wasn't done from the beginning with this one - each individual issue/symptom/workflow has to have a unique bug #.   When rolling similar scenarios into one report, the chances of resolving them all diminishes - right or wrong, that just tends to happen when dealing with a revolving list of issues to troubleshoot. 
 
But it sounds like the CW folks are at that point now and have the ability to better manage the data associated with each remaining aspect of "MIDI crosstalk".    That's a pretty big step forward IMHO. 
 

 
SilkTone, what I was referring to was that there were fixes checked into X3 and some users have reported seeing different results as a result of the checked in changes, making referencing past versions confusing given the case. Today's reality is different. I wasn't saying this to be rude or smart... it's just that SONAR X3 is not SONAR X2 or SONAR X1. 
 
Please understand that I wasn't saying "he said, she said" to be rude, nor was I saying "stories" to indicate you didn't know your facts. Perhaps I should have used a different word and I regret using that one now considering how much you've focused on it and how it could easily come across mistakenly, but you're putting other words in my mouth. If the tone of what I'm writing is being misunderstood then I'm truly sorry. You're focusing on my manner of speaking versus what I'm trying to communicate with you, which was written calmly with the hope that I could explain our process a bit so you could understand why things got to this point and why your reports came back the way they did. You were asking about the reports specifically, and I was providing clarification to what happened behind the scenes that caused them to be listed in our update notes.
 
My intention wasn't to argue with you, it was to tell you where I think we, Cakewalk, could have been more helpful with the reports in the first place. I was trying to explain for the sake of moving on to what would ultimately be more helpful for everyone. I think you're misreading my above post as argumentative or defensive whereas it was actually anything but. I was just trying to work with you on moving forward and getting more accurate info with the current version of the product. 
 
I think there are plenty of people reading along that could easily say at this point, "Hey Ryan, here's my experience with SONAR X3 and x,y,z plug-in, things look good" or "you know what Ryan, things look bad, I logged it in this case number, get this submitted to development please.". There are other folks who are doing this already and it is helpful. Thank you to anyone who has been doing this.

As Ryan  (and I said before that) the only real way to go is to log a new reproducible bug with Sonar X3C, and start from scratch avoiding the old baggage (it may just be a simple cut and paste affair with a few alterations). This issue was logged three years ago, the people who made the decision to close it then may not even work for Cake anymore or work in different departments, or maybe there was a completely different process.
 
Forget the past, deal with it and start from scratch. Get over the hump...
In the land of QA it can be extremely difficult to reopen issues, esp when it's down to internal politics, much easier to start a new one. I entirely understand the frustration but that has to be the clear way forward.