[PD] bi-directional OSC over TCP from liblo
pedro.lopes at ist.utl.pt
Fri Nov 9 15:00:34 CET 2012
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 and pd receives, but no data unpacks? Did I get it
write? If you open a ./oscdump on command line you get the data? (meaning
it would be a pd-side issue...)
On Fri, Nov 9, 2012 at 2:51 PM, Jamie Bullock <jamie at jamiebullock.com>wrote:
> 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 receive raw bytes.
> However, [unpackOSCstream] seems unable to unpack the data. It just outputs
> nothing for the bytes received.
> Likewise, if I send to liblo from [tcpserver] using the |client( selector,
> liblo crashes with the message "error? message too short?".
> 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?
> Has anyone else managed bi-directional communication using OSC over TCP
> with an external application?
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
Pedro Lopes (HCI Researcher / MSc)
contact: pedro.lopes at ist.utl.pt
website: http://web.ist.utl.pt/pedro.lopes /
http://pedrolopesresearch.wordpress.com/ | http://twitter.com/plopesresearch
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list