Hi<div><br></div><div>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...</div><div>
<br></div><div>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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>Best,</div><div><br></div><div>Leandro</div><div><br><div class="gmail_quote">2010/10/22 IOhannes m zmölnig <span dir="ltr"><<a href="mailto:zmoelnig@iem.at">zmoelnig@iem.at</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div class="im">> From: Leandro da Mota Damasceno <<a href="mailto:lemota@gmail.com">lemota@gmail.com</a>><br>
><br>
</div><div class="im">> Let's think in a different way... Why would I just use a udpreceive and<br>
> a route in Max/MSP to make it work and why doesn't it work with PD? What<br>
> does<br>
> the udpreceive does differently for the output in Max/MSP? I am guessing<br>
> it was an internal unpackOSC that does not care about /. Is that it?<br>
><br>
<br>
</div>i think, that max's [udp*] objects simply allows to use messages that<br>
are not OSC, whereas the Pd objects enforce a strict OSC-adherence.<br>
<br>
usually, the way to implement communication standards is:<br>
- - be strict in what you send (here the max-objects are faulty)<br>
- - be lax in what you accept (here the pd-objects are faulty)<br>
<br>
the simplest way to fix the problem is: adhere to the standard!<br>
<br>
so if you can change the max-patch, i would advise you to simply add a<br>
leading "/" to the messages you send.<br>
<br>
<br>
fgmsdft<br>
<div class="im">IOhannes<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
<br>
</div>iEYEARECAAYFAkzBxFkACgkQkX2Xpv6ydvS9xgCgrQZppWIAHu60uDEIqQ3MJCUh<br>
GrMAn0Wjhr77zAusMq9vVOu8QLX/dP2R<br>
=w3Q7<br>
-----END PGP SIGNATURE-----<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
<a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
</div></div></blockquote></div><br></div>