VioTrack - Revision history

Strohmy: /* Basic Setup */

2019-03-16T05:56:01Z

‎Basic Setup

2019-03-16T05:44:20Z

‎Basic Setup

2019-03-16T05:43:52Z

‎Basic Setup

2019-03-16T05:42:41Z

2019-03-16T05:41:55Z

2019-03-16T05:40:34Z

2019-03-15T17:04:42Z

‎Good to know:

2019-03-15T14:47:06Z

2019-03-15T14:45:04Z

2019-03-15T14:39:19Z

@@ Line 16: / Line 16: @@
 {{QuestionText|
 * Make sure that there is the Ventuz Sender Tab in VioTrack. If you just have the Sender Tab Ventuz will not be able to receive the tracking data as just the Ventuz sender will send the correct OSC commands to Ventuz. Most of the other render engines getting the tracking data in ASCII format.
-* Make sure that you setup the SDI board dorrectly - In case you face some BSoD (Blues screens) make sure that the Deltacast board is on a at least 4 channels PCIe slot. You can check the channels used in the Ventuz configuration
+* Make sure that you setup the SDI board correctly - In case you face some BSoD (Blues screens) make sure that the Deltacast board is on a at least 4 channels PCIe slot. You can check the channels used in the Ventuz configuration
 }}

@@ Line 15: / Line 15: @@
 {{QuestionText|
-* Make sure that there is the Ventuz Sender Tab. If you just have the Sender Tab Ventuz will not be able to receive the tracking data as just the Ventuz sender will send the correct OSC commands to Ventuz. Most of the other render engines getting the tracking data in ASCII format.
+* Make sure that there is the Ventuz Sender Tab in VioTrack. If you just have the Sender Tab Ventuz will not be able to receive the tracking data as just the Ventuz sender will send the correct OSC commands to Ventuz. Most of the other render engines getting the tracking data in ASCII format.
 * Make sure that you setup the SDI board dorrectly - In case you face some BSoD (Blues screens) make sure that the Deltacast board is on a at least 4 channels PCIe slot. You can check the channels used in the Ventuz configuration
 }}

@@ Line 15: / Line 15: @@
 {{QuestionText|
-* Make sure that there is the Ventuz Sender Tab. If you juast have the Sender Tab Ventuz will not be able to receive the tracking data
+* Make sure that there is the Ventuz Sender Tab. If you just have the Sender Tab Ventuz will not be able to receive the tracking data as just the Ventuz sender will send the correct OSC commands to Ventuz. Most of the other render engines getting the tracking data in ASCII format.
 * Make sure that you setup the SDI board dorrectly - In case you face some BSoD (Blues screens) make sure that the Deltacast board is on a at least 4 channels PCIe slot. You can check the channels used in the Ventuz configuration
 }}

@@ Line 14: / Line 14: @@
 # Follow the steps in the Manual or in the Quick manual to do the calibration
+{{QuestionText|
 ===Offset Calibraton===
@@ Line 56: / Line 59: @@
 * Adjust the shifting with the Fake FoV value

@@ Line 59: / Line 59: @@
 ==Good to know:==
 * Make sure that there is the Ventuz Sender Tab. If you juast have the Sender Tab Ventuz will not be able to receive the tracking data
 * Make sure that you setup the SDI board dorrectly - In case you face some BSoD (Blues screens) make sure that the Deltacast board is on a at least 4 channels PCIe slot. You can check the channels used in the Ventuz configuration

← Older revision		Revision as of 05:40, 16 March 2019
Line 31:		Line 31:


		+
		+	=== Adjust the Delays ===
		+
		+	* You can adjust the delays in VioTrack and also in Ventuz.
		+
		+
		+	=== Adjust the Effect Bleed ===
		+
		+	Because of the Lens Distortion there will be some graphics cut at the edges.
		+	* You can adjust this in the Live Options in Ventuz und Effect Bleed

	===After the offset calibration check the Lens shift:===		===After the offset calibration check the Lens shift:===

← Older revision		Revision as of 14:47, 15 March 2019
Line 1:		Line 1:
		+	==VioTrack F2==
		+	This is a help page for Interactive Asia which explains the setup of VioTrack F. Please always follow the official manual.
		+
	===Basic Setup===		===Basic Setup===

← Older revision		Revision as of 14:45, 15 March 2019
Line 43:		Line 43:

	* Adjust the shifting with the Fake FoV value		* Adjust the shifting with the Fake FoV value
		+
		+
		+
		+
		+
		+	==Good to know:==
		+
		+	* Make sure that there is the Ventuz Sender Tab. If you juast have the Sender Tab Ventuz will not be able to receive the tracking data
		+	* Make sure that you setup the SDI board dorrectly - In case you face some BSoD (Blues screens) make sure that the Deltacast board is on a at least 4 channels PCIe slot. You can check the channels used in the Ventuz configuration

← Older revision		Revision as of 14:39, 15 March 2019
Line 10:		Line 10:
	# Make sure that the sensor camera is fixed strongly after the adjustment		# Make sure that the sensor camera is fixed strongly after the adjustment
	# Follow the steps in the Manual or in the Quick manual to do the calibration		# Follow the steps in the Manual or in the Quick manual to do the calibration
		+
		+
		+
		+	===Offset Calibraton===
		+
		+	If the hardware setup and all the physical values are set then do the offset calibration:
		+
		+	# Make sure that both cameras can see the coded floor
		+	# Uncheck the Disable Master
		+	# set the Error Tolerance to 0
		+	# set the velocity update to 1
		+	# Record offset for about 5 to 10 seconds
		+	# stop recording
		+	# Click Calculate
		+	# Set the Error Tolerance back to 0.02 (recommended)
		+	# Set the Velocity Update back to 0.3 (recommended)
		+