In Pd's help files, it suggests table switching with [tabosc4~] to avoid rewriting tables. However, when I do this, I get small pops in my audio upon switching. I assume these are from the tables switching when the values are far apart, causing the signal to suddenly jump.

Is there a way to make the table switch happen when the index of the table is at 0 where both tables have the same value (i.e. 0?)

I have made a workaround basically by fading between an inactive and active table. It's good enough for my purposes but it feels like I ought to be able to do this more elegantly.

Are you using the [array] object, or are you using the array from the menu Put -> Array? In the second case, you'll get clicks because of the graphic representation of the waveform. You might want to share your patch (preferably a screenshot of the part that you think is the culprit), so we can see in more detail.

@alexandros thanks for replying! I am using [table], not [array]. I've experimented with hiding the tables in subpatches to get around the drawing CPU issue, but still had pops when the tables were hidden. This is an interesting question, though, because my CPU usage never really spiked any further than around 10% when playing with this-- are the issues with tables being redrawn a CPU draw issue or is it that the table's data set actually changes more slowly when they are graphically redrawn?

Unfortunately, I have edited the patch fairly intensely to implement my workaround- and the patch was complicated to look at to begin with. I did some testing in a more simple environment, but was still getting this issue. I'll throw together something soon to demonstrate what I'm talking about because I'd really like to understand what's going on.

@Matt-Stalcup said:

In Pd's help files, it suggests table switching with [tabosc4~] to avoid rewriting tables.

I think the help file is simply wrong about this.

AFAIK click-free wavetable switching will require a crossfade, full stop. That is, your workaround isn't a workaround -- it's just the right way to do it.

I can easily reproduce clicks using the help patch's example -- so the help patch itself doesn't even "work" in this sense.

Is there a way to make the table switch happen when the index of the table is at 0 where both tables have the same value (i.e. 0?)

Basically, no. Control messages such as "set" are evaluated only at control block boundaries (default 64 samples). To guarantee that you're switching at the beginning of the wavetable cycle, you would have to be sure that you are at the beginning of the cycle for every control block. That would require a wavelength that is an integer multiple of the block size, which is extremely unlikely condition to satisfy.

hjh