Besides finding/using zero crossings in the loop audio you could as well highpass filter the incoming audio before looping with an [svf~ 100] and a second [svf~20] after loop audio output.

Hi Jayrope,

Sorry but I don't get it.

could you tell me more or post an example please ?

thx a lot olivier

Quote: jayrope wrote on Mon, 27 October 2008 14:51 ---------------------------------------------------- > Besides finding/using zero crossings in the loop audio you could as well highpass filter the incoming audio before looping with an [svf~ 100] and a second [svf~20] after loop audio output. > > ----------------------------------------------------

Quote: Olivier Sebillotte wrote on Mon, 27 October 2008 06:17 ---------------------------------------------------- > Hi, > Is there a way to get rid of audio clicks/glitches when I scrub in an audio file? > > I am talking about artefacts when I CHANGE the loop's start and/or end. ----------------------------------------------------

Here's a thread on the same topic:

And here is the fe.nocut~ abstraction mentioned in the thread which always works for me. It ducks the amplitude of a signal in its signal inlet when a message (in this case the start or end point) is passed through its message inlet:

Would you post this as a 4.6 compatible text version, too?

Thank you very much!

oop did it myself quickly:

hello Lewis,

thanks for the link

Actually I read it a few days ago but I didn't choose the solutions given there because they cause some pitch artefacts when you change loop lenght :( But I overlooked the solution from fe.

thanks to you and him I can achieve what I need now.

here is a patch where 2 grooveducks with and without fe.nocut~ are used.

BTW,now I am trying to get rid of the granular effect caused by amplitude modulation, it is a never ending story I guess ;-)