Slow response to PT automation

[sphereman]

Not sure if this has been discussed, but ive noticed that when writing automation in PT with either the MC Mix or MC Control, it seems as if theres a lag from physically moving the fader to the response time in PT. Its similar to hui protocol over midi. I was under the impression that Eucon via ethernet had fast response times. But if i make a swift fader move, its always shows up a bit late in PT. Its been like this for several versions of PT and Mac OS versions.

HD3
Mac Pro Nehalem
PT 10, OS 10.6.8

[jesse p]

How late is it compared to your hardware buffer?


I know that Nuendo compensates for hardware buffering and will subtract that amount of time from the placement of the automation data, not sure if protools does that.

[sphereman]

Well its not late like it is on a native rig. Where you see the volume automation graph move back when you hit stop. This is a real time lag when using the MC Control or Mix. Although Ill check the buffer and see if maybe thats it. I rarely change it on the HD rig. I think it sits at 256k.

Thanks

Mills

[sphereman]

Certainly on my Mac Book Pro, theres a lag on the placement of the automation and it seems directly related to the buffer size. Dont think PT has a compensation setting for that. On the HD rig though this is real time. To reiterate from my above post, it can be when the automation is read only as well. You can see that your pulling the fader down for instance say before a certain snr drum hit and still hear it, even though im sure the fader is down before hand. ?????