See [n_oscformat] in rc-patches which is a wrapper for [oscformat] that accepts mrpeach style messages and sets the address for you.

https://github.com/danomatika/rc-patches

Also, if you are just now switching from mrpeach or the original OSC objects, I made a little turtorial when I was learning Miller's new design approach,
 see mrpeach-to-vanilla-osc.pd in:

https://github.com/danomatika/BangYourHead/tree/master/6.Communication


On Jul 12, 2019, at 7:15 PM, pd-list-request@lists.iem.at wrote:

Date: Fri, 12 Jul 2019 17:48:19 +0200
From: João Pais <jmmmpais@gmail.com>
To: "pd-list@lists.iem.at" <pd-list@mail.iem.at>
Subject: [PD] Problems with oscformat (and oscparse?) and slashes
Message-ID:
<CAN46m5qMcrWTawqghfCUdRM5sQU8J7Ya+-1scgfsdvvUfaKV=w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi all,

I'm having some issues with oscformat and slashes ( / ). Many programs out
there use formats such as "/parameter/bla 1", but both oscformat and
oscparse don't really cope that well with them.

For oscformat:
- it's not possible to send a string starting with a slash, the message
"oscformat: no method for '/aa' " appears.
- A hack can be done by sending a message [set /aa, bang( ...
- ... but this doesn't work if the message to send is /aa 1, as oscparse
will convert it to /aa/1
- defining an object as [oscformat /aa] seems to work, but it will mean
that another oscformat object has to be defined for each single string
being sent: /aa, /aa/a, /aa/b, ...

For oscparse:
- when it receives a message with slashes in it, it removes the slashes
automatically. Which is kind of acceptable, if it's going to be connected
with a normal route. But not that much if the message is going to be worked
on, and resent.

Or is there any other way of doing this? The documentation doesn't present
anything else. It took some time of screaming at the computer until I
compared the results with mrpeach's objects.

--------
Dan Wilcox
@danomatika
danomatika.com
robotcowboy.com