Hi Roman<div><br></div><div>Thanks for the help. Actually, I did not write the code in Max/MSP, but I think I will end up writing my own version of the application, because it does need a lot of tweaking. It is funny to realize how Max/MSP can be kind of agnostic towards that.</div>
<div><br></div><div>Well, I will try your patch. I hope it works. I'm getting sick of my patch already :P</div><div><br></div><div>best,</div><div><br></div><div>Leandro<br><div><br><div class="gmail_quote">On Thu, Oct 21, 2010 at 11:07 PM, Roman Haefeli <span dir="ltr"><<a href="mailto:reduzent@gmail.com">reduzent@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi again<br>
<br>
(I reply to the list as well...)<br>
<br>
Yeah, I now remember that the OSC address must always be a multiple of 4<br>
bytes long. I also stumbled across this problem a while ago and wrote an<br>
abstraction back then that does pad the the address of the OSC message<br>
with zeros as needed. Insert it right after the [list prepend 47].<br>
<br>
Check attachment.<br>
<br>
Although this might work now, it's clearly the fault of your max/msp<br>
patch that obviously does not comply with the OSC standard.<br>
<font color="#888888"><br>
Roman<br>
</font><div><div></div><div class="h5"><br>
<br>
On Thu, 2010-10-21 at 22:45 +0200, Leandro da Mota Damasceno wrote:<br>
> That solution sounded good, but this is the result I got:<br>
><br>
><br>
><br>
><br>
> unpackOSC: Packet size (257) not a multiple of 4 bytes: dropping<br>
> packet<br>
> unpackOSC: Packet size (41) not a multiple of 4 bytes: dropping packet<br>
> unpackOSC: Packet size (281) not a multiple of 4 bytes: dropping<br>
> packet<br>
> unpackOSC: Packet size (41) not a multiple of 4 bytes: dropping packet<br>
> unpackOSC: Packet size (281) not a multiple of 4 bytes: dropping<br>
> packet<br>
> unpackOSC: Packet size (41) not a multiple of 4 bytes: dropping packet<br>
> unpackOSC: Packet size (281) not a multiple of 4 bytes: dropping<br>
> packet<br>
><br>
><br>
> and so on. Any ideas?<br>
><br>
> On Thu, Oct 21, 2010 at 10:07 PM, Roman Haefeli <<a href="mailto:reduzent@gmail.com">reduzent@gmail.com</a>><br>
> wrote:<br>
> On Thu, 2010-10-21 at 19:39 +0100, Claude Heiland-Allen wrote:<br>
> > On 21/10/10 18:26, Leandro da Mota Damasceno wrote:<br>
> > > So, the question is... Is there any workaround I could try<br>
> in PD?<br>
> ><br>
> > |<br>
> > [list split 1]<br>
> > | |<br>
> > "/$1" |<br>
> > | |<br>
> > [list append ]<br>
> > |<br>
> > [list trim]<br>
> > |<br>
><br>
><br>
> This would require to convert the byte list to strings and<br>
> then back to<br>
> a byte list again.<br>
><br>
> You could instead insert a [list prepend 47] (47 is the byte<br>
> value of a<br>
> '/') right after the [udpreceive].<br>
><br>
> Roman<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> <a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
> UNSUBSCRIBE and account-management -><br>
> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div></div>