[PD] OSC problem
Christof Ressi
info at christofressi.com
Mon Feb 8 23:06:06 CET 2021
> I have made a little program in Unity to send over OSC (port 7000)
If you use UDP (which you normally would), then a [netreceive -u -b
7000] in Pd should give you the *raw* OSC message. "-u" stands for UDP
and "-b" stands for binary. Alternatively, you can also use
[iemnet/udpreceive 7000].
Then you have to convert the raw bytes to a Pd message, e.g. with
[unpackOSC] (from "mrpeach" resp. "osc") or Pd vanilla's [oscparse].
> Anyway, netreceive print to the console: slipdec: maximum packet
> length is 65536.
This error message definitely comes from the [slipdec] object.Totally
off topic, but these OSC addresses look weird. Why not use /trigger/0/0
and /trigger/34/1 ?
Christof
On 08.02.2021 22:02, Csaba Láng wrote:
> Dear list,
>
> I have made a little program in Unity to send over OSC (port 7000) 60
> times per second if a trigger was touched or not (1 and 0 respectively)
>
> However, any of my tries if it was over localnetwork or via IP to port
> 7000 nothing comes to Pd.
> Tried udp, tcp and netreceive but cannot catch any of the signals
> which looks like this
> /trigger0/0 or /trigger34/1
>
> Anyway, netreceive print to the console: slipdec: maximum packet
> length is 65536.
>
> What could go wrong?
> When I use Arena or Artnet the OSC is running with all the info I
> need, but Pd is muted totally.
>
> Best,
>
> Popesz
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20210208/cab704a9/attachment.html>
More information about the Pd-list
mailing list