I modified the looper patch from GuitarExtended, to be used with footswitches to record and overdub.

One footswitch upon first click will begin recording and begin setting the tempo to determine the length of the table. Upon second click that footswitch stops recording and sets the table size. A second footswitch turns on or off the loop. If the loop is on, the first footswitch will begin recording overdubs. If the loop is off, pressing the first footswitch again will begin the process aknew, erasing the table and resetting the size.

I am getting clicking each time I record the loop. I'm guessing this is because I'm setting the table and the same time. Any ideas how to get around this?

http://www.pdpatchrepo.info/hurleur/looper.pd

do you get clicking every time the loop goes round, or only on the initial recording?

if you get it every cycle, then you most likely have an issue with signal discontinuity, like in this picture:

http://www.tek.com/sites/tek.com/files/u811871/discontinuity.png

the simplest way to avoid that is to ramp the volume of the first 5ms (or so) of the loop up from 0 to 1, and then ramp the last 5ms down from 1 to 0. So, when you hit record, also trigger this:

[0, 1 5(
|
[vline~]
|
[*~]

and feed your signal into the left hand inlet of that [*~ ]

then, when you finish recording, you want to send [0 5( to that vline~ object, then delay the actual end of recording by a further 5ms to wait for the signal to ramp down (you won't even notice the delay...5ms is nothing)

..

the other issue, is that resizing an array is pretty clumsy and causes quite a bottleneck. If you are mainly getting clicks only when recording, then i suggest that you should not actually resize the table. Just decide on the largest possible size for the table, and keep it static.
This means that you can no longer rely on the right outlet of [tabplay~] to trigger the end of your loop, so you will need to set up some basic counter which will reset when you get to your loop size.

It clicks when I first record. If There is a note playing when I start recording it clicks loud. If there is nothing playing the click isn't really noticeable. There is a vline object that ramps the input like you suggest.

Each overdub records without a flaw so I think it has to do with the table resize.

Yep, it's a similar bottleneck like you get when loading long sounfiles to tables. Pd just tries to complete the whole process, but if that takes more than the time for 1 bloxk of audio, then the next block of audio will be delayed - causing that pop you hear.

Not resizimg the table is your best bet.

I've edited a little more and gotten it to record and playback without clicking. I set the table size and then created a timer to trigger the tabplay to loop after the end of the first loop recorded.

This loop in it's original state, has a reverse function that now tries to play the full table size in reverse whether or not I filled it with signal. The way the reverse works is beyond me since I didn't create it, but I think since it records the table to a temp table, reverses it and then rewrites it to the original table, I would have to shorten and resize the table according to the timer length?

Any one have any ideas of how I could proceed?

Thanks,

http://www.pdpatchrepo.info/hurleur/GuitarExtended-Looper2.pd