I think the soundfiler is Pd-specific. FIle operation in Max may be done with buffer~ (or maybe similar objects): see the help file of buffer~ and the manual (you can do more or less the same things as the Pd soundfiler).

tabXXX~ can (also) be replaced by index~ (warning, no interpolation at all so it’s not good for the tabread4~) but why not use play~, wave~ or groove~ ?

Cunha Claudio schrieb:
> I don’t can use these objects (play~ groove~ wave~) because in my PD
> patch tabread4~, tabwrite~ and tabosc4~ write or read in a array…
> With play~, groove~ and wave~ we use a buffer…
>
> Do you know how to do for using an array?

array is just another name for buffer~ (or the other way around for the
Pd perspective… ;-)

Quote: ccunha wrote on Wed, 10 October 2007 15:00
—————————————————-
> I don’t can use these objects (play~ groove~ wave~) because in my PD patch tabread4~, tabwrite~ and tabosc4~ write or read in a array…
> With play~, groove~ and wave~ we use a buffer…
>
> Do you know how to do for using an array?
>
>
> Thanks…
—————————————————-

In Pd, you use the same kind of data structure ("array" or "table") for storing both signals AND messages.

In Max, "buffer~" is one equivalent to the Pd "array" for signals and "table", "multislider" or such are equivalents for messages. That said, you can use "buffer~" like the Pd "array" thanks to the "peek~" and "poke~" objects ("index~" also)

I use your patches for tabread4, tabwrite, etc and I have a problem. In the window max I have the messages :
– #N: bad arguments for the message "record~" -
– #N: bad arguments for the message "play~" –
– #N: bad arguments for the message "r" –
– #N: bad arguments for the message "s".