This is really wierd: i have a patch where I'm trying to load up a file into soundfiler using openpanel. I figured out how to make the symbol, including the filename, to make it work.

"read -resize D:/dirxyz/filenamXYZ.wav tableL tableR" (Quotes added)

I could never get this to work, getting "no method for read -resize D:/dirxyz/filenamXYZ.wav tableL tableR" error message in pd. I have noticed though, that if I edit the message box containing the read statement, just add a space and then remove it, all the sudden it works! It is the exact same message i'm sending as far as I can see. Can anyone explain it, and HOW do I make it so i dont have to do that every time?

Hoping someone will reply.

Hi,

That's strange, I simply can't reproduce this on my system. Here I can send a message such as [read -resize /path/file.wav array1 array2( to [soundfiler] and it works without any bug or any need to edit message as you describe.

Could you maybe share your patch here, and also state your OS?

Best,
Gilberto

my guess is that you are sending the whole message as one atom, whereas you want to send it as 5 atoms. the method you want is read, but instead of the read selector, you are sending a single long symbol. somehow you need to make the pathname separately from the read -resize and tableL tableR part
when manually editing a message box, spaces are separators for atoms which is why it works when you manually edit it

It definitely seems to be smething that is not apparent from just looking at the message that is sent to soundfiler. I even tried sending the message to print, and the working version and non working version look identical.

[openpanel]
|
[list append sl sr]
|
[prepend read -resize]
|
[list2symbol]
|
[set $1(
|
[msg box(
|
[soundfiler]

Not sure if I notated that correctly. As I said, editing the message box by adding and removing a space makes it work.

OK, I removed the list2symbo and makefilename:

[openpanel]
|
[list append sl sr]
|
[set read $1 $2 $3 $4(
|
[msg box(
|
[soundfiler]

This works. Is there some way to "see" whether a message is one atom or 5 atoms? I used my "debugger", a route object with bang, float, symbol, anything, and udefined, outputs and in both cases it came out undefined. i could not really distinguish the two cases. Thanks.

[list length] would probably be the easiest way, although undefined selectors (which are "anything"s) are counted as an extra atom, for instance using [list length] on [read -resize( gives 2, even though the message actually has 1 selector and 1 "body". using [list length] on [list read -resize( also gives 2. So maybe a combination of [list length] and [route s l f b] in order to tell if the selector should be counted or not

Thanks, that sounds like a worthy addition to my debugger.