On Fre, 2012-11-09 at 17:19 +0100, IOhannes m zmölnig wrote:
On 11/09/2012 02:51 PM, Jamie Bullock wrote:
So, it seems like [packOSCstream] and [unpackOSCstream] are (un)packing
message in a format that can't be used with external clients/servers. Is
that correct?
from your
On 2012-11-10 05:24, Roman Haefeli wrote:
On Fre, 2012-11-09 at 17:19 +0100, IOhannes m zmölnig wrote:
On 11/09/2012 02:51 PM, Jamie Bullock wrote:
So, it seems like [packOSCstream] and [unpackOSCstream] are (un)packing message
in a format that can't be used with external clients/servers. Is
On 10 Nov 2012, at 17:10, Martin Peach martin.pe...@sympatico.ca wrote:
On 2012-11-10 05:24, Roman Haefeli wrote:
On Fre, 2012-11-09 at 17:19 +0100, IOhannes m zmölnig wrote:
On 11/09/2012 02:51 PM, Jamie Bullock wrote:
So, it seems like [packOSCstream] and [unpackOSCstream] are
Hi all,
Apologies for the rather esoteric question.
I'm trying to send OSC to/from Pd over TCP using the liblo OSC library and the
mrpeach/ OSC externals [tcpserver], [packOSCstream] and [unpackOSCstream]. I've
attached my testing patch.
I am able to connect to [tcpserver] from liblo, and
hey jamie,
Yep, in this project (https://vimeo.com/24818342) it was going back and
forth from the core app (cpp) to pd. Using OSC. Cannot recall if TCP or
not, but can probably track it down. (that should not make much of a
difference at least outside the network layer).
So you send from liblo
Hi Pedro,
Thanks for the reply. To clarify I can OSC over *UDP* from liblo to/from Pd
just fine using the mrpeach externals. It's using TCP, where I run into
trouble. I think it's due to the streamed nature of TCP, and message
boundaries, but I am not an expert on this.
On 9 Nov 2012, at
I just digged up my thesis (funny how memory works) and I was using UDP.
So its TCP, so you can do liblo to liblo? (or for that matter processing
using oscp5, which is fast to test). If so, could be something with pd
objects.
On Fri, Nov 9, 2012 at 4:19 PM, Jamie Bullock
].
Martin
From: ja...@jamiebullock.com
Date: Fri, 9 Nov 2012 15:19:07 +
To: pedro.lo...@ist.utl.pt
CC: pd-list@iem.at; martin.pe...@sympatico.ca
Subject: Re: [PD] bi-directional OSC over TCP from liblo
Hi Pedro,
Thanks for the reply. To clarify I can OSC over *UDP* from liblo to/from Pd
On 11/09/2012 02:51 PM, Jamie Bullock wrote:
So, it seems like [packOSCstream] and [unpackOSCstream] are (un)packing message
in a format that can't be used with external clients/servers. Is that correct?
from your experience with liblo, you seem to conclude that:
a) all external
On 11/09/2012 05:14 PM, martin.pe...@sympatico.ca wrote:
If you look inside [unpackOSCstream] you'll see that it uses [slipdec].
So the other end must be using [slipenc] or they won't match up.
Unless you are doing this over a serial connection there is no need to
use SLIP at all. [unpackOSC]
Date: Fri, 9 Nov 2012 17:25:41 +0100
From: zmoel...@iem.at
To: pd-list@iem.at
Subject: Re: [PD] bi-directional OSC over TCP from liblo
On 11/09/2012 05:14 PM, martin.pe...@sympatico.ca wrote:
If you look inside [unpackOSCstream] you'll see that it uses [slipdec].
So the other end
11 matches
Mail list logo
