Ableton Forum

I think my conclusion is it's a CPU problem or problem caused by how looper uses resources.
Changing a few parameters such as buffer size, giving priority to background services in Windows, freezing a few channels seemed to have fixed the problem.

It's hard to pinpoint. Funnily enough without changing all above parameters, the CPU level on Live never seems to go beyond 55% on this particular track so can't be certain where the problem is...

55 would be higher than I am comfortable looping live with.

'It's hard to pinpoint. Funnily enough without changing all above parameters, the CPU level on Live never seems to go beyond 55% on this particular track so can't be certain where the problem is...'

In my tests, %55 in ableton means its actually more like %70-%80 which is to high to expect stability.

I also have the pops n clicks (made from punching in and out when making loops) even though my cpu is about %30.

Its something to do with the midi triggering thats creating it for me.

Take a look at what your default warp properties are set at - beats, re-pitch etc. Might help.