Working on a project that was started several weeks ago.  This evening I manually added volume automation on several tracks, however the project does not respond to the volume envelope on playback.  Here are some of the variables
 
1. The automation Read button is selected on these tracks.
2. There are a number of other tracks where volume automation was added several weeks ago.  These tracks DO respond to the automation on playback.
3. Between the time the older automation envelopes were added and now I installed the 2016.11 upgrade shortly after it was released and had the crashing issues, specifically when opening this project.
4.  I rolled back to 2016.10 and the crash issues seemed to be resolved.
5. Just to add another factor, the latest updates to Windows 10 were installed today, before I started today's work on this project.  I did get the 'Sonar has unexpectedly stopped working' message when I tried to open this project today.  I restarted Sonar and the project opened from the Start Screen as expected.
6.  I then added the new volume automation lanes, which now don't work on playback.
 
I don't discount the possibility that I am missing something easy and obvious that I should have done, but if anybody has any ideas on how to get the automation working I will be grateful.
 
Thanks in advance for your help.
 

Is this a MIDI track, a simple instrument track or an audio track?

If it's a MIDI track or simple instrument track, does the MIDI synth or soft synth respond to CC7 events?

Is the track routed to a bus or an aux track that has a plugin attached that is affecting the position of the sound in the stereo field.

Hi Ron, It sounds like you're doing things right and this probably is a bug. I had similar problems a few months back (2016.9 ?) except it was automation to PC modules. I would draw in the automation but the module would not respond, so I tried with a different module and same result. BUT after I had started the project several times, the automation started working as it should. I recall doing the same things on a different track, different PC modules, and again at first it didn't work, after a few plays - it works.  Just thought I'd throw that into the mix.   <<<< pun 
 
Also, since 2016.11, I have had many crashes while opening first project after starting Sonar. Seems many people have had crash problems with this update. (which I hope 2016.12 will fix!)
 
Sorry, no good advice

promidi
Is this a MIDI track, a simple instrument track or an audio track?

If it's a MIDI track or simple instrument track, does the MIDI synth or soft synth respond to CC7 events?

Is the track routed to a bus or an aux track that has a plugin attached that is affecting the position of the sound in the stereo field.

Good questions.  These are all audio tracks and the Master Bus.  The audio tracks are routed to sub-busses, but these have no automation on them.  At this stage of the project there is no automation in use other than volume on some audio tracks and on the master bus.

In the Mix module in the control bar I found that the Envelope Offset button was activated.  Once I de-activated that, the volume automation worked as expected.  I will have to educate myself a bit more on that functionality.

RonCaird
In the Mix module in the control bar I found that the Envelope Offset button was activated.  Once I de-activated that, the volume automation worked as expected.  I will have to educate myself a bit more on that functionality.

It took me a long time to figure out offset mode. It's basically to allow you to set a static gain or pan to a track in addition to any automation you might have. You learn to check that offset mode button all the time.
 

I enable offset to make a change, then after the change, turn it off to prevent these kinds of issues. You can also see offset mode is on when a + sign shows up next to a parameter, e.g., Volume+ instead of just Volume

Anderton
I enable offset to make a change, then after the change, turn it off to prevent these kinds of issues. You can also see offset mode is on when a + sign shows up next to a parameter, e.g., Volume+ instead of just Volume

I did see the plus sign and wondered what it was about.  Thanks.

Anderton
I enable offset to make a change, then after the change, turn it off to prevent these kinds of issues. You can also see offset mode is on when a + sign shows up next to a parameter, e.g., Volume+ instead of just Volume

I did see the plus sign and wondered what it was about.  Thanks.