I am working on a loop pedal patch and I get this grinding/crackling noise when I delete the current loop. I think I have narrowed it down to the "resize" function. I have two loops that get reset to 0 and then they are resized to a much bigger array. I have attached a picture of the message box that creates the noise. I am using 128 block size with a delay of 12ms.

I am using an Odroid-XU4 running Ubuntu and have not been able to recreate this on my windows machine. I have a tried a workaround that mutes the audio and turns it back on which does get rid of the crackle but in a live setting I would be playing music while deleting the current patch so I can't have the audio dip all the way out..

Any help or suggestions would be greatly appreciated. Thanks

resize does create a "crackle" in my experience too.
One work around in your case perhaps would be to use delwrite~ and delread~ in aloop, something like this: liveloop~.pd
When you call this abstraction you need to specify the buffer size in ms which will be your maximum loop length.
I'm not exactly sure what you want to do but I hope this helps somehow

thanks allister! I will try this when I get a chance.

I’m also working on a looper pedal using a RPI3. It is based on Katja’s suggestion to use poke~ for writing driven by counter~.
Erasing a bigger array always crackles on my pi even with volume down. [*~ 0] I guess because there is a cpu spike.
I use another poke~ to zero the array, just increase the index value so it is a bit earlier than tabread~.
I don’t resize arrays, I just manipulate the min and max points of the counter~ object.
Right now there are 9 arrays, 120seconds long, running parallel without any problems.
( note : replaced [ wrap~] with [expr~ $v1%$v2] , somehow wrap~ produced incorrect, non integer index values )

@royal_orchestra interesting! I am using alfaloop (http://www.pdpatchrepo.info/patches/patch/155) but if you care to share your approach please do!

Cheers~