Map Input

There are various types of input maps that can be linked into various different objects.

Map Input can also be from external IO connections. These maps translate the incoming data from the IO connection into data that the object can use, for example, positional and rotational coordinates.

Available map inputs vary depending on the object type, therefore not all IO connections can be mapped into every object.

Objects with map input has an event for status change

How to add a Map Input

Under the Maps tab of an object, click on the (+) icon on the right hand side to bring up the list of avaiable sources for the object.

Depending on what IO connections are already added into the project the list of options will vary along with the object that you are trying to add a map input for.

IO connections such as OSC are node-based and must be connected to the object parameters within the board.

All Map Input have the option to add delays to the individual components of the data packet. This option is off by default.

Name	Description
Delay Position	Delay the position data by x number of frames
Delay Rotation	Delay the rotation data by x number of frames
Delay Custom Data	Delay all other custom data by x number of frames

If you do require this, you will need to enable this by clicking on the icon next to the Delay container

Simulated Map Inputs

In the situation where you do not yet have the signal source, but still would like to test the rest of the signal chain or the logic that you would want to build out, Grid Studio provides a few ways for you to simulate some data.

For a single point object, you can make use of the Animator Map Input to animate a point moving around in 3D space.

In the case where you like to have simulated data of a group of points moving around inside a volume, you can use the Volume - Test Map Input.

Object Specific Map Inputs

As mentioned before, depending on the type of IO connections that have been created in the project, different objects will have access to maps from different IO connections. For the specific details, please refer to the tables further down this page.

There are some other internal maps that are available for specific objects to help with creating a better / easier workflow.

• Follow Object

• Volume - Interpolated Point Data

• Volume - Point Data

• Volume - Volume Points

IO Maps In

These are objects which are compatible with receiving data from specific IO connections.

2D Tracking

2D Tracking	Tuio	Optitrack Camera	Sick LMS	Blobtracking Client
Object	Tracker	Tracker Volume	Volume	Volume

3D Tracking

3D Tracking	Blacktrax (RTTrPM)	Open VR	Kinexon	Optitrack (NatNet)	Optitrack (Motive API)	Pozyx	Sewio	PosiStageNet IN
Object	Tracker Laser Fixture	Tracker Skeleton Camera Centroid Volume Moveable Winch Winch 3 Light Fixture Laser Fixture Pixel Multipixel PTZ Camera Spotlight	Tracker Skeleton Camera Centroid Volume Moveable Winch Winch 3 Light Fixture Pixel Multipixel PTZ Camera Spotlight	Tracker Centroid	Tracker Centroid	Tracker Skeleton Camera Centroid Volume Moveable Winch Winch 2 Winch 3 Light Fixture Laser Fixture Pixel Multipixel PTZ Camera Spotlight	Tracker Skeleton Camera Centroid Volume Moveable Winch Winch 3 Light Fixture Laser Fixture Pixel Multipixel PTZ Camera Spotlight	Tracker Volume Pixel

Camera Tracking

Camera Tracking	ARRI CAP	FreeD UDP	Star Tracker (Mo-Sys)	Stype (Stype HF)	Technocrane	Cmotion
Object	Camera	Camera	Tracker Camera	Tracker Camera	Camera	Camera

Kinectic & Sensors

Kinectic & Sensors	MoveCat	Phidget 1047-1	Phidget ENC1000
Object	Tracker Moveable Winch Winch 3	Camera Moveable	Moveable Camera

Protocol

Protocol	OSC	Artnet	SPNet
Object	Volume Area	Tracker Skeleton Camera Rigid Body Centroid Volume Moveable Winch Winch 2 Winch 3 Light Fixture Laser Fixture Pixel Multipixel PTZ Camera Spotlight Area	Tracker Skeleton Camera Rigid Body Centroid Volume Moveable Winch Winch 3 Light Fixture Laser Fixture Pixel Multipixel PTZ Camera Spotlight

Skeleton

Skeleton	Kinect	Perception Neuron	Azure Kinect
Objects	Tracker Skeleton Camera Rigid Body Centroid Volume Moveable Winch Winch 2 Winch 3 Light Fixture Laser Fixture Pixel Multipixel PTZ Camera Spotlight Area	Skeleton	Tracker Skeleton Camera Rigid Body Centroid Volume Moveable Winch Winch 2 Winch 3 Light Fixture Laser Fixture Pixel Multipixel PTZ Camera Spotlight

Controller

Controller	GamePad	Joystick	3D Connecion
Objects	Tracker Skeleton Camera Rigid Body Centroid Volume Moveable Winch Winch 2 Winch 3 Light Fixture Laser Fixture Pixel Multipixel PTZ Camera Spotlight	Tracker	Tracker Camera

Interface

There are nodes within the board that also have mapping capabilities, below are the interface nodes and the compatible IO connections.

Interface Type	Reference	Button	Slider	Colour Field	Controller
IO Connection	Artnet SPNet OpenVR Sewio Kinexon GamePad Kinect Disto Perception Neuron	OSC MIDI Artnet SPNet PSN Out Vertex Commands	Artnet SPNet OpenVR Sewio Kinexon GamePad Kinect Azure Kinect Disto Perception Neuron	OSC Artnet SPNet OpenVR Sewio Kinexon GamePad Kinect Azure Kinect Disto Perception Neuron	OSC Artnet SPNet OpenVR Sewio Kinexon GamePad 3D Connexion Kinect Azure Kinect Disto Perception Neuron