Automation (problem between keyboard and chair) SOLVED

[banta24]

Hey there,

When recording automation in DP5 I can seem to get things to respond the way I want.

I'll try not to get too long winded...

Example - Riding the volume on a vocal

Say I want to have a vocal start at -2db and then rise to 0db during each chorus and head back to -2db for the verses. Here's what I'm doing:

1. Set the fader at -2db
2. Arm the automation record
3. Play the song
4. Type in 0db in the fader value box, but don't press enter
5. When the song reaches the chorus, I press enter, moving the fader to 0db
6. Type in -2db in the fader value box, but don't press enter
7. When the song reaches the end of the chorus, I press enter again, moving the fader to -2db

I repeat this process for the song. When I go back through it, the volume curves are not what I inputted. The automation apparently doesn't record the fader's initial position and subsequent moves are not recorded when I type in the value and press enter at the point I want the automation to change.

What am I doing wrong?

I keep coming back to my experience with Samplitude, which would always show your automation in its initial position, if you hadn't recorded any automation yet. Can I do this in DP?

What I really want to do is select Volume, Pan etc. from the dropdown list in the soundbite window and see an automation line for the current state of the track. i.e. If I have not made any pan automations, there is a line down the middle of the soundbite window that I can simply enter a couple of points on and manipulate them.

Sorry for the long post. I'm working on some mixes for a client and really want to make my workflow more efficient in this area.

Cheers!

[Dan Walsh]

maybe stating the obvious here--but--did you take an automation snapshot at the beginning of the track?

[FMiguelez]

.

I'm sure if you modify your workflow you will obtain the results you want.

All you have to do is touch the fader BEFORE you type the value in the field. I do this ALL the time. The second you touch the fader (or knob), the proper automation will appear at that point (the "initial" value). So touch the fader first, then click and type a number, and when you hit enter, you will then see the correct curve. This will work with ANY parameter. And you just need to touch the fader once for the first time (if there's no current automation in the track for the needed parameter).

You don't really need to take a snapshot first. But if you needed to, this could be accomplished in a couple of seconds anyway.

So, does this make things any better?

[FMiguelez]

.

Oh, and thinking about it, you could do this 8x faster at least... you are automating in real time. That takes as long as the sequence plays...

Why not trying the "r" trick instead? For this you would need to take an automation snapshot first if there's currently none (4 seconds tops).
Suppose you will automate volume for all tracks for a certain section. Make all the desired tracks visible in the GE. Select volume while you press option (all tracks change to volume). Drag your time range selection. Press the snapshot shortcut. Set the 3 parameters as needed. Press enter. Voila. In 3-4 seconds all your tracks will display the value for volume for that range of time.
Needless to say, this is only if you haven't done any automation for the needed tracks. If they contain the automation, you can skip this and go straight to:

Now, all you have to do is select a straight horizontal line from the tools, press "r" and drag above or below the current volume value for any track. The result: this will reshape the automation. If you want to add 2 dB to the chorus of the vocals, zoom out enough, press "r" and drag above the current volume value (a little above). Press shift as you drag to constrain to perfectly horizontal moves.

Sounds complicated, but you could turn up and then turn down the volume for the vocals for the chorus in literarily 3 seconds instead of doing it in real time.

[Dan Walsh]

.

Oh, and thinking about it, you could do this 8x faster at least... you are automating in real time. That takes as long as the sequence plays...

Why not trying the "r" trick instead? For this you would need to take an automation snapshot first (4 seconds tops).

Thanx man--now I just learned a whole bunch

[FMiguelez]

.

Oh, and thinking about it, you could do this 8x faster at least... you are automating in real time. That takes as long as the sequence plays...

Why not trying the "r" trick instead? For this you would need to take an automation snapshot first (4 seconds tops).

Thanx man--now I just learned a whole bunch

My pleasure, Dan
Glad you found it useful.

TO THE OP:
If this solves your problem, please edit your thread title. Just add: [SOLVED].
Thank you.

[banta24]

Thank you so much for the insight!

I'll give all of your suggestions a shot on the next song

I've been getting used to DP in general, but the automation has been a real pain in the butt. I'm looking forward to trying the "r" trick.

The multiple track selection idea is great too! Just this afternoon I was automating the sends from 4 drum tracks and did a separate pass for each track. Next time I'll do them all simultaneously.

Once again, thanks for your detailed responses!