oscformat splits the address as symbols (aka strings), so the “1” in your address is actually a symbol and not a float which is why it doesn’t match. route doesn’t allow mixed symbols or floats so you need to create an empty route object and send a “symbol 1” message i to its right inlet with a load bang. This explicitly matches to “1” as a symbol.
enohp ym morf tnes
Dan Wilcox danomatika.com robotcowboy.com
On Jul 13, 2019, at 6:01 PM, Mitchell Turner mmturner2468@gmail.com wrote:
Dan, After reading your reply to a separate thread, I took a look at your MrPeach to vanilla OSC patch here:
https://github.com/danomatika/BangYourHead/tree/master/6.Communication
I am trying to adapt your patch to use the TouchOSC app from my iPhone. However, I am running in to a road block. Everything works as expected until the output of [list trim]. At that point, I can print the data but unable to route the data further. The printed message seems fine; it is usually something like: 1 toggle1 1. (This message is the result of turning the first toggle on page 1 on.)
If I send this message “1 toggle1 1” to a [route 1], I expect the message toggle1 1 to come out of the first outlet of route, however, nothing comes out of the first outlet.
My patch looks like this:
[listen 8000( | | [netrecieve -u -b] | | [oscparse] | | [list trim] | | [route 1]
I’d like to have a [route 1 2 3 4] to separate the data coming from the various pages in the OSC app. From there, I’d like to further direct the data using [route fader1 fader 2 toggle1 toggle 2].
Thanks for any help, Mitch