| Wireless networks can be unreliable. I suppose the problem is neither
with Csound nor with liblo, but with the infrastruture.
Victor
----- Original Message -----
From: "Hector Centeno"
To:
Sent: Tuesday, April 15, 2008 1:16 AM
Subject: [Csnd] Re: OSC data not being transmitted
> Hello,
>
> Just to follow up on this. I tried using a wired connection instead of
> the wireless and it seems to work better. Does this make sense?
>
> Cheers,
>
> Hector
>
> p.s. I wonder if my posts are making it to the list since this is the
> second question I ask that gets no response (beside my own) either
> that or my questions are cryptically written (because of my bad
> English) or maybe I'm addressing very obscure areas :-)
>
>
>
> On Fri, Apr 11, 2008 at 5:45 PM, Hector Centeno wrote:
>> Hello,
>>
>> I'm communicating two Csound instances running in realtime in two
>> separate networked (through a router) computers. The first one has a
>> GUI with FTLK controllers and the values are sent over to the second
>> computer to be used as synthesis parameters. Everything seems to work
>> fine except that some times it seems that at startup all the initial
>> data doesn't make it to the second computer. When the first computer
>> starts it sends around 61 parameters (all floating point values) to
>> the second one, then after that it only sends whatever parameters are
>> changed through the GUI. I guess the limiting factor here would be the
>> bandwidth of the network but does that mean that if the bandwidth is
>> surpassed then the data gets lost? Is it not queued and sent as the
>> bandwidth becomes available (creating some latency I guess, which is
>> not a problem in my case)? The first computer is a laptop connected
>> via wireless to the router (I'll test using a wired connection).
>>
>> Thanks, I'll appreciate any help. I'm running Linux in both computers
>> and a CVS build of Csound.
>>
>> Hector
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
|