Of course, best of all would be additional functionality on [route] that enables routing by slashes, like the CNMAT [osc-route] max object.

On Tue, Jan 12, 2016 at 10:55 PM, Daniel Iglesia <daniel.iglesia@gmail.com> wrote:
Yes, I've seen that behavior of oscformat and oscparse. And, while I am no expert on the OSC spec, it seems contrary to the intentions of OSC to allow the address and the data to be undifferentiable like that.

Right now, with oscformat/oscparse, there is no ability to differentiate between
/foo/bar baz     (send /foo/bar the data "baz")
and
/foo bar baz     (send /foo the data "bar baz")
as both come out of oscparse as
foo bar baz

That's why I stick to using addresses clumped together with slashes, even if that hampers my ability to route them. Attached is my hacked solution to reconstituting the original addresses. Put it after a [netreceive] with the binary flag on. 





On Tue, Jan 12, 2016 at 10:05 PM, Dan Wilcox <danomatika@gmail.com> wrote:
There is if you transition to [oscparse]. :) Have you worked with the new vanilla  osc objects? The address is broken up into a list and pretended to the message arguments, so routing address and arguments works the same way.

I updated PdParty with built in oscparse functionality in Obj-C, but then again I haven't released it yet so I wasn't afraid of breaking anything, really. It's in the PureData class I believe.

(PdParty Open Beta coming around this weekend.)

enohp ym morf tnes
--------------
Dan Wilcox

On Jan 12, 2016, at 10:39 PM, Daniel Iglesia <daniel.iglesia@gmail.com> wrote:

I had wanted it for compatibility with existing patches that expected the leading slash. 

More detail: it is actually for the PdWrapper.pd that simulates the MobMuPlat app layer when developing on a laptop. The PdWrapper had previously used mrpeach OSC objects which, IIRC, kept the slashes. The editor sends an OSC message on GUI widget interaction, to be routed to the Pd patch being developed by the user. MobMuPlat (on device) reports the OSC message from the widget with the slash, so the PdWrapper.pd should do the same.

Is there a rationale for removing the slashes?




On Tue, Jan 12, 2016 at 9:23 PM, Dan Wilcox <danomatika@gmail.com> wrote:
Why re-add the slashes? You can just use [route] objects directly.


On Jan 12, 2016, at 10:11 PM, pd-list-request@lists.iem.at wrote:

From: Daniel Iglesia <daniel.iglesia@gmail.com>
Subject: Re: [PD] MobMuPlat - data from several iPads to one PC
Date: January 12, 2016 at 10:10:10 PM MST
To: Billy Stiltner <billy.stiltner@gmail.com>


[netreceive -u -b <portNumber>]

spits out ASCII (for me, on OSX, haven't tested linux). Connecting it to an [oscparse] will give the string, but parses out leading slashes. I have a tangled abstraction for re-adding slashes to the start of the OSC address if anyone is interested in that.

Dan