<- views_app_win:start|Views App (Windows) ^ views_app_win:start|Views App (Windows) ^ views_app_win:user_interface|User Interface ->


====== Overview ======
Views App Windows software is a software to show the content of DHD TFT touch screens on your computer. This can be used to control a remote hardware TFT touch screen, to replace a hardware TFT touch screen or to add an additional screen to your DHD system. The configuration works with an [[views_app_win:xml|XML Definiton file]]. This is suitable for administration without an user account management.

The Views App Windows software requires an 52-8511 license on your core device. Each TFT view that should be shown in parallel needs a license in the core, where the view comes from.  

<WRAP center round info 80%>
**Note**\\  If no license was installed the software will only show its firmware version.
</WRAP>

The Views App Windows software can be used for showing the state of a studio in control rooms or to create door panels with current studio state or remote access to diverse functions with views created especially for this software. Also it can be used to control a Series 52 device in combination e.g. with a DAW computer for administration purposes. 

The software is optimized for touch displays but can also be used with a mouse. The software can be used in ''Windowed'' or ''Fullscreen'' mode.

Additionally this software enables you to:
  * switch between different TFTs (of the same or even different Series 52 Core devices) within one instance of the software
  * scale the window size of this softare dependent on the currently selected display
  * protect a display using the "view only" mode
  * use a fullscreen mode
  * use the "always on top" function
===== Specifications =====

A Series 52 Core device handles a Views App Windows software instance the same way it handles a physical DHD TFT (e.g. 52-4010). A Series 52 Core device can handle a maximum of 16 different Central View-TFTs and any number of Fader TFTs. 

<WRAP center round important 80%>
**Important**\\  Minimum Series 52/XC/XD/XS core firmware required: FW 8.0.12
</WRAP>

<WRAP center round info 80%>
**Note**\\  The number of fader TFTs is only limited by the maximum number of physical faders that your DSP core supports. See [[installation:start#functional_range_of_series_52_core_devices|Functional Range of Series 52 Core devices]] for more details on core device limitations.
</WRAP>

A computer that runs the Views App Windows software has to be connected to the DHD Network. Also, the IP address room of the computer and the Series 52 Core Device have to be configured correctly. DHD recommends running devices in 10.X.X.X address space and a separate DHD network. The best way is to have a separate network card in this address room in your computer, if you want to use it with other network applications. See [[network:start|Network Specifications]] for more details.

<WRAP center round important 80%>
**Important**\\  When using two network cards on the same network, make sure not to create loopback routings.
</WRAP>

Also it is possible to have only one connection to a global network. Then there must exist a route from the DHD address space to the address space of the computers (e.g. 192.168.X.X).

Different computers can access the same core. 

It is possible to have multiple instances of Views App Windows software running on the same PC, accessing the same core device. You have to run each instance of Views App Windows software ''.exe'' file from a separate folder, it is not possible to run and use the same ''.exe'' file twice. You can copy the whole folder, including the ''config.xml'' file.

<WRAP center round important 80%>
**Important**\\  Views App Windows software does not support 52/XD/XD2 Core redundancy.
</WRAP>
<WRAP center round important 80%>
**Important**\\  TCP/UDP port 3009 must be opened on your firewall.
</WRAP>

In contrary to the Remote Control software, the 52-8511 Views App Windows software uses UDP connections to communicate with the DSP core. At installations with more complex IT infrastructures, it might be easier to use the Remote Control software which communicates with the DHDOS via TCP.