Ah, ok :)
Have you open [routeOSC] and [packOSC] in mrpeach ?
Click on [connect 127.0.0.1 9997( message, you must have in the
console :
udpsend: connecting to port 9997
Then click on [send /test/one/two/three zz 88 T( message, you must
have in the console :
print: /test/one/two/three zz 88 T
error: pipelist: no method for '/test/one/two/three'
... you might be able to track this down from the Find menu.
In this case, all should be ok ?
++
Jack
Le 5 févr. 09 à 16:23, mbutubuntu a écrit :
JacK, I know... packOSC works, but udpsend doesn't connect, neither
tcpsend...Jack wrote:
If you use OSC, you need [packOSC] before [udpsend]. See the help
patch of [packOSC] in mrpeach. ++Jack
Le 5 févr. 09 à 16:12, mbutubuntu a écrit :
thanks... udpreceive wors wery well.... but udpsend
doesn't... :P:P....Jack wrote:
Yep, as Roman says try [udpreceive] with [unpackOSC] (OSC comme
often 'on' UDP) or [tcpreceive] with [unpackOSC], if you want a
service with connection. The choice depends if you absolutely
need to receive your data. AFAIK, OSCx accepts only UDP protocol. ++Jack
Le 5 févr. 09 à 14:15, Roman Haefeli a écrit :
--- mbutubuntu mbutubuntu@yahoo.it schrieb am Do, 5.2.2009:
hello folks, I'm using OSC to send information from Processing to Pd... I started writing my "receiving" Patch in a Computer where was Installed Ubuntu 8.04 and Pd-extended 0.40.3 in stalled by the .deb package, my laptop was an Archlinux "client" in which Processing was running... Processing sent floating point numbers to Pd... All worked properly....
In the second Panorama, my archlinux box is both the "server" and the "client", Pd is the version 0.41.4 compiled by me with all useful libraries (OSCx for example)... Pd refuses to receive floating point numbers from Processing giving me this value:
1.4013e-45 ...... = n/0 ???
I can use only Integer numbers.... why ???
hi
from what i know, OSC supports a whole bunch of number types
and obviously [dumpOSC] doesn't know how to handle the type
chosen by processing.i guess, i can't help you here, probably only the author of the
OSCx library can. however, OSCx shouldn't be used anymore,
since it does not seem to be maintained anymore and is known to
be buggy. there is a well maintained and well tested
replacement for it in mrpeach, though it might not be as
straight forward to use as OSCx.i think, you could replace [dumpOSC] by something like:
[udpreceive <portnumber>] | [unpackOSC]
good luck
roman
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http:// lists.puredata.info/listinfo/pd-list