Are you guys shifting live tracks forward to compensate for latency after midi or rewire tracks have been laid down?
My input latency is 8 millisec and the host says 10 millisec output latency,,is that 18 millisec it has to be moved?
When your grid is set for seconds,,is .018 , 18 millisec?
Also,,I noticed in some Pro-Tools sessions ,,samples are moved apart on different tracks from each other on purpose,,so their not always on the same beat,, I quess to eliminate that sequencer feel,,I wonder what would be an acceptable spread?
Adjusting tracks to compensate for latency
-
- KVRAF
- 8701 posts since 24 May, 2002 from Tutukaka, New Zealand
No.....my host compensates for latency. What host are you using?
And yes, I would imagine 0.018 means 18 mSecs.
An acceptable spread? Depends on what it sounds like.... if it sounds too out of time, then it is too much. I read somewhere that around 20mS is audible, although I don't know if that's actually true - I suspect it would be higher for most people. Certainly I notice 50mS latency when I occasionally forget to reset my host after mixing and I want to record something. I settled on 20mS as my standard latency figure as a compromise between easing up on CPU and getting good recording times. I don't generally notice much of any difference whether I record at 20mS or 5mS (although my crap playing may have something to do with that
)
And yes, I would imagine 0.018 means 18 mSecs.
An acceptable spread? Depends on what it sounds like.... if it sounds too out of time, then it is too much. I read somewhere that around 20mS is audible, although I don't know if that's actually true - I suspect it would be higher for most people. Certainly I notice 50mS latency when I occasionally forget to reset my host after mixing and I want to record something. I settled on 20mS as my standard latency figure as a compromise between easing up on CPU and getting good recording times. I don't generally notice much of any difference whether I record at 20mS or 5mS (although my crap playing may have something to do with that
)-
- KVRian
- Topic Starter
- 1103 posts since 19 Apr, 2004 from Trent Severn WaterWay
My gal has an acceptable spread ,but its not measured in millisec,,,,anyway,,I'm using Abelton3 and I don't see compensation anywhere,,but not sure,I'm checkin..When your recording to a backtrack does this compensation thing take out the latency at the start of the track?
I don't know how that works,,but it sounds handy,,
I'm experimenting with samples at 20 millisec apart to start with and you know,,,some interesting things are happening to the mix..but it sure is a hassle zooming in so far...
I don't know how that works,,but it sounds handy,,
I'm experimenting with samples at 20 millisec apart to start with and you know,,,some interesting things are happening to the mix..but it sure is a hassle zooming in so far...
-
- KVRAF
- 8701 posts since 24 May, 2002 from Tutukaka, New Zealand
I really don't know about Ableton - I would imagine it has some sort of compensation though. Most new hosts do. All they do basically is detect what length latency a plugin or VSTi or whatever had, and it delays all the other tracks by that same amount. Then it will self adjust each time another channel is added that has latency.
A read through the manual should hopefully tell you - it might be buried away deep though.
A good way of testing is by playing a midi VSTi. Put in some notes that start exactly on a beat (which makes it straight forward for spotting delays). Then add a read-ahead limiter or compressor as an insert FX, or something that you know has some latency involved - brick wall limiters generally do. Record the track to audio. Go into edit on the .wav, and the start of each audio event should start at the same time as the original midi notes - if they start a few mSecs later, then you know it doesn't have compensation
A read through the manual should hopefully tell you - it might be buried away deep though.
A good way of testing is by playing a midi VSTi. Put in some notes that start exactly on a beat (which makes it straight forward for spotting delays). Then add a read-ahead limiter or compressor as an insert FX, or something that you know has some latency involved - brick wall limiters generally do. Record the track to audio. Go into edit on the .wav, and the start of each audio event should start at the same time as the original midi notes - if they start a few mSecs later, then you know it doesn't have compensation