[Csnd] socksend on win?
Date | 2014-03-04 16:19 |
From | Oeyvind Brandtsegg |
Subject | [Csnd] socksend on win? |
Hi, anyone got socksend/recv or stsend/recv working on windows? I tried connecting two Csound instances running on the same computer, using socksend a1, "127.0.0.1", 7777, 200 in the sending instance and a1 sockrecv 7777, 200 in the receiving instance, but I get no sound. Also tried using stsend/recv in a similar manner, but they give the error "write to socket failed" (and simultaneous "read to socked failed in the other instance) I start the receiver first, then the sender. Also tried starting in opposite order. Tried disabling firewall. Could there be anything platform related, or are they not supposed to both send and receive on the same machine? or is it just me doing something wrong? best Oeyvind -- Oeyvind Brandtsegg Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://flyndresang.no/ http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://soundcloud.com/t-emp |
Date | 2014-03-04 17:24 |
From | Anders Genell |
Subject | Re: [Csnd] socksend on win? |
I assume the omission of a comma in the sockrecv example you posted is just an email typo, and not the actual csd code... Other than that, I have successfully sent audio using socksend on windows, but it was received by a different program, so I have not tried receiving using sockrecv. Regards, Anders 4 mar 2014 kl. 17:19 skrev Oeyvind Brandtsegg |
Date | 2014-03-05 08:22 |
From | Oeyvind Brandtsegg |
Subject | Re: [Csnd] socksend on win? |
Hm, I can't see where the comma is missing here a1 sockrecv 7777, 200 (?) What application did you use to receive the data?, just so I could test under similar conditions. Oeyvind 2014-03-04 18:24 GMT+01:00 Anders Genell |
Date | 2014-03-05 08:41 |
From | Anders Genell |
Subject | Re: [Csnd] socksend on win? |
You're right, I can't read at all obviously. Forget about the comma. The application I used was one written by a colleague of mine, so it's not readily available and since I am no programmer myself, I can't really figure out what it does in detail. It is as far as I know written as a general udp receiver just taking whatever packets are inbound on the correct port and storing them in a buffer of some sort.
If you have a Linux machine available on the same network some headway may be made using netcat and/or wireshark etc to see if there is any datastream what so ever. Sorry for not being of much use..
Regards, Anders On Wed, Mar 5, 2014 at 9:22 AM, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote: Hm, I can't see where the comma is missing here |