All switching the button to automated mute does is change the behavior of how the *button* responds - not how previously recorded automation renders.  i.e. by default the button reflects the track level mute and will not change in response to mute automation envelopes present on the track.
 
The OP's sig shows that he is running X1. We fixed numerous bugs with automation (especially for jumps) and mute automation in X2 and X2A. As far as I know there are no issues with rendering mute automation in X2 like you describe.

Just use a volume envelope.

Guitarhacker
Just use a volume envelope.

This has a lot of merit
 
Sometimes you simply don't want the abrupt "snap" from fully on to fully off like you get with an automated mute.
I remember one of the Bakers saying that automated mutes involve using extremely short crossfades - but in my case, when I use them, they are still too short to prevent the odd "crack" that you hear when a non-zero crossing is involved.
 
With a volume envelope, you can get as surgical as you want with your fade in/out

Noel Borthwick [Cakewalk]
All switching the button to automated mute does is change the behavior of how the *button* responds - not how previously recorded automation renders.  i.e. by default the button reflects the track level mute and will not change in response to mute automation envelopes present on the track.
 
The OP's sig shows that he is running X1. We fixed numerous bugs with automation (especially for jumps) and mute automation in X2 and X2A. As far as I know there are no issues with rendering mute automation in X2 like you describe.

So basically .... to the OP and others who have this issue... Buy X2 or be left in the dark!
Wouldn't it be nice to see some bugs fixed and support for those who haven't upgraded?

thebiglongy
 
So basically .... to the OP and others who have this issue... Buy X2 or be left in the dark!
Wouldn't it be nice to see some bugs fixed and support for those who haven't upgraded?

Sure would be nice, I would imagine there are those running every other version of SONAR that have the same wish. Updates for older versions are not going to happen. There is a way to use mute if you want to, draw it in, it has always worked.

scook

thebiglongy
 
So basically .... to the OP and others who have this issue... Buy X2 or be left in the dark!
Wouldn't it be nice to see some bugs fixed and support for those who haven't upgraded?

Sure would be nice, I would imagine there are those running every other version of SONAR that have the same wish. Updates for older versions are not going to happen. There is a way to use mute if you want to, draw it in, it has always worked.

Of course updates for older versions won't happen, Cakewalk is in the money game after all...

I can't take credit for the Channel Tools idea because I swiped it from one of the Groove3 vids (kind of). I find trying to get some of the parameters on the actual console strips a little confusing and some stuff just doesn't seem to work as detailed in the manual. After seeing what could be done with Channel Tools within an FX Chain I can pretty much assume that I can automate most things that would traditionally be done via the console strip much easier. I've only played with this concept breifly though so I'm sure there are some limitations but for simple stuff like this the FXC + CT combo is a winner IMO. The button, knob and parameter boundary functions of the Chain Modules are wicked handy and easy to use once you figure them out. Cheers.

Bristol Jonesy, Thanks but per my original post, I am switching to automated mute first so I don't think that is the problem.
 
Guitar Hacker, I can use fader automation, of course, but as in my original post, I really want to save that until the mix and just turn the right tracks off and on while working.  Clip automation or clip mute will not work because Melodyne is in the tracks.
 
Basically, I can automate the faders quickly to get something going, but mute would be much more convenient and should work.  I do believe this is a bug.
 
One thought: since some people say auto mute works, and since there is a known issue trying to use auto mute by pressing the mute buttons on a control surface, maybe something about connecting the VS-700 control surface screws up the automated mute function.  To reiterate, I am clicking the on-screen buttons—not pressing the hardware buttons—but maybe this is an interaction bug between the VS-700 and Sonar.
 
For now, I will just use quick and dirty fader automation but I really really wish I had automated mutes for many reasons.  One reason is to preserve the fader moves while deciding which tracks to include in a mix—especially inmportant if you are doing multiple mixes.
 
Thanks for all the replies.

And, not wishing to flog this dead horse for too much longer, your mute envelopes are in the right place in the track yes? Up near the top for muted and down near the bottom for not muted yes?

Correct, Colin, the envelopes show the correct movements.  I feel that they are backwards (down should be mute and up should be unmute, in my opinion, to match volume), but either way, they are not doing anything: the track just keeps playing whether the envelope is up or down; and, whichever was last muted keeps "not playing" regardless of the envelope.  Very weird.
 
I am pretty much convinced it is a VS-700 thing, but who knows?