White [R] does what?

I just don't get the white [R] on each track and what it does...
I have seen no difference in using it or not using it.
So what is it for and what is different between using it and not using it? 

It toggles "Read Automation" on and off.

Wookiee
It is for recording automation Dave000

The R is? I thought that automation was the A? And the Rs always turn on, on the when ever I create a new track the R is always on... when I record multiple tracks the R is always on when done recording. really makes know sense. lol but I had top ask. 
 
Thank you :)
  

Sylvan

Wookiee
It is for recording automation Dave000

Actually, the "W" is for recording (writing) automation, the "R" is for reading automation.

Sylvan

Wookiee
It is for recording automation Dave000

Actually, the "W" is for recording (writing) automation, the "R" is for reading automation.

Yeah, what I said ^ I will need to play around with them a bit more. Still don't get why new track default is set to on...  Thank you. :)

Sylvan

Wookiee
It is for recording automation Dave000

Actually, the "W" is for recording (writing) automation, the "R" is for reading automation.

Correct I miss typed and thought I went back and edited it but seems a second post happened and has been deleted.

It's on so if you open an automation lane and draw in a change you'll hear it.  If it weren't enabled by default you wouldn't hear any change.   You could also open the Help Module and read out a short description of what different UI elements actually do when you hover the mouse over them.
 
Keith

Dave if you click views and select the help module it will open up a window that will give an explanation about almost anything you hover your mouse over.
Track automation isn't really a Cakewalk thing, it's been a part of mixing for decades and is something you might want to get familiar with.
 
Rocky

Bristol_Jonesey
I'd be totally lost without Track/Bus automation. There are SO many creative possibilities.

+1
Im not sure how a human survives without automation.
its a musicians/engineers food (as in bread and water). you almost need it to live.
there's only so many things a compressor can do to control levels without the use of automation.
 
If your from the old analog days...Remember fader riding ?
that's what automation is, only it has 100 hands. for volume, panning, gain, mute, FX controls and more.
 
I can respect where your at Dave, but when you want to take your recording to the next level. read up on it.

Keith Albright [Cakewalk]
It's on so if you open an automation lane and draw in a change you'll hear it.  If it weren't enabled by default you wouldn't hear any change.

 
True. However, I find the current implementation (R button already enabled when the track is created) not helpful in my situation. I mean, how can you EASILY tell which tracks have written automation data in them and which tracks don't if ALL tracks' R buttons are enabled (lit in blue)?  
http://forum.cakewalk.com/Automation-Read-button-grayed-until-you-actually-entered-any-automation-m3226256.aspx
 
Of course, the Automation Lanes button on the track looks blue-ish when there is an automation lane or lanes in the track, but the buttons are not visible when the tracks are minimized (or when working in CV), and also automation envelopes can be created without creating any automation lane (yes, by using Edit Filter).
 
For this reason, all Automation Read buttons in my custom project template are disabled by default. I think that automatable parameters should be automatically read-enabled only when the user created the automation lane or selected the desired automation parameter from the Edit Filter drop-down.
 
I even suggest that no automation data (even if invisible) should exist in the track until the user creates it himself. You'll see what I mean by following these steps:
 
1. Insert an audio track.
2. Click the R button in the track to disable automation read.
3. Click the Automation Lanes button to create an automation lane (Volume).
4. Click the Add Automation Lane button to add a lane (Pan).
5. Click the two R buttons in the lanes to enable automation.
 
Notice that the R button in the track header is only half lit. This means that some automation parameter or parameters exist in the track although the user didn't create them himself. I think new users will find this behavior confusing.
 
And I still strongly wish for a customizable MSR module in the narrow track strip in CV. I really want to replace the Arm and Input Echo buttons with Automation Read and Phase buttons.
 
 

chuckebaby

icontakt
 I mean, how can you EASILY tell which tracks have written automation data in them and which tracks don't if ALL tracks' R buttons are enabled (lit in blue)?

There is an Automation Icon that shows up on parameters that have been edited.

 
Yes, but that's only for track/bus strip parameters. I automate plugin parameters as well. 

scook

icontakt

Keith Albright [Cakewalk]
It's on so if you open an automation lane and draw in a change you'll hear it.  If it weren't enabled by default you wouldn't hear any change.

True. However, I find the current implementation (R button already enabled when the track is created) not helpful in my situation. I mean, how can you EASILY tell which tracks have written automation data in them and which tracks don't if ALL tracks' R buttons are enabled (lit in blue)? 

The R button is not an indicator of whether a track has automation or not.

 
I know, but I'm saying that it can be used as an indicator. If there's any other way I can easily identify tracks/buses that only contain clips and/or just automation for plugin parameters, I wouldn't use the R buttons as indicators. And I wouldn't have suggested the above suggestion. 

icontakt
I know, but I'm saying that it can be used as an indicator.

You can use the button any way you wish but it is not the purpose of the indicator and suffers its own shortcomings. There is a limit to the amount of information a single button can convey.
 
 

scook

icontakt
I know, but I'm saying that it can be used as an indicator.

You can use the button any way you wish but it is not the purpose of the indicator and suffers its own shortcomings. There is a limit to the amount of information a single button can convey.

 
My suggestion was to have the track's R button to be automatically enabled when the user created automation data or lane. What negative impact would it have on the users who are happy with the current behavior? I'd like to know, because I might be missing something. 

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. Actually for me its been rather convenient having them.
I am unsure of a reason for this thread. If we look back at the OP it is my understanding that Dave didn't know what R was for. That was answered. 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? 
 
BTW Dave could have avoided this thread if he had just read the manual. Now there is a constant help showing what everything does. Apparently Dave can't be bother to have that on either.
 
I have always thought of the automation in Sonar as being one of its strengths.    

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. Actually for me its been rather convenient having them.
I am unsure of a reason for this thread. If we look back at the OP it is my understanding that Dave didn't know what R was for. That was answered. 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? 
 
BTW Dave could have avoided this thread if he had just read the manual. Now there is a constant help showing what everything does. Apparently Dave can't be bother to have that on either.
 
I have always thought of the automation in Sonar as being one of its strengths.    

That's kind of harsh ...