[Csnd] OSCsend

[Csnd] OSCsend

Date	2014-05-29 12:54
From	Eduardo Moguillansky
Subject	[Csnd] OSCsend
	Hi All, The signature for OSCsend appears to be OSCsend kwhen, ihost, iport, idestination, itype [, kdata1, kdata2, ...] Is there a reason why `iport` could not be a k-variable? I need to implement a ping protocol and would need to reply when pinged to an arbitrary port Thanks! Eduardo

Date	2014-05-29 13:27
From	jpff@cs.bath.ac.uk
Subject	[Csnd] Re:
Attachments	None

Date	2014-05-29 14:32
From	Eduardo Moguillansky
Subject	[Csnd] Re:
	Thanks for your reply Maybe I did not make the question clearly. My use cases are the following: 1) an application needs to see if csound is alive. It sends an OSC message "/ping". Csound needs to send "/pingback" to the port that sent the "/ping" 2) an application like PureData, in its many OSC implementations, sends OSC from an arbitrary port. It needs to query some information from csound, for instance, its position in time. PureData is listening in port X. It sends "/time/get". It adds its reply port to the message, effectively sending ("/time/get", "i", X). Csound replies to port X, which is not known in advance. Without a variable port, the only workaround I found was to write an instrument whose only function is to send osc messages, and fire it with "event" every time there is some request. It works fine, but makes the code unnecesarily convoluted. On Thu, May 29, 2014 at 2:27 PM, <jpff@cs.bath.ac.uk> wrote: Quoting Eduardo Moguillansky <eduardo.moguillansky@gmail.com>: Hi All, The signature for OSCsend appears to be OSCsend kwhen, ihost, iport, idestination, itype [, kdata1, kdata2, ...] Is there a reason why `iport` could not be a k-variable? Yes. The port is part of knowing on what port to listen. The listener is set up on initialisation. If you change the port at k-rate it would require a great deal of redesign and huge hit on performance I need to implement a ping protocol and would need to reply when pinged to an arbitrary port Including port 25? Thanks! Eduardo

Date	2014-05-29 15:31
From	David Worrall
Subject	Re: [Csnd] OSCsend
	Thanks for this Eduardo! I'm not sure OSCsend could be used for ping - perhaps what we need is a netcap opcode. D. On 29.05.2014, at 13:54, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote: Hi All, The signature for OSCsend appears to be OSCsend kwhen, ihost, iport, idestination, itype [, kdata1, kdata2, ...] Is there a reason why `iport` could not be a k-variable? I need to implement a ping protocol and would need to reply when pinged to an arbitrary port Thanks! Eduardo

Date	2014-05-29 15:36
From	David Worrall
Subject	Re: [Csnd]
	Well, if we're going to "listen", why not include ports 110, 993, and 995. :-) D. On 29.05.2014, at 14:27, jpff@cs.bath.ac.uk wrote: > > Quoting Eduardo Moguillansky : > >> Hi All, >> >> The signature for OSCsend appears to be >> >> OSCsend kwhen, ihost, iport, idestination, itype [, kdata1, kdata2, ...] >> >> Is there a reason why `iport` could not be a k-variable? >> > > Yes. The port is part of knowing on what port to listen. The listener is set up on initialisation. > > If you change the port at k-rate it would require a great deal of redesign and huge hit on performance > >> I need to implement a ping protocol and would need to reply when >> pinged to an arbitrary port >> > > Including port 25? > >> Thanks! >> Eduardo > >