Anderton

azslow3

SilverBlueMedallion

John
To prevent the volume on the FM8 from being lowered goto the Event List View and insert a CC7 with level you want the FM8 to play at the very beginning. If for some reason you have other CC7s in the track and don't want them delete them. Once that has been done you can have reset controllers without problems. 

and what if i am not starting playback at the very beginning?  

This is not something one should have to do.  Maybe it shouldn't be getting random CC 7 messages to begin with.

Sorry for repeating that, one more and for the last time from me:
Sonar IS NOT injecting any MIDI, and it IS NOT changing synth parameter. It is you, your equipment or your installation which does that fancy things. At least there was no single prove that is usual for other users.
 
Sonar has some inconvenient behavior with MIDI, which is the same for everyone. Just inconvenient, nothing serious.
 
Sonar has some small bugs in MIDI, confirmed by other. All of them are triggered in quite special situations only. They are not in the list of your complains.
 
Sonar does not support MIDI routing. Sonar does not really support MIDI FXes in VST format. That is in the future requests for long time, but that is not a bug. It is simple "not there yet". Using VST MIDI outputs is A WORKAROUND to somehow support VST MIDI FX. Far from perfect. Has several problems, including known and not mentioned by you.  And it is known that using this workaround is a nightmare as soon as you change MIDI devices, re-route something, etc.
Sonar also can not prepare food. It is possible to insert  tons of plug-ins and start playback, that will drive CPU to the limit, it will produce a lot of heat, so theoretically cooking something. But it is pointless to complain that does not work perfectly.
 
Sonar is DIRTY CHEAP for the value of third party software coming with it. If you sum even cheapest discount prices of AD2, Melodyne and all other included plug-ins, it is easy to prove you pay almost nothing for the DAW. It can not do EVERYTHING the way ANY PARTICULAR USER wants. There are other software packages, which provide other and sometimes better ways for particular workflows. They are also DIRTY CHEAP. Think about it other way: all your $$ spent for Sonar can at most cover ONE programmer for ONE day....

 
Azslow3, I truly appreciate that a) you know what you're talking about, and b) that you try to educate people whose minds are made up and not interested in facts. However, after my providing links showing that something SBM repeatedly calls a "bug" is a specific design decision (detailed in the Cakewalk blog concerning SONAR's VST3 implementation), and his refusal to educate himself about why that design decision was made, I have chosen to give up on him and instead, spend my time on people who benefit from the learning process rather than reject it. 
 
And I can't believe he said "and what if i am not starting playback at the very beginning? This is not something one should have to do." Well one doesn't have to, but he clearly knows so little about SONAR's basics he's not aware of "Zero controllers when play stops" and "Controller searchback before play starts," let alone when or how to use them. Yet he wants us to believe he's incapable of user error.
 
People with a solipsistic mindset who demand constant attention and play victim get tiring. Perhaps we should take up a collection and buy him any software program he wants, with the stipulation that he participate only in that program's forum. 

 
 
Anderton, the user is telling me to put a CC 7 control in the beginning of my track to ensure the volume is where I want it.   Yes, I WILL need to start at the beginning of the track... that's the point!  I shouldn't have to if Sonar's "NONE" wasn't actually acting as MIDI Omni for input!  Don't you get it?

Also did you see the steps here?  http://forum.cakewalk.com/FindPost/3542477
 
How can you say this option is "working".   you seriously are flat out saying now things are working as is, when they CLEARLY aren't.  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.

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

Wrong.

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

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

That was me and I was trying to answer why when you start playback the volume is not what you want. The channel idea was trying to avoid errant MIDI affecting other synths. All you have to do to prevent synths from sending MIDI data out and is in the dialog I talked about uncheck that. I said noting about a widget in the track. 
 
I've been working with MIDI for twenty or more years. Before there was a Sonar. And these are not problems unless you make them problems. 

Go to preset/project/midi and make sure there is a check mark on patch/controller search back before play starts and when you start a playback later in the song Sonar will read all of the patch/controller settings prior to starting the playback.
 
Are you sure that erroneous MIDI data is making the changes or is the softsynth just starting at its own designated settings?  I have run into that with Kontakt were I have to start a track with a CC7/11 or 2 or else Kontakt will use its designated volume setting.  YMMV

This is what I'm talking about. 
 

 
Because it unchecked there will be no MIDI output from the synth. 

Ye Gods.

Look, this really is very, very simple.

Before you launch any DAW you turn your audio interface on, yes? That's a rhetorical question by the way. If you don't then any project loaded will complain about it and the master bus and any other busses feeding hardware outputs won't be routed correctly.

MIDI hardware is treated the same way.

If, before you launch Sonar you switch your MIDI controller on so Sonar is seeing the MIDI environment the projects tell it to expect to see MOST OF YOUR "PROBLEMS" WILL GO AWAY.

If you used MIDI channels to route MIDI MOST OF YOUR "PROBLEMS" WILL GO AWAY. If you used some DAWs, e.g. Logic for one, you would have to do that. If you used hardware synths or MIDI controlled processors you would have to do that. Putting lots of stuff all on the same channel is asking for problems and massively complicates sorting out routing problems and mistakes. Using channels means you can be certain MIDI only controls what that particular MIDI should be controlling. Doing it your way is asking for problems.

It is not Sonar's fault that you don't switch your controller on or refuse to use channels to help keep MIDI routing as you want it and would rather vent here about what is neither a design problem nor a bug other than the omni/none naming issue. WHICH YOU CAN AVOID BY TURNING YOUR CONTROLLER ON OR USING MIDI CHANNELS before opening a project that expects it to be available.

And that's the first time I've ever shouted on this forum, but I'd hate to see someone being misled by your personal gripes.

tlw
Ye Gods.

Look, this really is very, very simple.

Before you launch any DAW you turn your audio interface on, yes? That's a rhetorical question by the way. If you don't then any project loaded will complain about it and the master bus and any other busses feeding hardware outputs won't be routed correctly.

MIDI hardware is treated the same way.

If, before you launch Sonar you switch your MIDI controller on so Sonar is seeing the MIDI environment the projects tell it to expect to see MOST OF YOUR "PROBLEMS" WILL GO AWAY.

If you used MIDI channels to route MIDI MOST OF YOUR "PROBLEMS" WILL GO AWAY. If you used some DAWs, e.g. Logic for one, you would have to do that. If you used hardware synths or MIDI controlled processors you would have to do that. Putting lots of stuff all on the same channel is asking for problems and massively complicates sorting out routing problems and mistakes. Using channels means you can be certain MIDI only controls what that particular MIDI should be controlling. Doing it your way is asking for problems.

It is not Sonar's fault that you don't switch your controller on or refuse to use channels to help keep MIDI routing as you want it and would rather vent here about what is neither a design problem nor a bug other than the omni/none naming issue. WHICH YOU CAN AVOID BY TURNING YOUR CONTROLLER ON OR USING MIDI CHANNELS before opening a project that expects it to be available.

And that's the first time I've ever shouted on this forum, but I'd hate to see someone being misled by your personal gripes.

 
 
totally wrong, i dont need to plug in my interface if "NONE" actually meant "NONE".


see:  http://forum.cakewalk.com/FindPost/3542635
 
 

You're just trolling now. Blocking applied.

ampfixer
You're just trolling now. Blocking applied.

absolutely not trolling.  this is a REAL issue inside Sonar.  NONE=Omni 

LOL