Post Process Plug-ins
This page lists post process plug-ins used in VizMove setups. Post process plug-ins are added from the Configuration pane.
Marker ID
Note: The MarkedID plug-in should be added for both VizMove Walking and VizMove Projection systems. Manual Mode is the recommended mode to use.
Description:
MarkerID is used to resolve the ID's of the markers and prevent swapping.
Data Output:
The plugin will re-number and re-order all the markers so that they match the id programmed into the markers.
Manual Mode Configuration:
When using MarkerID in manual mode, there is no need to set the number of markers in the Markers field of the PPT interface. The plugin will adjust this number automatically.
Make sure either the 3D view is active (automatically enables Talk Mode) or Talk Mode is enabled when in the 2D view. The plugin will not work if Talk Mode is off.
Add the MarkerID Post-Process Plug-in found in the Configuration Pane.
Click the configure button on the plugin to open the MarkerID dialog.
Uncheck the box for Automatically search inventory to enable manual mode.
Select the check boxes for the physical marker ids you would like to have present in the environment.
The physical ID of a marker can be remapped to a different virtual ID. The virtual ID is the number shown in the 3D and marker data views. For typical VizMove setups the physical ID and virtual ID should be the same.
The following image shows the configuration for a single PPT Eyes and Wand in manual mode. PPT Eyes uses marker IDs 1 and 2. PPT Wand uses marker ID 3.
Automatic Mode Configuration:
Set the number of markers to the number of markers that you have available in the Markers field of the PPT interface.
Make sure either the 3D view is active (automatically enables Talk Mode) or Talk Mode is enabled when in the 2D view. The plugin will not work if Talk Mode is off.
Add the MarkerID Post-Process Plug-in.
Click the configure button on the plugin to open the MarkerID dialog.
Click the checkbox for Automatically search inventory.
You must place all of the markers at a location in the room where they are visible and trackable by PPT.
PPT will search for the markers, and then once all are visible, the marker ids will be assigned and used for tracking.
PPT Eyes
Note: Add this plug-in for VizMove Projection systems only.
Description:
PPT Eyes will automatically detect two tracked lights and merge them into a single tracked light with yaw and roll orientation data. The number of markers in the Marker Visibility and Marker Data panels will be reduced by 1. The 3D view should also show a single tracked light with an axis to indicate orientation data.
Note: For VizMove Walking systems, both PPT Eyes markers should be streamed to Vizconnect, so the PPT Eyes plug-in should not be added. Vizconnect merges data from the two markers with inertial sensor data to create a 6DOF head tracker.
MarkerID plugin should be added and configured for both lights of the PPT Eyes. This should be lights 1 and 2 if a single unit is used.
Add the PPT Eyes plug-in after MarkerID.
Click the configure button on the plugin to open the PPT Eyes dialog. Select Use Marker ID. The settings above Use Marker ID will be grayed out and do not apply once User Marker ID is enabled.
Press OK and the two markers should be merged into a single marker with orientation.
Camera Visualization (debugging)
Use When:
You want to find out how many cameras can see a particular point in your tracking space.
Software Configuration:
Add the Camera visualization Post-Process Plug-in found in the Configure Pane.
The plugin will start up with suitable defaults and show you a colored visualization of the tracking space
Options:
Click on the Camera visualization plugin name to specify configuration options for the plugin.
By varying the slider bars, you can alter the plane used to render the tracking quality information.
By adjusting the delta values, you can adjust the density of the calculated space. Use larger values for very large spaces that are slow to calculate.
Data Output:
The plugin uses differing colors to indicate the quality of the tracking space. Red indicates 2 cameras can see the location, orange indicates 3 cameras, while green indicates 4 or more cameras. You should aim to have green for as much of your space as possible.
Ray Visualization (debugging)
Use When:
You want to find out which 2D camera points correspond to 3D tracked markers.
Software Configuration:
Add the Ray visualization Post-Process Plug-in found in the Configure Pane.
The plugin will start up and show rays originating from the currently selected camera.
Click repeatedly on other cameras to turn on and off the rays intersecting each visible marker.
Options:
This plugin has no configurable options.
Data Output:
The output of the plugin shows rays originating from the camera and intersecting 3D points in space.