SilverBlueMedallion

frankjcc
I agree it is a bug, as this is the behavior I get as well, and I expect it to do what it says it will.  I don't think he should accuse Craig of something before giving him a chance to reply.

well I am simply going on past responses. Craig usually tries to soften problems within the software.  He even replied to me telling me how its not a bug - something about how if they disable it, then a whole other set of users will complain... HUH?  who's talking about disabling it?   Just get the check box to work properly!

You obviously didn't even bother to check the links I provided, or you would have realized that this is BY DESIGN, and if you pursued the topic further, and understood how plug-ins interact with hosts, you would find out why. 
 
Many design decisions involve tradeoffs. It so happens that this DESIGN DECISION trades off convenience for some people, who I think are likely the majority of users, for less convenience for other users, who I think are likely in the minority. 
 
I told you what feature request to put in. You will not get results by telling a company something done BY DESIGN, specifically to accommodate the VST3 spec, is a bug. It looks like you don't intend to pursue putting in a feature request, so I can only conclude you would rather double down on playing victim. You obviously won't educate yourself, and it's a waste of my time to try and educate you, or at least point you to places where you can educate yourself.
 

frankjcc
thank you SilverBlueMedallion, I see, I remember a chord playing synth that needed midi out like this(too complicated for me, deleted).  for me I think if I use something 99% of the time a specifiec way, it should be default behavior, and 1% that I want to change this, is when I should look into settings and stuff. especially if it's an option.

oh but it IS an option, see my 4 step process above from this morning.   the option just flat out IGNORES what you tell it.  

SilverBlueMedallion
 
oh but it IS an option, see my 4 step process above from this morning.   the option just flat out IGNORES what you tell it.  

 
It's not "it's all about you." SONAR is not ignoring you, it's paying attention to you opening the plug-in, and doing what the plug-in tells it to do when you open the plug-in. Blame Steinberg for making it so that VST3 instruments send a flag saying they have MIDI out so DAWs can enable it automatically, which is what SONAR (and other DAWs that follow the VST3 spec's recommendations) do.
 
If you can't grasp what I've presented in my last two posts, there's nothing more I can say. If you want this change, do a feature request. If I was Cakewalk, I'd likely ignore it because the current decision is intended, per Steinberg's suggestion, to benefit the greatest number of users. But give it a shot.

SilverBlueMedallion

chuckebaby

pwalpwal
sorry if this is no-brainer, but after unchecking the "ask every time" box, how do i get it to ask again the next time? (dragging a synth from the browser, with "midi out" unchecked, and "ask every time" unchecked)
thanks in advance!

hey PWAL, Go in to the Synth Rack and open up a synths properties page, then uncheck the box that says " Don't ask me again". hope this helps man.
 

frankjcc
I agree it is a bug, as this is the behavior I get as well, and I expect it to do what it says it will.

you get what as well ?
Are you saying im supposed to have manually enable MIDI out whenever I  want to use it ?
No thanks. im happy with the way it is.

 
How about the checkmark just do its job!  This way we BOTH can be happy Chuckebaby!   Allow users to determine the default "Enable MIDI Output" behavior.  Like the checkmark is SUPPOSED to!

This forum is a great place and has a wealth of knowledge from individuals who are willing to put in their free time to help others, however I found in the past that when users rub people the wrong way, then there are less people willing to oblige their free time to help.
 
Like the exclamation points. hope im not reading in to that too much but it appears as if your yelling.
No need to get upset. As said many times, no one is chaining you to this software. you can still use Sonar but use something else as well.
 
I have invested some good solutions and responses to a good portion of your threads. trying to help you out.
But I feel as though your not really interested in solutions. but more on the lines of "The squeaky wheel gets the grease". You want a customized DAW to work exactly how you want it to.
 
Simply try to enjoy making music with the tools you are given, if not then your really only making yourself miserable and exhausted. you have put a lot of work in to these threads. just think if you put this same passion in to your music.
 
Here's another food for thought.
This forum is a 2 way street, you ask for help and you help others. With the risk of getting too personal here, I haven't seen you once help anyone else on this forum besides yourself. Help someone else out once in a while. It will make you feel good as a person. Be part of this great community.
Pick and choose your battles man. you cant win every war. know what I mean ?
 
Peace and good luck making good music.

Craig, are you suggesting that the check box should have been removed upon conforming to the vst3 specs?

Anderton

SilverBlueMedallion
 
oh but it IS an option, see my 4 step process above from this morning.   the option just flat out IGNORES what you tell it.  

 
It's not "it's all about you." SONAR is not ignoring you, it's paying attention to you opening the plug-in, and doing what the plug-in tells it to do when you open the plug-in. Blame Steinberg for making it so that VST3 instruments send a flag saying they have MIDI out so DAWs can enable it automatically, which is what SONAR (and other DAWs that follow the VST3 spec's recommendations) do.
 
If you can't grasp what I've presented in my last two posts, there's nothing more I can say. If you want this change, do a feature request. If I was Cakewalk, I'd likely ignore it because the current decision is intended, per Steinberg's suggestion, to benefit the greatest number of users. But give it a shot.

 
Anderton, please explain what the checkmark does in the "Enable MIDI output" tab.   If you see my 4 steps, it does NOTHING.  Tell me what it does....  

SilverBlueMedallion

Anderton

SilverBlueMedallion
 
oh but it IS an option, see my 4 step process above from this morning.   the option just flat out IGNORES what you tell it.  

 
It's not "it's all about you." SONAR is not ignoring you, it's paying attention to you opening the plug-in, and doing what the plug-in tells it to do when you open the plug-in. Blame Steinberg for making it so that VST3 instruments send a flag saying they have MIDI out so DAWs can enable it automatically, which is what SONAR (and other DAWs that follow the VST3 spec's recommendations) do.
 
If you can't grasp what I've presented in my last two posts, there's nothing more I can say. If you want this change, do a feature request. If I was Cakewalk, I'd likely ignore it because the current decision is intended, per Steinberg's suggestion, to benefit the greatest number of users. But give it a shot.

 
Anderton, please explain what the checkmark does in the "Enable MIDI output" tab.   If you see my 4 steps, it does NOTHING.  Tell me what it does....  

Since you're clearly too lazy to follow my links and find out for yourself, I'll tell you in my very last response prior to blocking you. I see no need to respond to your posts if you don't read them, or don't know how to click on a link.
 
I already gave you everything you needed to know about how to find that out. I already explained it in very basic language. 
 
But I will try once more, in the simplest language humanly possible. I honestly don't know how I can dumb it down any further. 
 
It clears the "enable MIDI out" flag that synths can enable upon being inserted, in accordance with the VST3 spec.
 
When you insert a synth, if SONAR detects a command saying that MIDI out is available, it obeys that command and enables MIDI out. (The VST3 spec has priority over the SilverBlueMedallion "why can't SONAR read my mind and tell the VST3 spec before I load the synth that I don't want MIDI out enabled" spec.)
 
If you uncheck that box, you will find that it indeed does exactly what it's SUPPOSED to do and was DESIGNED to do - clear the VST3 default that enables MIDI out. (Note: Steinberg designed the VST3 spec. Cakewalk follows it.) 
 
It does not do what you want it to do because SONAR cannot disable something it doesn't know exists. That is why you would need to submit a feature request* that if you unchecked that box, would have SONAR tell the VST3 spec to go get lost, and pre-emptively ignore any MIDI out flag being sent by a plug-in. Because if it didn't, then the next time you inserted a synth with MIDI out, it would tell SONAR "hey, enable out." Then, of course, you would have to enable "MIDI Out" in the synth preferences after loading a synth that did provide MIDI out.
 
And I'm sure you'd complain about that as well, as would the others for whom this design decision by Steinberg, and followed by Cakewalk, was made. 
 
You could also write all the plug-in manufacturers who make instruments with MIDI out and ask them to include a switch in preferences that disables it from sending out a flag that says it's capable of providing a MIDI output. Good luck with that.
 
*If you don't understand the difference between a "feature request" and a "bug report," I'm sure the forum can help you out because I sure am not going to waste any more time on someone who can't read.

 

"It clears the "enable MIDI out" flag that synths can enable upon being inserted, in accordance with the VST3 spec."



 
 
then how is MIDI out still enabled even after I unchecked it?  see Step #3 and #4 above?  
 
oh and you keep mentioning VST3, well this happens with VST2 plugins as well.  

If the "Enable MIDI Output" checkmark actually does nothing as you say because of the VST3 specifications, then why have it?
 

I JUST FOUND THE BUG!

The "Enable MIDI Output" option ONLY WORKS if you have it prompt you EVERY TIME you launch a synth!   Then it does not enable the MIDI Output!

But if you set it as an option and then choose to never ask you again, it will NOT follow the checkmark state!!!  

So yea, has nothing to do with VST3 architecture Anderton!!

SilverBlueMedallion
I JUST FOUND THE BUG!

The "Enable MIDI Output" option ONLY WORKS if you have it prompt you EVERY TIME you launch a synth!   Then it does not enable the MIDI Output!

But if you set it as an option and then choose to never ask you again, it will NOT follow the checkmark state!!!  

So yea, has nothing to do with VST3 architecture Anderton!!

please clarify your steps, I'm still having the problem.