Specify OSC input with IP address and port

micpool's picture

I need to differentiate OSC input by IP address. Is there a reason there is no 'Specify OSC IP Input' node?

Is there a workaround to provide the equivalent?

Thanks

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●○○ — Appeals to current community

Device Picker

Original composition by Magneson. Here it is as a subcomposition for convenient reuse.

This composition outputs a device element from a list, with a separate control panel window for moving forward and backward in the device list. It currently uses List HIDs, but can be swapped out with List MIDI Devices, List OSC Devices, etc.

Composition and supporting files: 

Wildcards in OSC

micpool's picture

The OSC spec allows for wildcards like * and ? but these do not seem to work in Vuo e.g

I receive 2 consecutive messages with addresses /reply/cue_id/someSequenceof16Characters/duration and /reply/cue_id/someSequenceof16Characters/elapsed

I want to use filter by address nodes to route these addresses but I don't know what the someSequenceof16characters are

In OSC I should be able to write the addresses as /reply/cue_id/*/duration and /reply/cue_id/*/elapsed where * represents any characters as per the OSC spec but these don't seem to be recognised by the node for pattern matching. (For some reason the asterisks appear in the edit window for this post, but not in the post so I've attached a screenshot)

Is there something I'm Missing?

Thanks

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro

Implemented in Vuo version: 

Kinect for Xbox One (model 1520) and NImate

I know there is already a feature request for Kinect V2 integration, that would be very useful. I'm just doing some testing with it for the first time now. It works well with NI Mate, much quicker pick-up of the skeleton.

First thing to note is that it gives more joint position than the V1. Could you add a kinect V2 node with these extra OSC addresses please. (I know I could retrieve them manually but always good to have a built in node).

As you may know the NImate developer changed his licence/subscription recently and I asked him what plans he has for future support/development. Not much other than continued support for now it seems, the GL deprecation will probably effect some aspect of the programme in the long run too.

So how possible would adding the skeletal recognition into Vuo be? It would give us something to rely on into the future. (I read that you are considdering using Open NI in a thread somewhere).

Component: 

Notes from Team Vuo

Vuo Pro: 

No — available with both Vuo CE and Vuo Pro

Complexity: 

●○○○ — Up to a few days of work

Potential: 

●●○ — Could expand community

Pages

Subscribe to RSS - OSC