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