I thought i had this wroking but now, receive13~ does not work. I mean, just opening the help file for receve13~, no other patches open, it doesn't work. I figure if the help file doesn't work, it may be broken for Win7, 43.3 extended. The normal send/receive~ works fine. Anyone have this problem?

Nothing changed that i know of. I am 98% sure it was working before. i wrote 43.3 but meant 43.4, so is is current. i could try an older version. Regular send/receive works fine. i am trying to compile the receive13~ source on my pc, but I am not very good at it. using Mingw...

Sorry but I am not familiar with compiling from source under Windows either. You could also try reinstalling pd 0.43.4 instead of trying an older version. Also, hopefully another Windows user will stop by and write if these objects are working on his or her machine.

edit
[send13~] and [receive13~] works NOT on my win7-32 system.
it says:
receive13~ receive13~: no matching send

@bang

[send~] and [receive~] works on my win7-32 system.

Do you mean [send13~] and [receive13~]?

Yes, I can also use send~ and receive~ fine but not the "13" version. I am on Win7 64. i just now recompiled on my machine using mingw/gcc and cannot get the object to load, even with no errors or even warnings from gcc

Todd, did you also try to reinstall Pd 0.43.4-extended? I just insist on this because you wrote that you are 98% sure it worked on your machine before, meaning that there shouldn't be anything wrong with these objects themselves.

Take care,
Gilberto

I just realized that the normal receive~ does accept a "set xxx" to allow dynamic setting. I did not realize that, as i didn't see it in the documentation. Am i missing something? Why do we even need receive13~ ?

Why do we even need receive13~ ?

For the reason that [send] and [send~] do not accept [set <label>(. That is, [receive~] and [receive13~] are identical, but not [send~] and [send13~].

Take care,
Gilberto

OK that makes sense.