Latency removed from looper recording

[baseinstinct]

When a looper is appended to a string of fx and a loop gets recorded, the playback features no latency.

However, if you drag the loop to a new track, the audio is visibly and audibly postponed by several miliseconds.

Has anyone noticed that? It has been the same in previous versions, like 8, 7, too.

[Orbit-50]

I decided to try it out today and I discovered this problem myself. I'm sniffing around for information.


.-.

[Orbit-50]

Welp, as usual there's no information on a workaround anywhere to be found so I did my own research. I found out that before you record, you have to adjust your audio buffer size to basically nothing. Then the dragged audio loop from Looper with be right on the money! This work around kind of sucks, but at least it's possible to get tight loops out of Looper. I'm happy for that!


.-.

[baseinstinct]

Find it incredible the issue has not been noticed more widely - been there from looper's day 1.

If such manipulation with latency would be necessary as a workaround, a simpler way which proves effective surprisingly often is to record in one take two or three repetitions in a row and loop one of them. Then, move the start marker to the first transient. Obviously does not work with phrases which do not start precisely on 1.1.1; then you can record a click and later remove it

What is the strangest is that the recorded loop is perfectly intact with the song when still in the looper. Apparently, it uses latency compensation on the playback process and not on recording, which seems so ease to fix.

[Orbit-50]

What is the strangest is that the recorded loop is perfectly intact with the song when still in the looper.

That's the part I found very strange also. Hopefully they will fix it next week after they read this thread.



.-.