Automation question !!!

Shooshie · Post by **Shooshie** » Wed Dec 21, 2005 9:15 pm

Nahhh... no work at all on the CPU. It just inserts the points of your faders, pan pots, etc. Whatever you have chosen in the Automation Setup, which generally you only set once for your preferences. (though you can reset it often to get fancy)

By the way... do you want to solo all tracks? Hold down the COMMAND key, and click Solo on a track. All tracks but THAT one will solo.

Want to turn off all solos, except for one track? Hold down the Option key and click on the track you want. It will solo and all other tracks will turn off. This same principle works for mutes, automation, and even track selection in the Edit windows:

Option Key = select only the one you click
Command Key = select all BUT the one you click

Shooshie

Tim · Post by **Tim** » Thu Dec 22, 2005 5:12 pm

vudoo wrote:Thanks Sooshie,

Yeah, my head is still in the PT mode. BTW, when you take a snapshot of your initial mixer setting, does this impose more work on your CPU ??? and DP does not have an autoread mode right ?? therefore the automation play button has to always be activated after you've written automation ( of course unless you want to disable automation ).
Thanks again everybody.

Auto Read means read automation, in other words, automation on.
So yes, DP does have an "Auto Read" mode. It is when the blue triangle automation play/read/on/off button is lit.

Tim · Post by **Tim** » Thu Dec 22, 2005 5:15 pm

Shooshie wrote: Want to turn off all solos, except for one track? Hold down the Option key and click on the track you want. It will solo and all other tracks will turn off.

I hate when I do that only to find that it wasn't in solo mode.

Tripp Sprague · Post by **Tripp Sprague** » Thu Dec 22, 2005 9:08 pm

here's what I do:

in DP, work up a rough mix
in mixer, have tracks visible that I want to automate
hit snapshot button, hit OK
for all those tracks, enable automation
in sequence editor, make those tracks visible
hold option key, choose to view volume (all tracks will show volume)
start making volume changes

Mugambi · Post by **Mugambi** » Fri Dec 23, 2005 12:04 am

studiodog wrote:This is how DP works. No auto data until you insert it.
To do this across multiple tracks use a snapshot. Only snapshot the data you need though. No point generating a lot of unnecessary data.

On a single track just enable auto record, press play, and click on the fader.

You now have volume data at the level your fader was at.

I wanted to chime in here as I have a problem with how the automation works in DP. I visited the DP rep in LA with my issue and he could not understand or think it was logical to have the volume layer mirror the faders levels before you actually insert info. Of course I thought the opposite. I can't get my hands around the automation and the grid mode. Why can't you snap everything to the grid when you are in grid mode? It was interesting to see some of the responses to this post. PT and DP definitely have different philosophies on how they accomplish these tasks. I keep telling myself do not compare but it is hard when some of the simplest tasks requires in my opinion, too many moves. You've guys have been great and I am definitely enjoying DP more but there is still frustration. We all know what DP does great. I'm talking about your basic looping, automation, keeping edit start points, going back in forth between window, markers, etc. I can't seem to streamline my work-flow after all these months. Am I missing something?

Thanks,
Mugambi

studiodog · Post by **studiodog** » Fri Dec 23, 2005 12:52 am

Mugambi wrote:I visited the DP rep in LA with my issue and he could not understand or think it was logical to have the volume layer mirror the faders levels before you actually insert info.

Why would you want the program to insert auto data on it's own?
I don't want ANY automation data written anywhere unless I choose to do it.
DP doesn't do this, I assume ProTools does,that's what I gleaned from the post I quoted a portion of.

Point being, I want the software to respond to my input, not to assume that I want some data written in the sequence before I'm good and ready to commit to that.

Or I could just be giddy that I don't have to work till after Xmas, or is it XHoliday here? I've never been PC before so why start now...

Mugambi · Post by **Mugambi** » Fri Dec 23, 2005 10:19 am

studiodog wrote:
Mugambi wrote:I visited the DP rep in LA with my issue and he could not understand or think it was logical to have the volume layer mirror the faders levels before you actually insert info.
Why would you want the program to insert auto data on it's own?
I don't want ANY automation data written anywhere unless I choose to do it.
DP doesn't do this, I assume ProTools does,that's what I gleaned from the post I quoted a portion of.

Point being, I want the software to respond to my input, not to assume that I want some data written in the sequence before I'm good and ready to commit to that.

Or I could just be giddy that I don't have to work till after Xmas, or is it XHoliday here? I've never been PC before so why start now...

I agree with you about not wanting data written, I guess I was not very clear. The volume data in ProTools is always active for your editing once you have selected the volume layer and the default auto read mode. You make your move, you're done. It just seems easier and less hassle to me. For my brain, it's more comprehensive. I've tried your suggestion of arming automation in DP and clicking the fader though. I loved that! Volume info! I was actually writing a quick fader move and then going back to clean things up. Anything to make things go faster in DP I'm all for. Thanks.
[/i]