[PD] wavetables : tabosc4~ and tabsend~ compatibility problem

[julien.breval at tremplin-utc.net]

> You probably also get clicks? 

sometimes, but very few clicks actually

> In general it isn't very good to change
> the array read by a tabosc4~ on the fly. A better solution might be to
> drive a tabread4~ object by a phasor~ multiplied by the length of the
> array. This way you also won't have problems with the different array
> sizes. 

good idea, I will try this

thanks