This is very cool, thanks so much! Would one also use the same route object followed by unpack to capture things like buttons and sliders? Would that work? Thanks for your videos, I really enjoy your channel.
Thanks for watching! Yes, you could do the same thing with the sliders, but, for TouchOSC specifically, there's a small challenge there: TouchOSC adds a number (e.g. 1, 2, 3, 4), at the start of the message (after the "list") depending on which of the interfaces you're using (you can see this in the [print]). This number LOOKS like a number, but if you try to [route] it like a number, it won't work, because it's actually the SYMBOL "1" (confusing huh?). There are a few choices of solutions to this, but perhaps more that I can go into here... I'll have to make a follow up video soon.
The other month I got my moms old iPad, so I thought it would be nice to put TouchOSC on it, as it still supports that specific iOS version .. except Apple doesn't want my money because the app-store is broken .. meh. I'm also thinking if it would be possible to add OSC capabilities to HVCC using liblo, would be a bit odd to mock the netreceive/send objects though.
