Latency

[Nubus]

I'm using PTLE. I have been nudging my overdub tracks by the exact amount of samples my buffer is set to. Do any of you do the same?

[johnS]

You mean when record a new track you scooch the old ones over? I have never done this, but then again latency is very poorly documented in my protools manual. You do this to keep the timing right with overdubs?

[Nubus]

I slide the new one.

[blnkbnkr]

I did when I used an mbox. The latency was really perceptible. Now that I'm on a 002r though, and use the low-latency monitoring option, I haven't bothered because it hasn't been so glaring. In minute, "feel" matters though, those 64 samples could make a difference... I'll have to try it.

[dagosto]

Being a Sonar 5 and MOTU 828mkII user and never having to worry about latency this seems so shotty on digidesigns part. I would not want to deal with this.

[dolivas]

ever since i've updated my recording rig to a iMac G5 i've had near zero latency recording with my Ableton Live and Tracktion combo, having a better processing core and enough memory and extraneous stuff helped out on this one.

[johnS]

Are we talking monitoring latency or latency "to tape?"

I get around monitoring latency by splitting the signals just before they hit the inputs on the recorder. The splits go to a crappy little Behringer mixer, along with the monitor outs from my 001, and then to the speakers/headphones for monitoring.

Does Pro Tools LE delay overdubs by a certain number of samples? I haven't noticed, but that would be bad. I guess it would be easy to find out. Just hit return to zero on the transport, arm a new track, and see if it starts recording at zero or waits a few samples.

[Nubus]

yes but it is an mbox only goof, and some of the early 002s i think. it has been fixed. My new thing is the amount of time taken to get to the far mic on guitar. i use one close and one further back, then insert a delay 100% wett on the close and dial it in to tast in mono. am i going mad?

[dagosto]

Originally Posted by Nubus

yes but it is an mbox only goof, and some of the early 002s i think. it has been fixed. My new thing is the amount of time taken to get to the far mic on guitar. i use one close and one further back, then insert a delay 100% wett on the close and dial it in to tast in mono. am i going mad?

I usually don't worry about that sort of thing because I feel that the sound is often enhanced by the phase relationships between a far and a close mic. If I am not happy with I move the far mic. If I don't catch it until after it goes to tape I nudge it until I like the sound.

[Nubus]

that is the way to make a cool image too, out of the distance between the two. I am trying to get thick mono-compatiblity though, and I really like the way the sound develops into the distance mic.
i've been backing one mic off about three or four feet.
why am I posting this under latency?