TUIO host and port settings
If required you can configure UPDD TUIO to send touches to different ports depending on which touch screen it comes from, in essence running multiple TUIO servers at once, one for each touch screen. This checkbox switches between using the same TUIO host and port for all displays, and using different settings for each display. When checked, it lists each display configured in the driver and gives a field for setting its host and port. If this is not required then you can define the local IP address and post on which to transmit all touch data. Since most usage cases for a TUIO server is to have it running locally on the same computer that the TUIO client programs are running on then a reasonable default configuration is for it to use localhost with the default TUIO IP address (127.0.0.1), port number (3333) and packet size.
Divide X axis
When unchecked, all UPDD touches are converted directly to TUIO cursors without any changes to the parameterization of their coordinates. So all devices will use a range of 0.0 - 1.0 for the x coordinate of the TUIO cursors, and it will not be possible to distinguish which UPDD device they originated from.
When checked, each UPDD device will be given, in left to right order, a different, equal portion of the X-axis which its TUIO cursors will be parameterized to. This allows a TUIO client to determine which touch device a cursor originates from. For example, if there are four UPDD devices, then all touches on the leftmost device will be converted to TUIO cursors where their minimum X value is 0 and their maximum X value is 0.25. The touches on the second device from the left will have a parameterization of 0.25 to 0.5, the third device will have a parameterization of 0.5 to 0.75, and so on. The left to right order is determined by the system's display configuration. To get the proper coordinates for a TUIO device, simply reparameterize the X coordinates to a range of 0.0 to 1.0. The Y coordinates are unaffected
If Mouse Emulation is enabled all applications will receive mouse emulation clicks. Applications receiving touches via TUIO interface may not want to also receive mouse emulation clicks and this option is used to specify one or more process names that should not receive mouse emulation clicks. Whenever a process matching one of the names is ‘front most’ mouse emulation will be automatically disabled.
Once a window from any defined apps becomes ‘front most’, mouse emulation will automatically turn itself off, regardless of the setting in the system tray menu.
Indicates if TUIO server is to be invoked at system start. If TUIO is installed as part of the driver installation this is set automatically.
The TUIO server time stamps TUIO frames. By default this is as close as possible to 60 frames per second as per the TUIO specification. This setting can be used to transmit the frames at the same rate they are received from the driver albeit this does not conform to the TUIO specification: 0 or off = 60 FPS, 1 or on = UPDD driver rate. Any application written to retrieve frame times should now receive valid timestamps.
In our tests we achieved a TUIO data rate up to about 200 packets per second, although this speed will vary depending on hardware in use.
Other settings are self-explanatory.