tlw

SilverBlueMedallion
 MIDI data recorded all over the place that shouldn't be, etc...
 

I don't have that problem.

Wonder what I'm doing wrong?

 
What are you doing wrong?  Almost certainly, you are not a heavy midi user.    Midi all over the place might be the single "feature" of Sonar since the X series.   
 
It's possible that much of it can be twisted to be user error:   Oh, you didn't notice that Sonar changes your selection range when you insert a new track?  That's user error.    Oh, you didn't notice that Sonar changes your selection range when you use Edit-Cut for a midi segment selected by time?   That's user error.      Just two of many causes, there are far more than these. 
 
But midi data all over the place is ALL OVER THE PLACE.   

I tried to respond to individual messages, got too many quotes in quotes.  
 
Simply:   Adam, you are not wrong.   (Nor are you entirely right -- some of your comments show a bit of ignorance "how things work" in Sonar)  
 
And the same gang of forum bullies treat your post just as they have treated some of mine over the years.   It's almost amusing to read the same thing from the same people; you'd think they kept canned replies ready.  
 
I don't know what to advise; I own and use SoundForge and Cubase and Samplitude and even a trial copy of Studio One, and have tried others too.   Like you, I have years of experience and habits which lead me to continue to use Sonar, though I've modified the flow so I rarely use it alone.   
 
For the 'new specialist in midi':  two things:   SELECTION CRITERIA and MIDI CHANNELS.    Sonor is so screwed up in these two areas of midi that it desperately needs help.    If you can manage to persuade the old guard that 'envelopes' should be restricted to audio, that might be a start. 

AdamGrossmanLG

kitekrazy1

bitman
If you are leaving, just leave. Don't stand there with the door half closed looking back saying "I'm leeeaaavvving" - does anybody (sniffle) care?
 
Seriously? With all the DAWs out there, just go make yourself happy. You can bad mouth us all from over there in their forum.
 

 I hate posts like this.  It's like "since you refuse to be part of our fanboy club get out".  It's so reminiscence of what this forum use to be and it's reputation was known to outside users. Ever heard "beat down Sonar style"? A phrase used some years ago in other forums.

totally agree. I posted this to hopefully get the bakers attention and for users to read.  Not to piss anyone off.

Its amazing how emotionally attached some people get to their DAW...as if I am insulting their mother's cooking.

But didn't you yourself say that you had contact via PMs with Cakewalk staff to resolve problems and yet you feel the need to create A post like this to get their attention. I don't understand. It seems a bit rude.

williamcopper
 
And the same gang of forum bullies treat your post just as they have treated some of mine over the years.   
 

Granted there are some very passionate defenders of Sonar here, but there are also those who lurk in the shadows just waiting for an opportunity to say something negative and then come out swinging. Which one is the bully is just a matter of opinion I guess:)
 
All in all this forum seems a pretty friendly place to me.

yep.  it IS always the same people who get butthurt over the fact that their favorite DAW is not someone else's favorite DAW.

To be honest, the only reason I am still using Sonar is because my projects I am working on are in Sonar plus right now, I don't feel like learning a new DAW.... but still MIDI issues persist.   

There's just so much wrong, and 'williamcopper' makes a great point....   everything is "user error".... I should just know that Cakewalk doesn't act intuitively with Sonar, right?  So when it doesn't, it is USER error!

Every project, eventually if I have enough MIDI tracks and things going on, eventually somewhere MIDI messages from one track is bleeding into another....    it should just WORK RIGHT!
 
An option to have the MIDI input actually set to NONE as default would be nice or to the keyboard controller of your choice... NOT MIDI OMNI as it starts to receive messages from say an instance of Kirnu Cream on it or notes from a softsynth with MIDI Out enabled.
 
That, along with patches after unfreeze not restoring properly, and a bunch of other things... really makes Sonar the worst in the market when it comes to MIDI implementation.

AdamGrossmanLG
An option to have the MIDI input actually set to NONE as default would be nice or to the keyboard controller of your choice... NOT MIDI OMNI as it starts to receive messages from say an instance of Kirnu Cream on it or notes from a softsynth with MIDI Out enabled.

I've been asking for this for years.  I've also recently discovered at least one other top tier DAW that fails to persist a setting of NONE for the input selection to MIDI tracks.  I really don't understand ...
 
Maybe with the recent changes to MIDI port handling, this will become possible.

I am a huge cakewalk Fanboy (no surprise there ).
Your comments don't bother me, nor do I feel like lashing out, being a bully.
My suggestions has (and always will) be the same... if your not happy, use something else.
I jumped ship once, but found myself back here because I realized the other DAW I was using was less reliable than Sonar.
 
I never saw this forum as a place to come air out my beef's with Sonar (Use twitter or Facebook for that )
I've always thought about this as a place to share ideas, learn new things and help others.
 
But you cant blame some for not wanting to hear your story broadcasted over the forum.
Imagine leaving a restaurant and saying "Im outta here cause the food isn't good".
Would you call others bully's because they might turn to you and say "Then leave".
 
you probably wouldn't. So a case can be made for those leaving dear John letters.
Just move on and be happy. .
If it makes you feel better to air it out than I hope it helped.
What ever you end up doing, make good music and be happy. Good luck and I mean that sincerely.
 
Chuck

MIDI is an antiquated 8-bit architecture that got revived by the power of VSTis. In even a 32-bit world, what exists at interface points (required) could be turned into a powerhouse inside any DAW, but not a lot has been done there. I would wager that most users play a small number of live instruments and the rest are VSTi. There is a vast frontier for innovation to host VSTis in a manner consistent with the architecture available.

Fair enough chuckebaby.  I understand and appreciate your point.  I guess I just feel like openness and honesty without filtering or being politically correct is the route I like to go.  I think forums are best served with PURE emotions, feelings, thoughts and ideas.   
 
I have a history on this forum and none of it is like what it is in this thread, this was my one-off and I felt it was OK to do so.  I certainly didn't expect the backlash.
 
Personally, you have always been helpful, infact I am a subscriber of your Youtube channel.  Good stuff on there, you taught me all about templates :)

I always appreciate the help on here and I try to help others when I can as well.

The point of this thread was to hopefully raise awareness to LONG RUNNING problems with Cakewalk's MIDI implementation.   If I made just another small post that dissapears in a day or two, it wouldn't even get any traction or any possibility of getting noticed.

This thread however is STILL going strong, so while I might have rustled a few feathers, I hope to MAYBE get the Baker's attention in regards to the MIDI implementation in this product.

I will say this... for AUDIO, Sonar I feel is one of the BEST products...  when working with audio (tracking, editing, mixing, etc...) Sonar is 2nd to none...  (and I expect it to even get better once ripple editing gets implemented), BUT for MIDI, it is still one of the worst.

I am just being honest.  That is the view from my horse anyway.

It seems like long standing issues are the hardest ones for the developers to sort out.