I compared it to Cubase 5 and Reaper, both of which have the timing spot-on accurate. After you posted this, I was sceptical, but I went and did some research, and spent literally hours trying different options.

How much SE is affected by this problem depends on how much latency it has and/or on whether you put any other third party plugins in front of it.Д¬hanging your buffer size in preferences will have an impact on how much you hear the problem. But in some cases like CamelSpace and (I suspect) SE, the plugin's own latency is enough to spoil the timing. Typically the problem is only obvious if more than one plugin is put in front of a 'stutter' type plugin (because the more plugins, the more latency you get, the more the audio is out of time with the stutter). The result: SE will cut off the front of your audio and it will also be out of time with other tracks. But for the stutter to stay in time it's 'syncing' actually has to be shifted by the same amount that the audio is shifted. The stuttering effect in SE is synced to Live's transport. The audio passing through SE is effectively 'shifted in time' to compensate for the latency of the plugin. I think you might find that it is Ableton's fault. I guess if you need to increase the buffer at a later stage, the workaround would be to perform the effects, freeze, and dump to audio track. To be honest, I think that's not really Ableton Live's fault, and more to do with how the plugin works. Delie wrote:I noticed the same thing, with low buffer size it works much better.

Stutter edit manual