csound connecting to remote osc port
Date | 2016-05-09 05:20 |
From | Kelly Hirai |
Subject | csound connecting to remote osc port |
hey fellow csounders, i'm having difficulty discovering an example where csound connects to a remote osc port. has this been implemented yet? kelly Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2016-05-09 07:12 |
From | Anders Genell |
Subject | Re: csound connecting to remote osc port |
Doesn't the examples in the manual do that? Sending: https://csound.github.io/docs/manual/OSCsend.html Receiving: https://csound.github.io/docs/manual/OSClisten.html Regards, Anders > 9 maj 2016 kl. 06:20 skrev Kelly Hirai |
Date | 2016-05-09 17:17 |
From | Justin Smith |
Subject | Re: csound connecting to remote osc port |
One thing that could be confusing is that OSC is a stateless protocol, which means that you don't have a "connect" or "connection" per se. You tell it which host and port you are targeting, and send a message. That's it. The connection is not two way, and has no error correction. On Sun, May 8, 2016 at 11:12 PM Anders Genell <anders.genell@gmail.com> wrote: Doesn't the examples in the manual do that? |
Date | 2016-05-09 17:18 |
From | Justin Smith |
Subject | Re: csound connecting to remote osc port |
err. clarification, OSC uses UDP, and beyond what raw IP offers UDP has no error correction On Mon, May 9, 2016 at 9:16 AM Justin Smith <noisesmith@gmail.com> wrote:
|
Date | 2016-05-09 17:20 |
From | Kelly Hirai |
Subject | Re: csound connecting to remote osc port |
thanks. my mind must have gone on strike. :) kelly On 05/09/2016 02:12 AM, Anders Genell wrote: > Doesn't the examples in the manual do that? > > Sending: > https://csound.github.io/docs/manual/OSCsend.html > > Receiving: > https://csound.github.io/docs/manual/OSClisten.html > > Regards, > Anders > > >> 9 maj 2016 kl. 06:20 skrev Kelly Hirai |
Date | 2016-05-09 17:27 |
From | "Joe ." |
Subject | Re: csound connecting to remote osc port |
My brain's name is Eugene v Debs. /* Joe */ On Tue, May 10, 2016 at 12:20 AM, Kelly Hirai <khirai@ongaku.isa-geek.net> wrote: thanks. my mind must have gone on strike. :) |
Date | 2016-05-09 19:11 |
From | Kelly Hirai |
Subject | Re: csound connecting to remote osc port |
i'm targeting the behringer x18 headless mixer. from what i can tell, you establish a 2 way connection, when you change states, it 'acks' with the report of the new state. it emits gobs of unsolicited osc data as well ( rt analyser, perhaps even audio). it seems to accept multiple connections to the same port. k. On 05/09/2016 12:18 PM, Justin Smith wrote: > err. clarification, OSC uses UDP, and beyond what raw IP offers UDP has no > error correction > > On Mon, May 9, 2016 at 9:16 AM Justin Smith |
Date | 2016-05-09 19:21 |
From | Justin Smith |
Subject | Re: csound connecting to remote osc port |
Once again, OSC is UDP, and UDP is stateless. UDP has no "connections", it simply tells you the source IP of each message. It can send data back to you, but it's on the receiver to a) be running at all and b) do anything with that data, and you set up a listener totally independent from the transmit. You can listen to replies and send requests, but this is not a single "connection" as it is in TCP, it's two stateless servers that happen to send each other messages - they could each be running in a different piece of software if you like. On Mon, May 9, 2016 at 11:11 AM Kelly Hirai <khirai@ongaku.isa-geek.net> wrote: i'm targeting the behringer x18 headless mixer. from what i can tell, |
Date | 2016-05-09 20:25 |
From | Kelly Hirai |
Subject | Re: csound connecting to remote osc port |
"and you set up a listener totally independent from the transmit." ahh, now i see. thanks! k. On 05/09/2016 02:21 PM, Justin Smith wrote: > Once again, OSC is UDP, and UDP is stateless. UDP has no "connections", it > simply tells you the source IP of each message. It can send data back to > you, but it's on the receiver to a) be running at all and b) do anything > with that data, and you set up a listener totally independent from the > transmit. You can listen to replies and send requests, but this is not a > single "connection" as it is in TCP, it's two stateless servers that happen > to send each other messages - they could each be running in a different > piece of software if you like. > > On Mon, May 9, 2016 at 11:11 AM Kelly Hirai |