In addition, see mrpeach-to-vanilla-osc.pd in https://github.com/danomatika/BangYourHead/tree/master/6.Communication

I created it to understand the design differences and now I much prefer the built-in functionality using a couple abstractions in my rc-patches

n_oscformat - convenience wrapper for oscformat (sets the address from the first list item like [packOSC])
n_oscreceive - convenience wrapper for netreceive & ocparse
n_oscsend - convenience wrapper for netsend & oscformat

I think using [route] with the osc messaging is great. :)

Maybe I should add this to the wiki. Perhaps we need to make an expanded Pd-Extended to "new vanilla" transition guide...

On Feb 10, 2019, at 10:56 AM, pd-list-request@lists.iem.at wrote:

Date: Sun, 10 Feb 2019 01:56:04 -0800
From: "Scott R. Looney" <scottrlooney@gmail.com>
To: Pd-List <pd-list@lists.iem.at>
Subject: Re: [PD] trying to set up OSC between Unity and PD via
[netreceive] or [iemnet/udpreceive]
Message-ID:
<CAAo07Q2abMbuoJEwdec0+xhWPf+9-Cg5CG1--CF4xQQ3mr4FDQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

OK thanks Christof! [oscparse] seems to do the trick, and formats it as a
list that i can break up. and it seems i have [netreceive] working properly
after all, so that was my error thinking it was broken. it is a bit picky
and seems to work better if i send it a message as to what port to listen
to rather than defining it as an argument initially.

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