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 <[email protected]>wrote: > > 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 14:00, Pedro Lopes <[email protected]> wrote: > > > 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 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...) > > Yes that's correct. There is an example "echo server" that comes with > liblo. I can get bidirectional communication liblo <-> using this example. > If I replace one end of the communication with [tcpserver], liblo can > connect, [tcpserver] receives data, but [unpackOSCstream] can't seem to > unpack the data. Likewise [packOSCstream] doesn't seem to generate a data > format that liblo can understand. > > best, > > Jamie > > > > -- Pedro Lopes (HCI Researcher / MSc) contact: [email protected] website: http://web.ist.utl.pt/pedro.lopes / http://pedrolopesresearch.wordpress.com/ | http://twitter.com/plopesresearch
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
