Hi, I am making a simple patch bay sort of patch to help our group be able to share our data over OSC. I am using the flatspace object entry which creates a grey field in which you can enter text, in play mode, that then you can use as variable, control information or whatever.

This is nice because I want my patch to be able to be used by:
1. people who don't work in PD much
2. people who don't want to ctrl+E to go to edit mode and type a new port number into the receive field, then ctrl+E back again, but instead to simply enter the number push Return and go...

I already have a "send" area, working fine...one can enter IP addresses, and ports to send to, and the messages are sent.

With the receive area if I use the udpreceive object with a pre-established port number it works fine (it receives the messages - and I mean both internally, in my machine, and over a network, no problems)
the issue is that I want to make the udprecieve object accept a variable so that I can assign an input field to it to make my patch user friendly, especially as we are not all running pd-based systems, even if pd is managing our network!

example:

[udpreceive 9010]

works fine, but

[udpreceive $1]

does not, even if this variable has been established elsewhere

any advice?

thx,
Jorge

i don't have the [udpreceive] object installed, so i couldn't check exactly.

but, i'm assuming it doesn't have an inlet that can be used to set the port?
i'm also assuming you already tried checking the [udpreceive] help documentation, and confirmed there's not a 'set' message or something?

in that case, a simple dynamic hack might be the best way. patch attached

http://www.pdpatchrepo.info/hurleur/dynamic-udp.pd

Aaahhh, you beat me to it.

I've been wanting to do this for a while, anyway, so here's an abstraction version of it.

http://www.pdpatchrepo.info/hurleur/udpreceive.mmb.pd

Aaahhh, you beat me to it.

I've been wanting to do this for a while, anyway, so here's an abstraction version of it.

http://www.pdpatchrepo.info/hurleur/udpreceive.mmb.pd

Wow, yeah this should be just the thing. Both of these are interesting. I have to look at how this "wrapper" business works, this is something totally new to me, i was trying all sorts of backwards ways to do this.

Ok, so I will post a test version when I have something. Its nice with the gui, and since you can send multiple OSC messages to the same port and then just parse them later (using the header) you can have multiple arrays of connections between different machines, and then just toggle between the streams of data as needed, for whatever you are doing.

Hi all, I have tried to reverse engineer what you did to write that wrapper onto that udpreceive object in order to write one for a udpsend object. However, it is not so simple like I thought...I am missing information...how do I write these wrappers?

is this pd or some other type of code that lives in a message box and can interface with pd (maybe i can write my own if I understand what you put in that message
box above)

as you will see, in my patch, attached, the problem is (go into the pdsendOsc2 subpatch) that I cannot assign variables correctly to the "connect" message box in order to get them into the udpsend object...)

obviously there is some chaos here but this is because I was trying many combinations of packing them as messages in different ways, but I cannot even find one way that it will function...this is simply the last state I left it in before I said "ok, I don't understand this"

I want to make a system where 5 people or 10 can simply type the ip addresses & ports into my flatspace box and connect to all 10 of each other
of course one connection would be a success..
but since we can all send each other messages on a single receiving port (huge advantage with OSC) and parse them later based on a the headers assigned by individual users I thought to make a single input space where each user simply connects (and then receives from the others) would be a simple solution

before I had four send bays and four receive bays, it was working but clunkly and everyone had to input the ports and and addresses by basically (ctrl E) modifiying the patch each time, as not everyone in our group is super pd-friendly (though I wish they were) I think an input interface where people can just input the address and ports they want is much better

that is what I am trying to do...(below)
any suggestions are appreciated, especially as to how I can make these "wrappers" to create new inputs for objects that do not have them. Is it possible without knowing a lower-level language?
thanks!
J
ps the test patch included is just to get some numbers rising and falling for testing

http://www.pdpatchrepo.info/hurleur/space_cmd8RecieveFunctionsTest.pd

ps! sorry, but the extra message box on the first input of the pdsendOsc2 object is just my ip address there as a control mechanism I was using to see the difference in my direct connection (which functions but is not user-intefaceable) and the flatspace object (where a user will hopefully just be able to input the ip and port number) just there for a test...in case that caused confusion
I would like to just get rid of this once its working

Because your patch has so many things that are not necessary to solve your problem, I'm not entirely certain I understand what you're asking. When posting patches, it's best to not include excess experiments that don't work. Just explain what you're trying to do and post what you have. Having all this extra stuff can make things more confusing. It's good to be thorough in your explanation, just be careful not to include things that are unnecessary.

However, I think I see what you're asking. I think this should solve the problem of connecting [udpsend]:

[entry]
|
[symbol2list]
|
[connect $1 $2(
|
[udpsend]

Right now, you are treating both the IP address and the port as one symbol. However, the connect method for [udpsend] uses two arguments: the IP address and the port. These need to be separated. [entry] outputs everything as one symbol, and [symbol2list] will parse the symbol into a list using spaces as separators by default. You can use that to split the [entry] symbol into multiple list elements.

When I refer to an abstraction as being a "wrapper", I just mean that it uses an object as it's core, but tries to make it more useful or intuitive. For example, a GUI wrapper for a [vcf~] object might have a display of its frequency response and sliders to control the cutoff frequency and resonance, but it still only does what [vcf~] does. In the case of this [udpreceive.mmb] abstraction, what it does is dynamically patch in a new instance of [udpreceive] when you change the port number. Other than that, it's the same object. You can read more about dynamic patching in Help -> Browser -> Manuals -> pd-msg.

"into a list using spaces as separators by default"

that should do it! I am going to have a go at it asap.

You are correct about that patch being a mess, I didn't want to clutter the board. Posting it like that was a reaction out of frustration. Next time I will clean it up first, and definitely I will post a nice clean version when I get this working.

The pd-msg stuff is, in fact, what I was asking about in the question about the abstraction itself. I somehow never realized this existed! When I saw your abstraction, and the information in that message box looked like klingon to me, but I see that those arguments are explained right away in this. Great!

Ok, I will get back to this and post results later. Thanks so much for your advice, this board is a godsend.
J