OK, I cut all automation from a project and started over mixing it.  Everything was fine.  I made several test mixes (exports) and each time made some minor tweak.  The last time, the mix was a disater: Master red-lined, bass level was completely different, etc.
 
And now I am back to the problem I documented before.  The kick says it is at -11, but the fader is at 0, and it is very loud.  All the other instruments display anomalies like this.
 
I tried touching O off and on to see what happened.  Most of the faders did not move when I went into offset mode, but, oddly, the three tracks that were most screwed up all went to 0 db which would indicate no offset.  In other words, it's backwards.
 
Essentially I wasted the entire day.
 
What the hell...

We would need more detail, step by step procedure from a newly created project etc to get to the heart of this I suggest. I half understand what you say, but you will first need to rule out whether this is project specific or not anyway.

Hallo, Konrad, Happy New Year to you and yours.

I may have missed something in the other thread, and I know we have touched on this before, but have you checked that all tracks and busses are output to Master bus? And checked any odd sends?

I know you would have tried this, but I'm just clutching at straws.

Thanks.  Everything is going to master.  In essence, the mix was fine.  I clicked on a node to lower a guitar part one db and then re-exported and suddenly everything was way off.  Strange.  Even supposing I touched O for Offset (which I don't think I did), that would not automatically change the level of lots of tracks whose faders weren't touched.  Weird.
 
Unfortunately, I have done a ton of work on this track over the months so I can't recall everything that happened, but I do know this odd behavior has happened on other projects.  I am going to cut all automation, make sure the offset is zero on every track, and then start over.  Frustrating, but not sure what else can be done at this point.

Did you have more than one track selected when you made the node adjustment?
 
Unlike track controls, nodes will respond on all selected tracks without holding down the ctrl key as you would have to when quick grouping controls. That's because the nodes within the selected range and tracks are all selected thus respond as one.
 
A bit late for you on this project now but a tip I use is I to "save as" at landmark times of a project so I can always get back to a certain point. Each project I am working on has a main save name such as "My Project" and then others such as "My Project - Tracking finished", "My Project - Comping Finished", "My Project - Automation finished", etc. etc.
 
HTH

FastBikerBoy
A bit late for you on this project now but a tip I use is I to "save as" at landmark times of a project so I can always get back to a certain point. Each project I am working on has a main save name such as "My Project" and then others such as "My Project - Tracking finished", "My Project - Comping Finished", "My Project - Automation finished", etc. etc.

Another great FBB tip.

If I'm giving you tips Craig I am in awe.
 
I have learned loads from you in the form of videos, forum posts and your "Sound on Sound" column of course. Thanks for all of that long may it continue.

Many of us not only appreciate your in depth knowledge of Sonar but the manner in which you share it Karl.

FastBikerBoy
If I'm giving you tips Craig I am in awe.
 
I have learned loads from you in the form of videos, forum posts and your "Sound on Sound" column of course. Thanks for all of that long may it continue.

Well thanks for that! Sonar is such a deep program, with such sophisticated capabilities, that getting the perspective from multiple people on how to use it is helpful to all of us. For example I use screen sets and they're great, but I appreciate that you've really explored them in great depth, and shared the results. So now I can just hop on to your part of the "screenset learning curve," not have to do all the exploratory work you did, and reap the benefits of what you've learned.

FBB and Craig are both awesome and we are lucky to have them participating here.
 
About the Save As, I always saved multiple versions of my project along the way, but then a certain company told me that my string libraries (Vienna and Hollywood) were performing poorly because I needed more free disk space.  So, I took a Saturday to move all but the most recent versions of every song to an external drive, keeping only the latest version of each on my internal drive (and backed up externally, of course).  I then defragged the disk.
 
This all made absolutely no improvement in the string performance.   I seemed to be cursed.
 
I think the only solution is to buy a new PC (with SSDs for sample libraries), and install X3 fresh.  (I will also try to install both my V-Studio I/O and MOTU Interface so I can toggle between the two. There is a theory going around that the V-Studio I/O causes a lot of my problems, but I do not believe it.   The issues seem to be Sonar related and I know of no other Roland interface users with similar problems.)
 
Needless to say, this would be costly and the time would be significant, since my Vienna libraries alone will take two days to install, and I have many other libraries.  I will also have to go through all the onerous authentications (like NI!) and make sure eLicenser and iLok are working.