Options->Project->MIDI Out->Zero Controllers When Play Stops

Post
benstat
Max Output Level: -71 dBFS
2010/12/01 05:00:38
Hi all,
I have two VSTi plugins with certain midi CC's that reset to zero when I stop playback (Vir2 Electri6ity and Garritan Personal Orchestra 4). I fixed the problem by disabling the setting mentioned in the title. It seems odd that I have to do this at all, because I have loads of other plugins that work just fine with it enabled.
I suppose I'm wondering why this setting is enabled by default, what good does it do anyway, and what effect it's having (if any) on my other plugins when I disable it?
Many thanks!
rbowser
Max Output Level: -10 dBFS
Re:Options->Project->MIDI Out->Zero Controllers When Play Stops 2010/12/01 10:13:57
Hi, Benstat

I'm glad you found that setting.  Ever since GPO first came out, it's been the #1 instruction to Cakewalk/Sonar users that they have to change that setting.  When "zero controllers" is left un-checked, GPO instruments constantly come up silent after pausing and hitting Play again. 

It's because CC1, Mod Wheel, is the volume controller in GPO, and the instruments need CC1 values constantly streaming to it.  The programmers intend for Mod Wheel data to be almost constantly fluctuating, and when it is, a much more natural performance is recorded.

I've used GPO for years now, and along side many other virtual instruments that don't behave the same way - and it's no problem.  Having that un-checked won't have a negative effect on your other synths.  I can guarantee that from years of experience.

Randy B.
brundlefly
Max Output Level: 0 dBFS
Re:Options->Project->MIDI Out->Zero Controllers When Play Stops 2010/12/01 10:32:19

Having that un-checked won't have a negative effect on your other synths. I can guarantee that from years of experience.

 
It will have one noticeable negative effect: When the notes of any instrument are being held by sustain (CC64), they will continue to ring after you stop playback until you do something to stop them. The easy way is to cycle the sustain pedal on your controller.
 
For a project with a piano part full of sustain events, I prefer to leave zero controllers enabled, make sure that Controller Searchback is also enabled, and every track that needs a non-zero controller value for volume or some other sound parameter to be correct has at least one such event in the track.
 
 
post edited by brundlefly - 2010/12/01 10:37:57
rbowser
Max Output Level: -10 dBFS
Re:Options->Project->MIDI Out->Zero Controllers When Play Stops 2010/12/01 10:59:02
Hi, Brundle - Thanks for that note.  I'm so used to the ringing out CC64 syndrome that it didn't even come to mind when I replied to benstat earlier.  My foot is always there on the pedal as I work - click, no problem.  That's been my ingrained adaptation.  Your solution is probably more elegant. 

And it's a good example of why Zero Controllers is in Sonar in the first place - With it, ringing Sustain is avoided.  It seems like the hardware synths I first started with would have volume and Everything stuck without that controller.

I have worked with this control off for years now, and it's worked fine for me.  Without knowing about that setting in Sonar, many Garritan newbies have been very confused.

Hope you have smoother sailing now, Ben.

Randy B.
brundlefly
Max Output Level: 0 dBFS
Re:Options->Project->MIDI Out->Zero Controllers When Play Stops 2010/12/01 11:13:53
My foot is always there on the pedal as I work - click, no problem. That's been my ingrained adaptation. Your solution is probably more elegant.

 
Since piano is my primary instrument, and I only recently started using synths that use CC1 for volume (JABB ), I've pretty much come to depend on Zero Controllers. But there have been other times I wished I could have it zero only CC64.
 
I sort of figured the Bakers would add some flexibility to that feature of their own volition at some point, but it never happened. Guess I'll need to make a feature request.
bvideo
Max Output Level: -58 dBFS
Re:Options->Project->MIDI Out->Zero Controllers When Play Stops 2010/12/01 11:17:29
Edit - sorry, late reply - ignore

The usual reason for reset to zero is for controllers that are used for expressions, like a pitch bend or the hold pedal. Resetting a pitch bend or hold to zero before the next play seems like a pretty reasonable arbitrary behavior.

As for why some VSTi's do and some don't reset their CC's, it may be simply that they do or don't respect the commands sent by Sonar or they don't use the particular CC's that Sonar chooses to reset.

As for the problems it might be causing you, also check out the searchback option. Both options spelled out from the manual:

Zero Controllers When Play Stops
If this option is enabled, SONAR zeroes (resets) the pitch wheel, the pedal Controller, and the modulation wheel Controller on all 16 MIDI channels whenever playback is stopped. It also sends a “Zero All Continuous Controllers” MIDI message, which turns off other continuous Controllers on newer synthesizers. If you
experience frequent stuck notes when playback stops, try checking this option.
Patch/Controller Searchback Before Play Starts
If this option is enabled, SONAR searches for and sends the most recent patch change, wheel, and pedal events on each output and MIDI channel before starting playback. This ensures that all these settings are correct, even if you start playback at an arbitrary point in your project.

Note: I don't know if searchback will work on all the CC's you might be using for your VSTi's.

Bill B
post edited by bvideo - 2010/12/01 11:26:39
benstat
Max Output Level: -71 dBFS
Re:Options->Project->MIDI Out->Zero Controllers When Play Stops 2010/12/01 12:16:11
Many thanks for all of your responses. That makes a lot of sense. I now know what it's for, and how to work with it or around it as necessary!