[PD] OSC messages without / (fwd)
Leandro da Mota Damasceno
lemota at gmail.com
Sat Oct 23 09:40:01 CEST 2010
I would like to apologize for the private emails. it's that when I reply to
the messages they go to the author, not the list. Weird. that's not what
happens in other mailing lists...
So, I have tried to fix the standalone as jasch suggested, but i got all
sorts of error messages. I would have to work almost from scratch and if my
knowledge on PD is still in beginner level, my knowledge of max/MSP is
almost null. Unfortunately, I'm on a deadline to have this thing working, so
I need a workaround by next week.
So right now, I'd rather not mess with the standalone and working on a new
version by myself in a few weeks from now. Martin, I can send you the patch,
but I'm afraid it won't be any helpful for this case, since it depends on
dating coming from the standalone. I can give it to you, of course, if you
want. But I think it's pretty much what has been described here. The best
solution for now I think would be to have a way to get ordinary messages
through udp. No OSC standards.
2010/10/22 IOhannes m zmölnig <zmoelnig at iem.at>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> > From: Leandro da Mota Damasceno <lemota at gmail.com>
> > Let's think in a different way... Why would I just use a udpreceive and
> > a route in Max/MSP to make it work and why doesn't it work with PD? What
> > does
> > the udpreceive does differently for the output in Max/MSP? I am guessing
> > it was an internal unpackOSC that does not care about /. Is that it?
> i think, that max's [udp*] objects simply allows to use messages that
> are not OSC, whereas the Pd objects enforce a strict OSC-adherence.
> usually, the way to implement communication standards is:
> - - be strict in what you send (here the max-objects are faulty)
> - - be lax in what you accept (here the pd-objects are faulty)
> the simplest way to fix the problem is: adhere to the standard!
> so if you can change the max-patch, i would advise you to simply add a
> leading "/" to the messages you send.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> Pd-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list