Question regarding FX automation Pro Tools

JayB

Member
Oct 10, 2009
3,230
0
36
open.spotify.com
Hey guys, quick question. I'm attempting to do a bit of FX automation in Pro Tools, but things are not working out that well. For instance, there's a part where I want to use a telephone effect over the drum bus, and I have that working with automating the master bypass, but for some reason it's not "instant". What I mean is that the effect doesn't kick in when it's supposed to, about an 8th note later. Same with when it's supposed to end, it stays for a split second longer. How do I fix this?
 
some kind of latency issue?

don't know how you have it setup and all but as a quick workaround you could always just route all the drums to a new stereo track and print the effect. Then you wouldn't have to bother with the automation, all you need to do is mute all the main drum tracks in that/those spots
 
^ I was thinking latency, but I have much more complex effects than a simple eq going on in the mix, and none of them are kicking in late like this. I was thinking about printing the effect but I'd like to know how to do this properly, it would just make the creative aspect of messing with effects much more fun/ easy.
 
go into the pencil edit tool and mess about with where the effect come in . so the drum buss change the view from volume to fx parameter i ibelieve its called
 
go into the pencil edit tool and mess about with where the effect come in . so the drum buss change the view from volume to fx parameter i ibelieve its called

I'm doing this already. What I'm saying is that the effect is delayed, it's not starting and stopping where I tell it too when I automate the master bypass.
 
But do you hear the latency or you only see the latency of the fader? Because I notice the latency on the fader too, but the sound usually changes correctly. Anyway you can try to switch back a little the attack point
 
You can also try creating a new session and importing only the tracks and busses for the drums. Then try duplicating the error. If it works fine in the new session it's possible you're master session is just bogged down from everything else and you're seeing the latency in the fader more than hearing it
 
But do you hear the latency or you only see the latency of the fader? Because I notice the latency on the fader too, but the sound usually changes correctly. Anyway you can try to switch back a little the attack point

Yeah I can hear that the latency is really bad. I'll try and bounce a mix so you guys can hear what I'm talking about a lil later.
 
You can also try creating a new session and importing only the tracks and busses for the drums. Then try duplicating the error. If it works fine in the new session it's possible you're master session is just bogged down from everything else and you're seeing the latency in the fader more than hearing it

I don't know what you guys mean by seeing the latency in the fader. I'm hearing that the latency is bad, that's how I noticed this in the first place.
 
Write your automation correctly and record the result (drums only). You'll see how much the effect is delayed. Then you rewrite the automation but earlier, actually with the same amount than the delay.

But what Skinny Viking said in his first post is the simplest thing to do in that case imo.
 
Thanks for the tips guys. I guess it is a latency, it's just weird that none of the other effects are delayed. Maybe because they are all consistent, like vocal plugins etc there appears to be no latency. I believe in PT8 LE there is no delay compensation
 
Thanks for the tips guys. I guess it is a latency, it's just weird that none of the other effects are delayed. Maybe because they are all consistent, like vocal plugins etc there appears to be no latency. I believe in PT8 LE there is no delay compensation

No there is no adc

Don't know how big your session is but if you wanted to upload it I could always try it on my system (using same as you) and see if I have the same problem. At least I could get a better idea if how it's all setup and where the problem might be

And save yourself time typing ...

Carlos ;)

But everyone just calls me Los
 
No there is no adc

Don't know how big your session is but if you wanted to upload it I could always try it on my system (using same as you) and see if I have the same problem. At least I could get a better idea if how it's all setup and where the problem might be

And save yourself time typing ...

Carlos ;)

But everyone just calls me Los

Thanks for the offer man, but the session is huge. It's an entire album being mixed in one session. I think what I'll do is just print the effects like you originally said, if I have any problems then I'll be sure and post here again.
 
The latency your getting with regards to automating an insert bypass corresponds to your HW buffer size. The lower the buffer size the less latency you'll have. If I'm doing similar automation, I usually select Slip Mode and write the first automation breakpoint a little before I want the action to take place. You may have to move it around a little but you'll find where it will work best. You could also buss the drums to an audio track and record the result of the automation to determine exactly how far ahead you have to place the breakpoint.

-kacey
 
The latency your getting with regards to automating an insert bypass corresponds to your HW buffer size. The lower the buffer size the less latency you'll have. If I'm doing similar automation, I usually select Slip Mode and write the first automation breakpoint a little before I want the action to take place. You may have to move it around a little but you'll find where it will work best. You could also buss the drums to an audio track and record the result of the automation to determine exactly how far ahead you have to place the breakpoint.

-kacey

Sounds like a good idea, I'll probably give that a try. I have the HW buffer size up pretty high when mixing.
 
The latency your getting with regards to automating an insert bypass corresponds to your HW buffer size. The lower the buffer size the less latency you'll have. If I'm doing similar automation, I usually select Slip Mode and write the first automation breakpoint a little before I want the action to take place. You may have to move it around a little but you'll find where it will work best. You could also buss the drums to an audio track and record the result of the automation to determine exactly how far ahead you have to place the breakpoint.

-kacey

This. Just start and end the automation a bit earlier to compensate for the delay.
 
Control click on the fader volume level readout down the bottom to see your delay in samples. It may be in the thousands. Adjust accordingly.