I've also been trying to figure out how to send two different values via the one netsend, but can't seem to figure it out. I assume its some combination of [pack] / [unpack], is that right? Or is this where [oscparse] and [oscformat] come in?

I'm a little confused by those objects, and to be honest after about 6 hours straight this I think I need to stop for a bit... but does the [oscformat] object essentially add the osc address (or name) to the front of a value before its sent?

and is [oscparse] a bit like a routing object (or route in Max/msp) to unpack them at the other end?

@toddak Phew...... finally a connection.
We can try to break it in a minute.
Yes, you have installed a very recent Vanilla... not extended.

I don't know the osc vanilla objects at all...... but @alexandros has sent you some help below!
OSC messages are just messages like "page1/fader3 0.2345" but they are sent as a string of data and the [packOSC] and presumably the [oscformat] objects will do that conversion.
Then [oscparse] will break up the message according to (and removing) the forward slashes.....
That can be done in a number of ways in extended without using osc objects at all but........ ..

Right-click [oscformat] for help...... the same goes for all objects.
Yes for [netsend] and [netrecieve] you can give your message a "header" like "param1" "param2".
Pure data works with lists, and adding a header has made the message into a list. If you attach a print object to the outlet of something you will see what messages are passing through. So if you send messages that are "lists"....... "param1 0.5" param2 0.75" and you send them to [route param1 param2] you will see your messages 0.5 and 0.75 drop out of the relevant outlets (it creates an outlet for every argument + one for any list that doesn't match).....

So........ aargh........ networking
http://manual.aptosid.com/en/inet-setup-en.htm is a reasonably good explanation from someone else in Melbourne, although a little complicated, but then it's never easy!.
Always make a backup before you change things......
and then try this. It should boot to your network every time (the wifi dongle must be plugged in at boot) and it should give you the same address on the ethernet connection if the wireless is not working..... AND....... it should try to reconnect to your network if it loses the connection.
If you cannot make it work with wpa-roam then change that to wpa-conf for now.
wpa-roam is what will allow your pi to reconnect if the connection is lost.
pi ip conf.txt
David.

Just a demo patch showing how to use [oscformat] and [oscparse]. The arguments of [netsend] and [netreceive] (-u -b) stand for a UDP connection and binary format, respectively. -b is necessary for [oscformat] and [oscparse]. If you need a TCP connection then just omit the first argument in both [netsend] and [netreceive].
The message to [netsend] should contain the receiver's IP instead of "localhost".
oscformat_parse_usage.pd

Haven't followed the whole of this conversation, but what I've understood is that you're trying to connect to a wireless network, right? Do you use a wireless dongle or something? Cause I think the Pi doesn't have wireless, or does it?
Anyway, since both your computer and the Pi are in the same network, you can run a script on the Pi's side to get it's IP and send that over to your computer, if setting a fixed IP is a problem. Actually you can use [shell] to get the IP of the Pi without using a script.
Put the following line in a message:
ip addr list wlan0 | grep "inet " | cut -d' ' -f6 | cut -d/ -f1
and send that message to [shell] and it will output the IP of the wireless from its left outlet. If you know your computer's IP (which should probably be fixed for such a project) you can have that hard coded in the patch running in the Pi and send the output of [shell] to [netsend] via [oscformat]. Then in your computer you can have the incoming IP go through a [symbol] and from there to the following message:
connect $1 9001
taken that the port your computer will send data to the Pi is 9001. Anyway, you get the idea. This way your computer will get connected to the Pi.

@whale-av Sorry for the break in communication. had some other trouble shooting happening. My modem, the linkysys WRT45GL arrived, so I thought I should set that up then proceed with all the IP work so that its all working off the router it will be using. But for some reason I can't seem to connect to the router using its IP address (192.168.1.1) and safari. The reset button on the back does nothing either. I know this isn't a modem forum, but thought it was worth mentioning as you had a similar model.

So, for that reason I haven't pursued the static IP addresses further, although I'll start booting all the pis up with PD in the mean time, and should the modem not be sorted, will proceed with the IPs. Thanks for the links, and for the txt file, it does make sense and will try it shortly.

Also, thanks for explaining that PD is list based, that I didn't know, and seems to be a big difference between it and max. Max still uses lists, just in a different way.

@alexandros That patch does make a lot of sense, but is there any chance you could show me a version that sends/recieves two different values from two different sources? (Like a volume 1 and volume 2 scenario). I'm just trying to figure out how to send multiple items at the moment, and unsure as to how to package that into a list.

That's an interesting work around for the IP address issue, and good to know about [shell]. Yes, mainly connecting pi's to pi's, but maybe a computer at a later date. They don't have wifi, so yes, a dongle is used on all of them.

@toddak Tehe..... routers as well.....
First, a question that I should not ask...... but I have to....... Have you "joined" the new routers' network before trying to access it. It cannot "join" your home network.... sorry to ask....... but it is a completely new and separate network!........
Probably definitely best to do a total reset of the Linksys (especially as you cannot talk to it and you have no idea how it was set up by the previous owner).
Power it up and press the reset for 30 seconds and keep it pressed while unplugging the power.
Now keep it pressed for 30 seconds and keep it pressed still for another 30 seconds after you plug the power again. Now it is "factory reset"
It's address will be 192.168.1.1 OR 192.168.0.1
It will pop up as the network "Linksys".
Its username when you get to the login is just blank..... no user name, and
the password is: admin
If that doesn't work you will have to google a bit.

Here is how you can send more parameters over [netsend]. I recommend [netsend 1] as tcp can crash Pd if the connection is broken. udp does not actually make a "connection". It just broadcasts to only one port at one ip address, so if the information is not received it doesn't know and doesn't care. It is safer (for Pd).
send x2.zip

You can add as many list headers (like the "param1") as you need, or change them to "whatever".

Osc is not "special" but works in exactly the same way. Header "paths" for osc are slash delimited........ more about that later if you need it! But you only need osc if you are planning to use external controllers (like TouchOSC) or send to things that require an osc message.................

David.

There you go osc_deep_address.pd
The address /volume/1 doesn't work because of some strange behavior of [route] that I can't understand. But /volume/one works fine.

@whale-av Next I'll be asking you to help me move house :P
But thanks, that actually worked a lot better than the other reset I found! And it seems to be working so far, just need to set it up and save changes, but I should be ok. Sorry for the delay, been sick, but will hopefully get this up and running over the next few days!!

@alexandros
Is it possibly numbers in the address that freak it out a bit? Anyway, mega thanks for that patch, that definitely makes the routing a lot clearer to me.

Not sure why a [route 1 2] won't output, say 53 from a list "2 53" out its middle outlet, when this list comes out of [route volume] in the example patch I sent. It's strange cause if you send a message "2 53" then [route 1 2] works fine, but not with the chain in the specific patch. Didn't look at it too deeply though..

So I've configured the router, and set that up. But now I'm getting a new error message in my PD window.

When connecting to my home wireless network, it all works fine, but when I connect to the router I get the message:

'netsend: Can't assign requested address (49)

warning: 11 removed from poll list but not found'.

Any ideas?

What's the configuration? This has to do with connecting your computer to the Pi, right? When you say you connect to the router, do you mean via ethernet? Then, what's the IP of your computer? Does this error message show up in the Pi or your computer? What the IP of the Pi? Better post your patch...

@toddak I am pretty sure it is a long standing bug in the osx network stack. There have been a lot of complaints over the years. The only solution found is to shut down the socket (wlan0 probably) flush the cache and then restart the socket.... (for your mac!).... or just to reboot it..... which some people have found to be absolutely the only solution....
I hope that works for you as well!
David.

@whale-av Its just feels odd to me that it works fine on the Home network, but doesn't work on the other router. I would have thought that if it was an issue with OSX, then it wouldn't work on either. Is that a fair assumption?

I did manage to get PD to generate another two error messages:

netsend: Connection refused (61)

warning: 11 removed from poll list but not found
connecting to port 9001
netsend: Network is unreachable (51)

warning: 11 removed from poll list but not found

Could there be something in the router that needs changing? Alternatively, could it have anything to do with the edits I made to the /etc/network/interfaces file?

@alexandros -So the pi and my computer are connected to the router via wifi, not via an ethernet cable. Its the same idea that was working before when I used my home router, only know I'm using a different router. That's the only difference in the system.

As far as I know the IP address of my laptop is not static, so I've been using that to send from just for tests. I've set up the pi with the static IP address of 10.1.1.101, and that has been working fine on the home network.

The error message appears on my computer, the sender. I'm just using the receiver/sender_udp patches you gave me, but have updated the IP address to 10.1.1.101.

@toddak Have you tried re-booting the mac? (after making the Linksys your preferred network).
Normally netsend in udp mode should not care even if you have turned off all your network adapters. I am (almost) certain that the error messages are being returned by the os.
I wonder if osx will not connect properly to the Linksys because there is no internet connection? I hope not!, but osx, is at least as intrusive as the new windows 10.
You should definitely fix your Ip address for the mac for the Linksys network location. It could be very important later in your project that addresses never change.
What version of the wrt54 did you get (printed on the label on the bottom somewhere). If I have one the same I could send you a configuration file........
David.

If you're connected to another router it's very likely that your computer gets a different IP, if it's using DHCP instead of a static IP. In this case, you should probably log in the Pi via SSH (you can use ssh -X pi@raspberrypi.local if you're not sure about its IP) and once you know your computer's IP, change the Pi's patch accordingly.
I believe it's better to have a connection over ethernet and set a static IP both for the Pi and your laptop for their ethernet connection and leave their wi-fi untouched so you can log it any router and the internet without problems.

@alexandros Hello Alexandros..... He needs wifi for his project, and the Pi's are already static....
David.

@whale-av then I guess he'll need some scripting...
@toddak I think that you can send data via OSC to the IP address 255.255.255.0 and given that the port is the same for the sender and the receiver, the message will arrive to any recipient in the network. So you can maybe use that to send the Pi's IP to your laptop on boot (using the script I've posted in an earlier reply) and then start sending from your computer to the Pi. You can probably use the same technique to send your computer's IP to the Pi as well...

@alexandros Hello Alexandros..... He will always know the PI's IPs (it's almost poetry isn't it!) because they will be (are already I hope) fixed. He is going to send different messages to each one...... so no multicast....
I think I should start a chat with him for the network setup. The patch problem is solved, and this thread has become very long.............. !!
His whole setup works fine on his home network, but it looks as though his mac (the central control) is not communicating properly with the router that will be used for the show.........
David.

@whale-av I guess I've been partly understanding this thread cause I've been partly reading the posts, to be honest... sorry for throwing random stuff in this conversation.

@alexandros That's ok....... it could have been useful (and in fact it could help someone else that stumbles across it later!).........
It's a problem with threads as long and twisted as this one......
David.