Ableton Looper bad really sync (help)

[nilsemil]

Ok, have worked on this for years and i'm never able to get it to work.

I want to create a Boss-style RC-50 looper with much better sound and options in Ableton live using the looper. The problem, the looper do not sync.

Here is an example, i can make a video version of it if necessary, but i am playing back a cr78 snare and recording it into three different channels of Looper.

As you can hear, with minimal taxing on the processor, still the looper is immediately out of sync. You can hear the flamming of the snare in the three different tracks, and the real cr78-plugin included also.

Could this ever be addressed?
What can i do about this? Latency compensation doesnt seem like a great way to go, since those numbers differ on different CPU taxing.

in short. HELP!

ADDITION: when rendering it down to a bounced file the flam is much less of a problem, so its in the playback state (which is crucial to looping) the problem occurs..


couldnt find how to attach a file, here's a link to SC.

https://soundcloud.com/nilsemil/bad-syn ... er/s-G353d

https://soundcloud.com/nilsemil/bad-syn ... er/s-G353d

(i'm in parallell working on same setup on Elektron Octatrack, but it has it's own limitations and known bugs, would love to have this one working in the end)

[Stromkraft]

Could this ever be addressed?
What can i do about this? Latency compensation doesnt seem like a great way to go, since those numbers differ on different CPU taxing.

No, they don't. This is not how latency compensation work. Unfortunately I don't use looper myself.

It's really beyond me why Ableton wouldn't make it dead easy to record and loop into a succession of tracks set to a prefixed length or a length based on the first track (clip) or a multiple of this.

Are you running tracks without delay compensation? There's you answer. Turn it back on or deal with it manually. With it off it's your job to deal with this.

[TomKern]

Strange, I have no issues with Loopers going out of sync. (and I use them a lot too). Very stable.

And my Looper shows a latency of 0 samples, so I don't see how that can lead to the effect you are observing.

Is there anything special in your set-up that you didn't mention yet?

[siliconarc]

I'm no expert on loopers here but i imagine that that slight flamming is to be expected. My guess is there's a tiny time or pitch shift each loop, to avoid phase cancellation. If there weren't tiny fluctuations in time/pitch, each loop would cancel out the previous one (in your audio example). These are unnoticable in 'normal' use but not here. Unless im not hearing something more serious..? Ipad listening

[Stromkraft]

If there weren't tiny fluctuations in time/pitch, each loop would cancel out the previous one (in your audio example).

This would be true only if the same loop played back polarity switched to itself. How often does this happen? Close to never unless you do this intentionally.

[Angstrom]

I've experienced the looper going out of sync after about 30 or 40 minutes, under circumstances where theres an M4L device preceding it and the track is armed and the playthrough optimisation option is active (I forget what its called) and the instrument rack is complex. But I've never experienced immediate flamming in a basic setup though. Thats odd.

[siliconarc]

If there weren't tiny fluctuations in time/pitch, each loop would cancel out the previous one (in your audio example).

This would be true only if the same loop played back polarity switched to itself. How often does this happen? Close to never unless you do this intentionally.

*doh* yep you're right
posting from bed with hangover not recommended

[Klaus Kobald]

Still in ableton live 10 they did not fix that looper issue. it´s an open ticket since 2011!
If you have a looper running in overdub mode with 100% feedback it runs out of sync within 1-2 minutes!
That really sucks and they don´t give a shit about it!

[ethnotronik]

I have just came across this issue as I started using looper in ableton live 10 (most recent) MBP 2012 16gb RAM OSX

I have a big set, over 150 tracks, effects on the master channel, subgroups, vst synths, audio clips...

As I start looping, when the looper plays back recorded audio "glued" to the grid, I hear lot of latency immediately. My project buffer is at 512, and I think it has to be there at all times in this live set.
I have tried compensating on the looper audio track arround -40, but it seems to me that this value is variable every time CPU is doing something different?!
Does anyone have a practical solution, or this has been an ongoing problem in live?
Is there a workarround?
Is there a definite way to know the proper compensation values?