I am now wondering how to route OSC messages I get from oscparse. I
would love a behavior similar to routeOSC but would like to stay
within vanilla Pd.
The internal [route] object itself does not allow to parse
more than one layer of OSC address space when receiving messages from
oscparse and seems to have problem with numbers in the address.