Hi Roman<div><br><div>It's ok, i just keep forgetting to reply to all...</div><div><br></div><div>so, I really don't understand how that could be happening, especially when in max/MSP i don't have to route any #bundle tag. It's funny how it shows how different it is to work with osc in both languages. the deadline for next week is what is actually getting me worried...</div>
<div><br></div><div>best</div><div><br></div><div>Leandro</div><div><br><br><div class="gmail_quote">On Wed, Oct 27, 2010 at 9:38 AM, 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 Leandro<br>
<br>
Sorry for not having responded quickly.<br>
<br>
I know that OSC supports so-called bundled messages. However, I haven't<br>
yet investigated how they actually work. It seems like your Max patch is<br>
sending bundled OSC messages. It seems like those are tagged with a<br>
'#bundle' and obviously the '/' is prepended to #bundle tag instead of<br>
the OSC address.<br>
<br>
I don't have a solution at hand for this, since it makes OSC message<br>
parsing in the byte realm even more complex.<br>
<br>
Probably there are some other ways to 'de-bundle' those messages first<br>
before prepending them a '/'? (Question to the commmunity)<br>
<font color="#888888"><br>
Roman<br>
</font><br>
P.S.: I think this discussion is still interesting for the list, so I<br>
cc'ed to the list.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
On Mon, 2010-10-25 at 09:41 +0200, Leandro da Mota Damasceno wrote:<br>
> Hi Roman. My print message is returning something like:<br>
><br>
><br>
> mensagem: /#bundle likeliest 1<br>
><br>
><br>
> it was supposed to be /likeliest 1<br>
><br>
><br>
><br>
><br>
> Best,<br>
><br>
><br>
> Leandro<br>
><br>
> On Mon, Oct 25, 2010 at 9:18 AM, Roman Haefeli <<a href="mailto:reduzent@gmail.com">reduzent@gmail.com</a>><br>
> wrote:<br>
> Sorry, I definitely missed your reply then. Can you post the<br>
> error<br>
> message again?<br>
><br>
> Roman<br>
><br>
><br>
> On Mon, 2010-10-25 at 02:46 +0200, Leandro da Mota Damasceno<br>
> wrote:<br>
> > It partially worked. It seems to be something ALMOST there,<br>
> but I got<br>
> > an error message. I posted a few days ago. But it's<br>
> definitely the<br>
> > best solution right now<br>
> ><br>
> > On Sun, Oct 24, 2010 at 10:45 PM, Roman Haefeli<br>
> <<a href="mailto:reduzent@gmail.com">reduzent@gmail.com</a>><br>
> > wrote:<br>
> > On Sat, 2010-10-23 at 09:40 +0200, Leandro da Mota<br>
> Damasceno<br>
> > wrote:<br>
> > > Hi<br>
> > ><br>
> > ><br>
> > > I would like to apologize for the private emails.<br>
> it's that<br>
> > when I<br>
> > > reply to the messages they go to the author, not<br>
> the list.<br>
> > Weird.<br>
> > > that's not what happens in other mailing lists...<br>
> > ><br>
> > ><br>
> > > So, I have tried to fix the standalone as jasch<br>
> suggested,<br>
> > but i got<br>
> > > all sorts of error messages. I would have to work<br>
> almost<br>
> > from scratch<br>
> > > and if my knowledge on PD is still in beginner<br>
> level, my<br>
> > knowledge of<br>
> > > max/MSP is almost null. Unfortunately, I'm on a<br>
> deadline to<br>
> > have this<br>
> > > thing working, so I need a workaround by next<br>
> week.<br>
> > ><br>
> > ><br>
> > > So right now, I'd rather not mess with the<br>
> standalone and<br>
> > working on a<br>
> > > new version by myself in a few weeks from now.<br>
> Martin, I can<br>
> > send you<br>
> > > the patch, but I'm afraid it won't be any helpful<br>
> for this<br>
> > case, since<br>
> > > it depends on dating coming from the standalone. I<br>
> can give<br>
> > it to you,<br>
> > > of course, if you want. But I think it's pretty<br>
> much what<br>
> > has been<br>
> > > described here. The best solution for now I think<br>
> would be<br>
> > to have a<br>
> > > way to get ordinary messages through udp. No OSC<br>
> standards.<br>
> > ><br>
> ><br>
> ><br>
> > Sorry in case I missed it, but did the abstraction I<br>
> sent you<br>
> > recently<br>
> > not work? I don't think, that it should be too<br>
> difficult to<br>
> > find a way<br>
> > to deal with the faulty OSC messages in Pd (so that<br>
> you don't<br>
> > have to<br>
> > touch the standalone max/msp patch).<br>
> ><br>
> > Roman<br>
> ><br>
> ><br>
> ><br>
><br>
><br>
><br>
><br>
><br>
<br>
<br>
</div></div></blockquote></div><br></div></div>