Hello,
I have had trouble with some hardware synths recently not being in time with Live so I have been trying to implement the 'Track Delay' feature which is not fun at all. I then went to 'Option -> Reduce Latency When Monitoring' and it has magically fixed all of my delay.
I can not find this Option in the Live manual to help me understand what it is doing. Can anyone help?
Options -> Reduce Latency When Monitoring - ?
Re: Options -> Reduce Latency When Monitoring - ?
reduce latency when monitoring. An explanation.
usually, during playback, all the tracks are delayed so that they align. so lets say we have 3 tracks :A, B and C. Imagine track A is a resource hog and has a latency of 200ms, B has a latency of 13ms and C has a latency of 50ms. Now it would be no use if they all played back like that, they would be out of sync with each other so Automatic Plugin Latency calculations put them all in time. What happens is : everything is delayed to the longest track latency time, that way A=200ms, B=200ms and C =200ms. all in time.
Now, lets say you arm track B for recording, you want to play the electric piano sound which is on track B. We know from the above that Track B is being delayed by 200ms to make all the tracks be in time with each other, so it's going to be uncomfortable to play. This is where "reduce latency when monitoring" comes in. It decouples the armed or monitored tracks from the latency calculation of the whole set. So while B is armed the latencies are now A: 200ms, B:13ms , C:200ms
likewise if you armed B and C to record the latencies would be A: 200ms, B13ms, C:50ms. because B and C are now ignoring the increased latency of the entire set and are instead reducing their latency to their minimum possible, while monitoring.
The magic of computers means that when you stop recording, or take these tracks out of monitor mode the audio (and in 9.2 beta the automation) will be put back in time. Everything will once again be 200ms, in sync
usually, during playback, all the tracks are delayed so that they align. so lets say we have 3 tracks :A, B and C. Imagine track A is a resource hog and has a latency of 200ms, B has a latency of 13ms and C has a latency of 50ms. Now it would be no use if they all played back like that, they would be out of sync with each other so Automatic Plugin Latency calculations put them all in time. What happens is : everything is delayed to the longest track latency time, that way A=200ms, B=200ms and C =200ms. all in time.
Now, lets say you arm track B for recording, you want to play the electric piano sound which is on track B. We know from the above that Track B is being delayed by 200ms to make all the tracks be in time with each other, so it's going to be uncomfortable to play. This is where "reduce latency when monitoring" comes in. It decouples the armed or monitored tracks from the latency calculation of the whole set. So while B is armed the latencies are now A: 200ms, B:13ms , C:200ms
likewise if you armed B and C to record the latencies would be A: 200ms, B13ms, C:50ms. because B and C are now ignoring the increased latency of the entire set and are instead reducing their latency to their minimum possible, while monitoring.
The magic of computers means that when you stop recording, or take these tracks out of monitor mode the audio (and in 9.2 beta the automation) will be put back in time. Everything will once again be 200ms, in sync
Re: Options -> Reduce Latency When Monitoring - ?
Thank you for your response. A great help!
-
graphixsounds
- Posts: 164
- Joined: Wed Oct 23, 2013 9:02 pm
Re: Options -> Reduce Latency When Monitoring - ?
Angstrom wrote:reduce latency when monitoring. An explanation.
usually, during playback, all the tracks are delayed so that they align. so lets say we have 3 tracks :A, B and C. Imagine track A is a resource hog and has a latency of 200ms, B has a latency of 13ms and C has a latency of 50ms. Now it would be no use if they all played back like that, they would be out of sync with each other so Automatic Plugin Latency calculations put them all in time. What happens is : everything is delayed to the longest track latency time, that way A=200ms, B=200ms and C =200ms. all in time.
Now, lets say you arm track B for recording, you want to play the electric piano sound which is on track B. We know from the above that Track B is being delayed by 200ms to make all the tracks be in time with each other, so it's going to be uncomfortable to play. This is where "reduce latency when monitoring" comes in. It decouples the armed or monitored tracks from the latency calculation of the whole set. So while B is armed the latencies are now A: 200ms, B:13ms , C:200ms
likewise if you armed B and C to record the latencies would be A: 200ms, B13ms, C:50ms. because B and C are now ignoring the increased latency of the entire set and are instead reducing their latency to their minimum possible, while monitoring.
there should be a video tutorial for this- a lot of people are curious about this
The magic of computers means that when you stop recording, or take these tracks out of monitor mode the audio (and in 9.2 beta the automation) will be put back in time. Everything will once again be 200ms, in sync