On Mon, 18 Jul 2005, David NG McCallum wrote:
Ah... I was actually using tabread4~ to do table lookup for waveshaping. Maybe there's a better way to do that...
hmm, I see. In this case you will have to scale the incoming signal accordingly. Think of the array size as of in milliseconds. e.g an array of 1024 has 23.22 ms length (1024/44.1)
Then scale your signal to fit between 0 .. 23.22 and send it to tabread4~
Is there a list of PDa differences somewhere that I didn't read?
greetings
Guenter
PS: I hope you do not need array drawing, this is still buggy.
Cheers, David __ _ _ _ _ __ ___ _ ___ __ _ _ _ ____ __ Music wants to be free http://sintheta.org
Guenter Geiger wrote:
Hi David,
The tabread4~ is one of the objects that act differently than their pd version. In PDa the maximum number that you can get out of a signal is 8192.0. Therefor tabread is not indexed with samples but with milliseconds. (Which in turn limits the samples playable to a length of 8.192 seconds).
In short, if you want to play a second of sound, send [0, 1000 1000< to the line~ object connected to tabread4~.
If you use phasor~ to control tabread~, multiply its output by the amount of milliseconds that you want to play, not by the number of samples.
If you still have problems, send me the patch you are using. PDa is not comming with all the help files because of these small incompatibilities (and, because I would have to redo them because of the screen sizes)
Greetings,
Guenter