Loop point introducing artefacts when timestretch is active

Hello everyone, I got my Octatrack 2 weeks ago and the goal being to use it in a DJ format as documented in many places (manual, Youtube, etc.)

I finally got perfect loops working (in Slice mode) - setting Slice START visually and setting Slice END by calculating the sample count based on BPM. It’s quickest IMO and for electronic music from 120 BPM and up, it works really well.

I noticed that for a few of the songs / slices, artefacts are introduced (and quite audible too) once I play with the overall BPM (plus/minus 5 BPM). And the culprit being whether the slice had a LOOP POINT set or not.

Hence, for those slices and change of BPM where Timestretch would be doing its job:

  • START + END only = plays fine
  • START + LOOP POINT + END = artefacts introduced even before reaching the loop area

Has anyone experienced this?

ps: The workaround so far is to work without loop points and simply add more slices (and set LEN to 2, which should do the trick of playing into the next slice and looping the 2nd one - I’ll have to try it to confirm it works)

Welcome @riazb

I didn’t but I am curious about it. Possible to record a comparison example ?
I barely used loop points in 10 years with OT.

A workaround to loop point is to use 2 slices (Slice mode, LEN = 2 slices). The 2nd slice is played looped.
EDIT : ah apparently you found it. :wink:
So I can confirm it works, can’t remember the particular setting.
EDIT 2 Here it is : you have to set a loop point ! DOn’t know if it will work with timestretch…

2 Likes

Thank you - it’s nice to be on this forum.

The song in question is something I bought on Bandcamp so I’d hesitate posting even a sound bite here. Maybe I’ll try posting the smallest length which surfaces the artefact loud enough.

Re: the LEN = 2 trick, I’m going to try a few ways and confirm. If a loop point is needed on the 2nd slice as per your attachment, it’s likely I’ll avoid the artefact(s) on the 1st slice but inherit them on the next (looped) one.

I’ll play around a bit first.

1 Like

A loop point is indeed needed on Slice 2 else it loops all the way back to Slice 1.

I noticed that introducing LEN = 2 and a Loop Point on Slice 2 brings artefacts to Slice 1 even!

I’m going to try a couple of other songs and have a listen. I’m (seriously) hoping that via some solid bad luck, I picked a song that brings up those issues and I won’t see this elsewhere.

1 Like

@riazb if you want a specific tempo, you can also use timestretch, resample, then disable timestretch and make you loop points.

1 Like