SilverBlueMedallion
What is that "Enable MIDI Output" option there for, when you see it doesn't do ANYTHING!
 
I can't actually believe after looking at my 4 steps you are still saying this is by design!!  The checkmark actually DOES NOT DO ANYTHING!!!  IT - IS - BROKEN!

How is that by design?  What you are saying makes no sense now.... just anything to make this not look like a Sonar issue.  Unbelievable.

What's unbelievable is that you blame me because you don't understand what a default is, what overriding a default is, what creates defaults, what a specification is, don't pursue links I provide that back up what I say, and then cross-post in other threads making idiotic accusations but never update the errors you make with correct information.
 
When I'm wrong, I have the decency to say so and give credit where credit is due because my concern is disseminating correct information. Apparently you have different priorities.
 
At this point, I honestly don't know if you truly don't understand, or whether your're willfully ignorant.
 
Please, turn the thread title from a threat to a promise. 

Anderton

SilverBlueMedallion
What is that "Enable MIDI Output" option there for, when you see it doesn't do ANYTHING!
 
I can't actually believe after looking at my 4 steps you are still saying this is by design!!  The checkmark actually DOES NOT DO ANYTHING!!!  IT - IS - BROKEN!

How is that by design?  What you are saying makes no sense now.... just anything to make this not look like a Sonar issue.  Unbelievable.

What's unbelievable is that you blame me because you don't understand what a default is, what overriding a default is, what creates defaults, what a specification is, don't pursue links I provide that back up what I say, and then cross-post in other threads making idiotic accusations but never update the errors you make with correct information.
 
When I'm wrong, I have the decency to say so and give credit where credit is due because my concern is disseminating correct information. Apparently you have different priorities.
 
At this point, I honestly don't know if you truly don't understand, or whether your're willfully ignorant.
 
Please, turn the thread title from a threat to a promise. 

Here is what I know.  

The checkboxes in the SAME dialog box don't act the same.  This is not the "norm" if you will.   As I showed you in the video, if I select "Simple Instrument Track" or "Track Folder" or "All Stereo Outputs" - and then choose to never ask me again... those settings will always work when I insert a softsynth.... just not the "Enable MIDI Output".   

If you can't see how that seems like a poor design, I don't know what to tell you.   One would expect that if "Enable MIDI Output" is disabled and then you choose "never ask me again", NO synth you insert would have it's MIDI output enabled!  It's like SUPER-simple.   INFACT the checkbox works when you choose to ask every time!  Seems kinda wonky.

Oh and what about this....  is this a bug?  http://forum.cakewalk.com/FindPost/3542635
 

SilverBlueMedallion

Anderton

SilverBlueMedallion
What is that "Enable MIDI Output" option there for, when you see it doesn't do ANYTHING!
 
I can't actually believe after looking at my 4 steps you are still saying this is by design!!  The checkmark actually DOES NOT DO ANYTHING!!!  IT - IS - BROKEN!

How is that by design?  What you are saying makes no sense now.... just anything to make this not look like a Sonar issue.  Unbelievable.

What's unbelievable is that you blame me because you don't understand what a default is, what overriding a default is, what creates defaults, what a specification is, don't pursue links I provide that back up what I say, and then cross-post in other threads making idiotic accusations but never update the errors you make with correct information.
 
When I'm wrong, I have the decency to say so and give credit where credit is due because my concern is disseminating correct information. Apparently you have different priorities.
 
At this point, I honestly don't know if you truly don't understand, or whether your're willfully ignorant.
 
Please, turn the thread title from a threat to a promise. 

Here is what I know.  

The checkboxes in the SAME dialog box don't act the same.  This is not the "norm" if you will.   As I showed you in the video, if I select "Simple Instrument Track" or "Track Folder" or "All Stereo Outputs" - and then choose to never ask me again... those settings will always work when I insert a softsynth.... just not the "Enable MIDI Output".   

If you can't see how that seems like a poor design, I don't know what to tell you.   One would expect that if "Enable MIDI Output" is disabled and then you choose "never ask me again", NO synth you insert would have it's MIDI output enabled!  It's like SUPER-simple.   INFACT the checkbox works when you choose to ask every time!  Seems kinda wonky.

 
Okay, now I know for sure: You're willfully ignorant. I provided a recipe that proves what you say in bold is wrong and I provided a link to back up what I said. 

Oh and what about this....  is this a bug?  

Now I also know for sure you don't read my responses, because I already replied to that - which supports the perception that you have no interest in a dialog. Your only response to anything is ultimately "It doesn't work the way I want it to work." 
 
I can't let this go by without comment...
 

But I understand as a VP of Gibson, this thread could potentially sway new users away from a purchase, hence you have to make it look like there is no problem and its a user error.

 
If potential SONAR owners see this thread, they'll be very impressed with our patience. Then they'll check out the other forum threads, and think "Yeah, this is a pretty helpful bunch of people...well, except for a couple."
 
I have been a VP at Gibson for almost 4 years. I switched to SONAR almost 17 years ago. I have been using DAWs since the first Pro Tools. You will find no difference in what I've said about SONAR before and after I was with Gibson, except that I do bite my tongue a bit more to avoid seeming too enthusiastic about new features (besides, plenty of people here do it anyway), and I'm more critical of the program because now I actually owe something to the users beyond just helping out. I think most people here know that I advocate for the needs of Cakewalk to the users, and for the needs of the users to Cakewalk. That advocacy is not always positive, in either direction.
 
I have worked with Ableton, Steinberg (for whom I designed a plug-in), Avid, Magix, Sony, Native Instruments, Acoustica, PreSonus, Waves, and others whose names escape me right now. As a result I am proficient in all their programs. I don't complain about learning curves being difficult, I respect and admire that all these companies have made extremely deep and innovative programs for tiny niche markets.
 
Even when I was consulting to them, they knew upfront that SONAR was my DAW of choice. But they were mature enough to realize that it's my DAW of choice because it fits my particular needs best. All software has bugs, workflow issues, legacy items in need of cleanup, sections that haven't been updated in years, etc. However, I don't have a sense of entitlement about it. I am very grateful for the fact that this industry has produced tools costing us a few hundred dollars that were worth a half a million not that long ago (and which required constant maintenance, by the way). I am thankful we have all these incredible tools at our disposal, warts and all. Despite your opinion that making a lot of noise and demanding attention will get results, you are wrong. It's not because of people like you that this rate of improvement occurs; it's because of the people at these companies and the people who actually learn and use the programs.
 
I urge you to download trial versions of other programs. It's insane that you're not doing that now - you said you were going to leave Cakewalk, so you better start learning  some other programs in order to make good on your thread title.

too many quotes within quotes, so let me just hit a few short points:

#1:
Anderton:  "Okay, now I know for sure: You're willfully ignorant. I provided a recipe that proves what you say in bold is wrong and I provided a link to back up what I said. "
 
Adam:  The "Enable MIDI Output" option ONLY works if you have it set to ASK.  Can we establish that as fact?   If you have to have it ask every time, perhaps the option should be removed from the default options window, no?   It could get very confusing.... as "simple instrument track", "track folder" and other parameters DO work even if you set it to never prompt.   So the "Enable MIDI out" in the SAME dialog prompt NOT working (if you don't set it to ask every time) seems like it shouldn't be there, since it doesn't really do anything.

I actually feel like you are missing my point, we can't be this far off.  I trust you are an intelligent person, and trust me, I am too, despite what you think lol.   I seriously think we are having a serious miscommunication.  



#2:  (regarding:  http://forum.cakewalk.com/FindPost/3542635)
 
Anderton:  Now I also know for sure you don't read my responses, because I already replied to that - which supports the perception that you have no interest in a dialog. Your only response to anything is ultimately "It doesn't work the way I want it to work." 
 
Adam:  I haven't seen you once speak to this.   The screenshot itself is showing 2 different things lol.  When you choose "None", it actually says "Omni" below (see the 2 red arrows?) how can that be Anderton?   It is either "None" or "Omni".  And it works like "Omni" (All MIDI as a source) instead of "None".   How can you say that choosing "None" as an input and having it work as "Omni" is not a bug?  You know that in a private message with a Cakewalk engineer, I pointed this out as a problem and it was actually acknowledged as a problem, right?   Yet you are saying things to the effect this is design?


And as far as anything about you being a VP or anything personal... let me say this right now.   Before this "tiff", I thought you were a cool dude.   I remember a song you wrote for your daughter, it had to do with being so far away or something... really good stuff I recall.   You have always helped me in the past and I have always thanked you for it.  In no way did I come start this thread to fight with you or any of the CW members.  It was just plain truth.  A friend of mine was over when I lost the patches for a song of his, and I just decided, you know what.... "I think i might need a new DAW"....  the list of problems kept growing, so... that was my title.  Nothing but TRUTH.  I have been testing DAWs, have a few installed, but I would love to just stay with Sonar. It is what I know for a long time now.   I started to get angry when I felt all you were doing was trying to soften my post.   

I lost a lot of time spent on this project (yes stupid me, I didn't save patches), because I trusted "freeze synth, whatever... lesson learned...  but just remember, my frustrations come out of real problems I had here, then softening the thread really just made me feel like you were doing it so it seems like a user problem and not a Sonar problem.

Anderton,
 
I made a new short video, maybe I am failing to type properly what I mean, but I am very clear and to the point here.   Maybe this is what I should have posted to begin with.  I hope you see the problem(s) here.

https://www.youtube.com/watch?v=M9z1Lr2P5rQ

Thank you,
Adam
 

SilverBlueMedallion

gustabo

SilverBlueMedallion

gustabo

SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!

Wrong.

 
OK, my volume on my synth is being controlled by erroneous data, so someone told me to insert a CC 7 value (volume) at the start of my track so it resets the volume.... how on earth will it reset the volume to that parameter if I am not starting at the beginning of the track where the CC 7 value is manually entered in.  

besides, I shouldn't have to do that anyway if erroneous MIDI data wasn't making its way into the track

There is something called "Controller searchback before play starts".

 
Oh ok, cool.  I have that turned off, it was suggested from another issue I am having with presets not saving correctly.   Cool feature.

I saw that post, the dude was helping you troubleshoot why your soft synths were consistently not remembering their settings.
He never told you to leave it off, he said try it.

gustabo

SilverBlueMedallion

gustabo

SilverBlueMedallion

gustabo

SilverBlueMedallion
Yes, I WILL need to start at the beginning of the track... that's the point!

Wrong.

 
OK, my volume on my synth is being controlled by erroneous data, so someone told me to insert a CC 7 value (volume) at the start of my track so it resets the volume.... how on earth will it reset the volume to that parameter if I am not starting at the beginning of the track where the CC 7 value is manually entered in.  

besides, I shouldn't have to do that anyway if erroneous MIDI data wasn't making its way into the track

There is something called "Controller searchback before play starts".

 
Oh ok, cool.  I have that turned off, it was suggested from another issue I am having with presets not saving correctly.   Cool feature.

I saw that post, the dude was helping you troubleshoot why your soft synths were consistently not remembering their settings.
He never told you to leave it off, he said try it.

 
of course, but I am saying that isn't the issue here, that's all.  i appreciate the efforts.

Right now, these are the 2 things that I don't get:  https://www.youtube.com/watch?v=M9z1Lr2P5rQ

SilverBlueMedallion

gustabo

SilverBlueMedallion
hmmm actually according to this, it appears that function does not search back for any and all CC data, just 
patch change, wheel, and pedal events.  so i dont think thats it.  
 

https://www.cakewalk.com/Documentation?product=SONAR%20X2&language=3&help=Playback.33.html
 
 

Your ignorance about what you want astounds me!
What do you think pedal and wheel events are? They're CC info.
Without testing it, you'll never know!

(It's Cakewalk's fault for not seeing you coming, they should have listed every single CC# )

either way, I shouldn't have to put any CC 7 data in there if CC from other softsynths wasn't erroneously making changes to other softsynths.

I've had that happen on projects before with just one soft synth loaded. It wasn't a Sonar issue, it was a soft synth and/or patch issue, it was resetting itself without any cc7 data in the midi track. To overcome that, I would right click on the midi fader and click on "disable control".

gustabo

SilverBlueMedallion

gustabo

SilverBlueMedallion
hmmm actually according to this, it appears that function does not search back for any and all CC data, just 
patch change, wheel, and pedal events.  so i dont think thats it.  
 

https://www.cakewalk.com/Documentation?product=SONAR%20X2&language=3&help=Playback.33.html
 
 

Your ignorance about what you want astounds me!
What do you think pedal and wheel events are? They're CC info.
Without testing it, you'll never know!

(It's Cakewalk's fault for not seeing you coming, they should have listed every single CC# )

either way, I shouldn't have to put any CC 7 data in there if CC from other softsynths wasn't erroneously making changes to other softsynths.

I've had that happen on projects before with just one soft synth loaded. It wasn't a Sonar issue, it was a soft synth and/or patch issue, it was resetting itself without any cc7 data in the midi track. To overcome that, I would right click on the midi fader and click on "disable control".

 
fair enough.   I am not saying there can't be some wonky VST issues... but check my video.  Tell me if my 2 points dont make sense.  Thank you. 
https://www.youtube.com/watch?v=M9z1Lr2P5rQ

BobF
If you want the Baker's attention, submit feature requests and/or problem reports as required.

 
Check the OP's OP. They have done just that.