Or Self Feeding Infinite Midi Loop Death Spiral   (SFIMLDS)
 
This may be caused by some type of persistence issue where Sonar is not keeping midi inputs locked on channels and devices selected and making everything all - OMNI ???
 
I continue to play with this but I see exactly the same thing that Arachnaut sees.
 
JR

Hi
I use Twistedtools Colorflex in Reaktor.
Colorflex has eight midi channel.
Colorflex triggers softsynth(Kontakt,massive etc) at the same time.
In playback,no problem.
When I record midi, a signal of all midi channnel becomes mixed-up on one truck.
In X3, it does not change either.

I will see if I can recreate this evening and see what could be the problem.
 
JR

Wow that Colorflex is quite the sequencer AO !  Very Powerful and lots of potential.
 
Unfortunately the demo only ran for 10 minutes and then stopped.  Usually you can close the project and get another 10 minutes, but this demo just stopped and never worked again.  At least I assume that is the demo limitation, I could find no information about the demo limitations on the web page or with google.  
 
 If it was 20 $ I would buy, but 50 $ is a little steep right at the moment.
 
JR

Yes is a very old issue that some of us have been struggling with for a long time. Many users on this forum are probably sick of this issue and of me complaining about it (especially those that don't understand the issue or the severity of this bug).  But now that this issue is finally getting more attention, I think giving some history of this bug is appropriate.
 
I actually noticed this issue more than 5 years ago when I was using various plugins that sent out MIDI (crashes, dropped/stuck notes, MIDI crosstalk etc). I always wrote it off as buggy plugins, but when I started developing some of my own plugins I started realizing that there is something wrong with Sonar's MIDI implementation. So to repost a brief summary of what I did (sorry for the repost from another thread, but I was told this thread is more appropriate):
 

• CWBRN-1336 -Multiple MIDI bugs, all related to VSTi MIDI output (filed on 02/24/2009)
• CWBRN-2504 - Bugs related to the "Enable MIDI Output" functionality (this refers back to 1336 and gives additional info on how to reproduce it)
• CWBRN-2534 - Can't record from two MIDI keyboards at the same time 
• CWBRN-2533 - MIDI notes cut short when a different source sends notes
• Created a web page in Feb 2009 that details clear steps, including:
  • A VSTi that reproduces the issue, including source code
  • A Sonar project used to reproduce it
  • Very clear steps on how to reproduce it
• A very long email discussion with Willey Jones regarding this issue where I provide great detail on reproducing it. All I got back was empty promises that it will be fixed.
• Endless threads about this issue, usually met with arguments how this really isn't a bug, just user error. See here, here, here, here. There are more.

 
One of the things that really ticked me off is how difficult and futile it was to work with CW support. As an example, asking for an update 2.5 years after filing CWBRN-1336, I get this response back:
 

Thank you for contacting Cakewalk Technical Support. Sorry for the delay in getting back to you. We were unable to create the issue with the steps provided.
 
Please submit this issue to our problem reporter within the link below... 
http://www.cakewalk.com/Support/ProblemReporter/
 
Some things to remember... 
1. Provide your instructions starting with a blank SONAR project. 
2. Please only use/reference plugins that are included with SONAR (no 3rd party plug referenced please). 
3. Include every step, even the ones you'd think to be obvious (there are many ways to get to the same results, I'd like to make sure we're both following the same workflow).
 
Thank you for choosing Cakewalk! 
Best Regards,

 
Hey OK those are great tips! I'll make sure to remember those things when filing the error report!!! Again
 
And then people wonder why I got so upset about this issue. This bug has been a complete showstopper for me in my workflow, which is why I eventually just gave up and switched to another DAW.
 
To Ryan... I'm seeing conflicting reports from various people whether this issue has been fixed in X3c. Can you confirm either way? As I said I got off the bus during the X1 bugfest days and have been out of the loop ever since then. Given the bad experience I've had with CW and Sonar, I find it hard justifying putting down yet more money to get something that should have been fixed over 4 years ago.

Ryan (or someone else from CW), can you confirm whether this issue has been completely fixed in X3c? As I said I can't tell from the various conflicting reports from other users whether this has been completely fixed in X3c or not.

Hey st,

No - not completely fixed. I see that my video comparison of reaktor midi outs in sonar and studio one has been reposted in a couple of these threads and that behavior still exists in x3c.

swamptooth
Hey st,

No - not completely fixed. I see that my video comparison of reaktor midi outs in sonar and studio one has been reposted in a couple of these threads and that behavior still exists in x3c.

Thanks for the update. Good thing I wasn't duped into paying for yet another upgrade just to find out Sonar is still incapable of doing basic MIDI routing. I don't understand how CW can call this thing a "professional" DAW.
 
Sorry for the negativity, but if you've been banging your head for almost 5 years trying to get CW to take notice of this issue, anyone will start having a headache after a few years. I also used to be bright-eyed and bushy-tailed about Sonar just like many of the members here, until this issue cropped up and I realized dealing with CW is like talking to a brick wall.
 
But once again, thanks for the confirmation.

I use multiple daws as well. Sonar is my main one though because it does most things very quickly intuitively and efficiently. If i want cv routing i use reason or rewire it into sonar. If i need to search for samples (setting up the metadata for their media bay takes forever but is very worth it) or do synth midi generation like in this post or use release velocities or vst note expression i use cubase.
Scoring is sibelius. Algorithms = pure data.
I do the majority of my work in x3 though. It has crashed less on me than cubase 7 as well. And no 64 bit video support in studio one was a deal breaker so i didn't take long removing them from my short list. Different tools for different jobs.
Considering craig anderton said he'd never really taken a deep look at midi out from vsts and now might play with it a bit i think is a great step in the right direction. It took me by surprise that he hadn't played with this, but i think he'll see its usefulness and become an advocate in the future.

OK I need some clarification on this issue from CW. In this thread, Ryan writes:
 

Yesterday I closed out a CWBRN[-1336] as "fixed" which notified you of it. Our Dev and QA team returned this as fixed as part of the X3b and X3c updates, I was just behind with closing out the CWBRN report.

 
But we have confirmation from swamptooth above that it isn't fixed in X3c. So which is it now? I realize CW wants this thread to die off but I'm going to keep bumping it until CW gives a clear status on whether CWBRN-1336 has been fixed in X3c or not.