Video Wall Processor - Matrox

Video Wall Processor - Matrox

The DISPLAX TILE is compatible with Matrox video wall processors,  such as the QuadHead2Go.


The Matrox QuadHead2Go allows you to create a video wall from a single video source. It's designed for use in various environments, such as digital signage, control rooms, experience centers and entertainment venues.


Video wall processing: The QuadHead2Go can split a single video source into four independent displays, creating a video wall. This makes it ideal for applications that require a large, immersive display.


Here are some of the key functions of the Matrox QuadHead2Go:

  1. Easy setup: The QuadHead2Go is easy to set up and configure, with plug-and-play installation and intuitive software that allows you to adjust and customize your display configuration.
  2. High-quality output: The QuadHead2Go delivers high-quality output, with support for resolutions up to 4K and refresh rates up to 60Hz. It also includes advanced features such as EDID management and frame lock to ensure seamless synchronization across all displays.
  3. Multiple connectivity options: The QuadHead2Go supports a range of connectivity options, including DisplayPort, HDMI, and DVI. It doesn't support daisy-chain between devices, meaning that each QuadHead2Go needs be connected directly to the PC. 




Below is an example of a 4x1 DISPLAX TILE video wall setup built using the Matrox QuadHead2Go. 


The devices used were: 

  • Matrox D-1480 ( graphics card) 
  • Matrox QuadHead2Go (video wall processor)
  • Standard industrial PC



Each step of the configuration is explained below:


  1. Connect the Matrox QuadHead2Go to your computer. The QuadHead2Go has a single input port (the type will depend on the model), so you'll need to connect it to the output port of your graphics card (Matrox D1480). Make sure that the QuadHead2Go is powered on and detected by your computer system.
  2. Connect the DISPLAX TILEs: Connect each of the four DISPLAX TILEs to the Matrox QuadHead2Go using the provided video cables (either HDMI or DisplayPort). The DISPLAX TILEs have a single input port for HDMI, and an IN and OUT port for DisplayPort (need to use the IN), so you'll need to connect each TILE to one of the four output ports of the QuadHead2Go. Ensure that each DISPLAX TILE is securely connected to the QuadHead2Go and powered on.
  1. Connect the Matrox QuadHead2Go to the local network using a RJ45 cable. Make sure that it is connected to the same network/sub-network as your PC.
  2. Once all the TILEs are connected you will need to configure and arrange their layout. For that, you need the Matrox PowerWall software.

    • Related Articles

    • Video Wall Calibration

      DISPLAX Connect version 3.7.0 and later includes the feature, Video Wall Calibration - added to our existing calibration modes to ease the process of calibrating multiple TILEs in a videowall or table, at once. DISPLAX Connect will detect all TILES ...
    • Recommended Hardware

      Computer Windows 10 Pro or superior Intel core i7 500 GB SSD 16 GB DDR4 RAM Graphics card capable of Videowall configurations USB Expansion Ports Graphic cards tested (this is only an example) MATROX D1480 The GPU selected should be suited to your ...
    • DisplayPort

      Selecting DP 11 or DP 12 The DISPLAX TILE has 2 different Display Port protocols available. Each of them offers different solutions for videowall mosaic setups. The available protocols are DP 11 and DP 12. To select either protocol, access the ...
    • Set Up Mosaic - DP 11

      Using the DP 11 mode allows to use the DISPLAX TILE internal videowall processor. In the below example we are covering the steps for a 6 x 1 video wall, arranged in 6 vertical columns, and 1 horizontal row. Since each TILE has a resolution of 1080 x ...
    • Pointer Events

      While developing video wall applications, take into consideration the type of events you need to use. To be able to use multiple touch-points in many or all screens of a video wall at the same time, it is necessary to use Pointer events instead of ...