[PD] OSC messages without /

Leandro da Mota Damasceno lemota at gmail.com
Thu Oct 21 23:12:15 CEST 2010


Hi Roman

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.

Well, I will try your patch. I hope it works. I'm getting sick of my patch
already :P

best,

Leandro

On Thu, Oct 21, 2010 at 11:07 PM, Roman Haefeli <reduzent at gmail.com> wrote:

> Hi again
>
> (I reply to the  list as well...)
>
> Yeah, I now remember that the OSC address must always be a multiple of 4
> bytes long. I also stumbled across this problem a while ago and wrote an
> abstraction back then that does pad the the address of the OSC message
> with zeros as needed. Insert it right after the [list prepend 47].
>
> Check attachment.
>
> Although this might work now, it's clearly the fault of your max/msp
> patch that obviously does not comply with the OSC standard.
>
> Roman
>
>
> On Thu, 2010-10-21 at 22:45 +0200, Leandro da Mota Damasceno wrote:
> > That solution sounded good, but this is the result I got:
> >
> >
> >
> >
> > unpackOSC: Packet size (257) not a multiple of 4 bytes: dropping
> > packet
> > unpackOSC: Packet size (41) not a multiple of 4 bytes: dropping packet
> > unpackOSC: Packet size (281) not a multiple of 4 bytes: dropping
> > packet
> > unpackOSC: Packet size (41) not a multiple of 4 bytes: dropping packet
> > unpackOSC: Packet size (281) not a multiple of 4 bytes: dropping
> > packet
> > unpackOSC: Packet size (41) not a multiple of 4 bytes: dropping packet
> > unpackOSC: Packet size (281) not a multiple of 4 bytes: dropping
> > packet
> >
> >
> > and so on. Any ideas?
> >
> > On Thu, Oct 21, 2010 at 10:07 PM, Roman Haefeli <reduzent at gmail.com>
> > wrote:
> >         On Thu, 2010-10-21 at 19:39 +0100, Claude Heiland-Allen wrote:
> >         > On 21/10/10 18:26, Leandro da Mota Damasceno wrote:
> >         > > So, the question is... Is there any workaround I could try
> >         in PD?
> >         >
> >         >   |
> >         > [list split 1]
> >         >   |          |
> >         > "/$1"       |
> >         >   |          |
> >         > [list append ]
> >         >   |
> >         > [list trim]
> >         >   |
> >
> >
> >         This would require to convert the byte list to strings and
> >         then back to
> >         a byte list again.
> >
> >         You could instead insert a [list prepend 47] (47 is the byte
> >         value of a
> >         '/') right after the [udpreceive].
> >
> >         Roman
> >
> >
> >
> >
> >         _______________________________________________
> >         Pd-list at iem.at mailing list
> >         UNSUBSCRIBE and account-management ->
> >         http://lists.puredata.info/listinfo/pd-list
> >
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20101021/39a8ade5/attachment.htm>


More information about the Pd-list mailing list