John
I've been using automation from back in the Pro Audio days. I used the Studio Mix back then. I can't say the W and R buttons have been even a slight problem.
.....
Now its about something entirely different in that some few seem bothered that by default reading automation is on. Really! Is that a real problem?
I'm sure you'll understand this, but I only wanted to let Keith (and OP) know that having automation on by default isn't helpful for everyone, and that the current behavior could be changed in order to make SONAR an even more user-friendly DAW. As for the potential user confusion (which actually happened to me) I mentioned in the second half of my first post, it comes from the inconsistency between the state of the track's R button and the state of the lane's R button. I don't know how the track's R button behaved during the period between Pro Audio and X1 (since the only versions I owned during the period were version 2 and X1, and I didn't really use the latter), but at least the automation lanes introduced in X2 confused me when I started re-learning automation in SONAR a year or so ago. The videos below will help people reading this thread understand why it's confusing (at first at least).
1. As you can see, for those who prefer to disable automation read by default (for easy identification of automation written tracks), the inconsistency between the R buttons is confusing. (In this example, volume and pan are the only automation envelopes/lanes I created)
2. I removed the default EQ from the ProChannel module sometime ago, so the track only contains three automation parameters (volume, pan and automated mute) by default. Notice that the track's R button is still half lit after I removed the envelope/deleted the lane (this could be a bug, though).
So I suggested the improvement that would make some of us happy, without hurting the workflow of majority of users.