[This article is specific to Player on Windows and Composer.]

Intuiface natively supports the Windows HID for Multi-Touch protocol. In fact, if a touch display is "Windows plug-and-play", you can be sure it is 1) using this protocol, and 2) will work with Intuiface. Display drivers using this protocol are said to be Windows 10 or 11 compliant. In our experience, the majority of touch displays use Windows 10 or 11 compliant drivers. 

With some configuration, Intuiface also supports TUIO 1.x using the /tuio/2Dcur profile.

Working with TUIO 1.x using the /tuio/2Dcur profile

To enable TUIO support, use a simple text editor to modify the Topology and Device sections of the inputdevicesconfiguration.xml file found in the Intuiface Player and Composer installation directories. You need to make this change for each instance of Player on Windows and Composer connected to a TUIO device. These changes will not take effect until Composer and/or Player are restarted.

Topology section

Enter the display resolution to which the TUIO events will be mapped.

<Topology>

    <Display Id="0" Type="Screen">

       <Param Name="Top" Value="0" />
       <Param Name="Left" Value="0" />
       <Param Name="Width" Value="1920" />
       <Param Name="Height" Value="1080" />

    </Display>

</Topology>

Device section

Uncomment the section for ID=0 then update the Screen and Port parameters. The default values - 0 for Screen and 3333 for Port - are correct for most TUIO-based devices. (Just leave the IP value set to "any".)

<Device Id="0" Type="TUIO" Name="TUIO">

  <!-- Screen attached to our TUIO device -->
  <Param Name="Screen" Value="0" />

  <!-- IP address used to receive TUIO messages: an IPv4 address in dotted-decimal notation (ex: 127.0.0.1 for localhost) or the keyword "any"  -->
  <Param Name="IP" Value="any" />

  <!-- UDP port used to receive TUIO messages (3333 by default) -->
  <Param Name="Port" Value="3333" />

</Device>

• The Screen parameter refers to the ID number of the TUIO-based display in the Topology section mentioned above.
• The IP parameter indicates the IP address of the TUIO device. Leave this value set to any if no IP address is defined.
• The Port parameter refers to the network port through which the display's TUIO tracker will pass its events.

Multiple TUIO screens configuration

The example below shows how to configure two side by side FullHD screens in portrait orientation

<Topology>

  <Display Id="0" Type="Screen">
    <Param Name="Top" Value="0" />
    <Param Name="Left" Value="0" />
    <Param Name="Width" Value="1080" />
    <Param Name="Height" Value="1920" />
  </Display>

  <Display Id="1" Type="Screen">
    <Param Name="Top" Value="0" />
    <Param Name="Left" Value="1080" />
    <Param Name="Width" Value="1080" />
    <Param Name="Height" Value="1920" />
  </Display>

</Topology>

<Device Id="0" Type="TUIO" Name="TUIO">

  <!-- Screen attached to our TUIO device -->
   <Param Name="Screen" Value="0" />

  <!-- IP address used to receive TUIO messages: an IPv4 address in dotted-decimal notation (ex: 127.0.0.1 for localhost) or the keyword "any" -->
   <Param Name="IP" Value="any" />

  <!-- UDP port used to receive TUIO messages (3333 by default) -->
   <Param Name="Port" Value="3333" />

</Device>

<Device Id="1" Type="TUIO" Name="TUIO">

  <!-- Screen attached to our TUIO device -->
   <Param Name="Screen" Value="1" />

  <!-- IP address used to receive TUIO messages: an IPv4 address in dotted-decimal notation (ex: 127.0.0.1 for localhost) or the keyword "any" -->
   <Param Name="IP" Value="any" />

  <!-- UDP port used to receive TUIO messages (3333 by default) -->
   <Param Name="Port" Value="3334" />
</Device>

NOTE:

• When you restart Composer or Player you might be warned by your firewall that the application is trying to establish a connection. Just accept it.
• Composer and Player can be configured independently. For example, Composer can be configured for a plug-and-play display while Player is configured for a TUIO device.