well, I dont mind how much space it takes up its just the fact that I have to write it out so many times is the problem, Ill have a look at the pack object or something, or see can I turn the IP into some variable so I only have to write it once, like variable = 10.50.42.10 so itl be like |connect variable 3005| |connect variable 3006| etc hopefully Ill find something that does that, any suggestions appreciated thanks for the help
-----Original Message----- From: Martin Peach [mailto:martinrp@vax2.concordia.ca] Sent: 08 March 2004 17:27 To: Adrian deCleir Cc: PD-List Subject: Re: [PD] one other thing, bout sending info to a message
Adrian deCleir wrote:
Ok I dont know if this is possible its sounds a bit weird, but In a
project
I have where people play music together over the internet or a network
there
is several netsend connections, each one for something different, like |connect 10.42.50.10 3001| for volume, then |connect 10.42.50.10 3002| for the actual note, and | connect 10.42.50.10 3003| for pitch bend or
something
different like that, this means I have about 10 netsends overall , all for different features. This means when Im connecting with someone different I have to write in
the
IP address 10 times for everything to work, this project is for college
and
a problem like this will seriously make the project look bad, any ideas?
Use OSC with one connection and path-like routing of parameters, something like: synth1/volume/0.5 synth1/pitchbend/0.333 synth1/noteon/60
as in is there a way of just writing the IP once and send it to
all the different |connect| messages so it'd be like this
you write in the IP here |10.42.50.10 | and it sends it out to all the
other
ones like it shows there | | |____________________________________ | |_________________________ | | | | |connect 10.42.50.10 5002| |connect 10.42.50.10 5000| | |connect 10.42.50.10 5001|
Something like:
|10.42.50.10( | |5000( | | [pack s f] | |connect $1 $2( | [netsend]
...takes up almost as much space! Martin
I do this type of thing all the time and here's how I do it:
I just have one netsend/netreceive and the routing is done within the patch depending on prepended numbers so a message like this 1 50 might be intended as a volume value and 2 79 might be a note value. In the receiving patch the received messages first go to a route object like this
route 1 2 3 4
What happens then is it routes the message based on the first value in the pack and removes that value at the same time so a message 1 50 will be routed out the first outlet and only the value 50 is passed. Take a look at routemap.pdf at http://130.208.220.190/panse/res.htm to see what I mean.
Pall Thayer artist/teacher Fjolbrautaskolinn vid Armula http://www.this.is/pallit http://www.this.is/pallit/isjs http://www.this.is/pallit/harmony http://130.208.220.190/panse
----- Original Message ----- From: "Adrian deCleir" 0031259@student.ul.ie To: "'Martin Peach'" martinrp@vax2.concordia.ca Cc: "PD-List" pd-list@iem.kug.ac.at Sent: Monday, March 08, 2004 5:48 PM Subject: RE: [PD] one other thing, bout sending info to a message
well, I dont mind how much space it takes up its just the fact that I have to write it out so many times is the problem, Ill have a look at the pack object or something, or see can I turn the IP into some variable so I only have to write it once, like variable = 10.50.42.10 so itl be like |connect variable 3005| |connect variable 3006| etc hopefully Ill find something that does that, any suggestions appreciated thanks for the help
-----Original Message----- From: Martin Peach [mailto:martinrp@vax2.concordia.ca] Sent: 08 March 2004 17:27 To: Adrian deCleir Cc: PD-List Subject: Re: [PD] one other thing, bout sending info to a message
Adrian deCleir wrote:
Ok I dont know if this is possible its sounds a bit weird, but In a
project
I have where people play music together over the internet or a network
there
is several netsend connections, each one for something different, like |connect 10.42.50.10 3001| for volume, then |connect 10.42.50.10 3002|
for
the actual note, and | connect 10.42.50.10 3003| for pitch bend or
something
different like that, this means I have about 10 netsends overall , all
for
different features. This means when Im connecting with someone different I have to write in
the
IP address 10 times for everything to work, this project is for college
and
a problem like this will seriously make the project look bad, any ideas?
Use OSC with one connection and path-like routing of parameters, something like: synth1/volume/0.5 synth1/pitchbend/0.333 synth1/noteon/60
as in is there a way of just writing the IP once and send it to
all the different |connect| messages so it'd be like this
you write in the IP here |10.42.50.10 | and it sends it out to all the
other
ones like it shows there | | |____________________________________ | |_________________________ | | | | |connect 10.42.50.10 5002| |connect 10.42.50.10 5000| | |connect 10.42.50.10 5001|
Something like:
|10.42.50.10( | |5000( | | [pack s f] | |connect $1 $2( | [netsend]
...takes up almost as much space! Martin
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
-
Adrian deCleir -
Pall Thayer