Documentation Center

Viz Engine

Version 3.11 | Published August 27, 2018 ©

Troubleshooting Video Wall Configurations

Please take a look at this section prior to configuring a Video Wall for the first time. It provides solutions for common issues which may arise during setup, and covers the following topics:

It is highly recommended to turn off any Windows scaling features, even if they make it easier to work on Videowalls. Windows scaling can force the Viz Artist GUI to behave in an abnormal way.

Run Viz Engine as Engine and not as Artist mode. The startup should be viz.exe -w

Performance issues

Create a simple scene with a bar moving from left to right and back in an endless loop, and run this scene on the newly configured Video Wall to spot issues such as jittering, tearing effects, etc. When troubleshooting performance issues, always make sure to check the following before investigating further:

Steps to recover from severe NVIDIA Mosaic driver related issues

  1. Remove the NVIDIA drivers.

  2. Shutdown the system.

  3. Ensure that all monitor cables are connected properly to the graphics card.

  4. Boot the system.

  5. Reinstall the NVIDIA drivers.

Experiencing BSOD or system freeze while setting up Mosaic

While operating in Mosaic mode, any changes to the physical setup, such as adding or removing monitors, can cause a system crash resulting in a Blue Screen of Death or complete system freeze. There is a chance to run into follow-up issues (mentioned in this chapter) after the system has rebooted.

Only some displays of the Video Wall display an image

The reasons for this can be many-fold. Please ensure that:

Missing NVIDIA Control Panel settings

Please perform a re-installation of the NVIDIA driver as mentioned in section Steps to recover from severe NVIDIA Mosaic driver related issues. A known cause for this behavior are physical changes to an existing video-wall setup, for instance adding or removing monitors, while operating in Mosaic mode.

images/download/attachments/41781136/videowall_nvidia_control_panel_missing_settings.png

NVIDIA Control Panel crashes

There is a possibility that the NVIDIA Control Panel crashes during Mosaic configuration, although this is not considered a reliable indicator on whether a driver re-installation is required or not. Sometimes the NVIDIA Control Panel can be restarted manually, and usually rebooting the machine should suffice.

Please refer to section Steps to recover from severe NVIDIA Mosaic driver related issues if the issue persists.

Mosaic configuration not supported error

If running with two or more cards, make sure the same outputs are used on each card. For example, if using two DisplayPort outputs and one DVI output on the first card, the same outputs must be used on the second card, etc. Failure to do so may result in Mosaic setup failure, with an error message stating that the configuration is not supported.

G-Sync status LEDs or Topology reports indicate a synchronization issue

If the status LEDs on the NVIDIA G-Sync status LEDs indicate an issue, or the topology reports "The display is locked to the house sync signal" for all displays, the topology view may indicate that everything is fine at first sight. However, when taking a closer look at the topology, it reveals that all monitors seem to sync to the house sync signal instead of reporting that the display is locked to the frame lock sync pulse:

images/download/attachments/41781136/videowall_nvidia_gsync_locked_to_house_signal.png
This indicates that there exists an synchronization issue which needs to be fixed. Solving this may require going through one or several of the following steps:

  1. Re-establish synchronization

    1. Disable display synchronization in section Synchronize Displays.

    2. Re-establish synchronization.
      See the NVIDIA Mosaic Configuration for 1080i50 or NVIDIA Mosaic Configuration for 1080i60M sections for more detailed instructions.

  2. Reconnect G-SYNC signal cables

    1. Physically disconnect the sync cable from the G-SYNC card.

    2. Reconnect the sync cable.

    3. Switch synchronization back on in the NVIDIA Control Panel. Go to Synchronize Displays and set the radio button to An external house sync signal. See the NVIDIA Mosaic Configuration for 1080i50 or NVIDIA Mosaic Configuration for 1080i60M sections for more detailed instructions.

    4. Verify the LEDs on the NVIDIA Quadro Sync, or in the Topology Inspector of the NVIDIA Control Panel.

    5. If this does not help, try to reboot the machine.
      In case this does not fix the issue, please:

  1. Disable display synchronization in section Synchronize Displays.

  2. Shutdown the machine.

  3. Check cabling and signal sources.

  4. Reboot the machine.

  5. Re-establish synchronization as mentioned in section Synchronize Displays.

Poor performance when using GFX channels as DVE

On high resolution Video Walls in particular, poor performance may be experienced when using GFX channels as DVEs. This is caused by anti-aliased "blitting". To disable anti-aliasing on GFX channels, open the Viz configuration file, locate the gfx_channels_antialiased string, and set the value to 0. The default value is 1.

Example: gfx_channels_antialiased = 1

Note

Turning on GPUDirect can result in less performance than running without it. There is a workaround for this problem and we recommend to use this setting in video wall setups. Enable the flag use_threaded_IO in the configuration file.

Setting: use_threaded_IO = 1

Jittering on HP Z840

Jittering on the HP Z840 is most commonly caused by a missing swapgroup. Make sure to run the RENDERER_JOIN_SWAPGROUP 1 command to the Engine.

Other synchronization issues

When attaching the connector cables between the graphics card and the G-SYNC card, make sure that the red line on all of the connector cables are facing the card’s mounting bracket, towards the back of the case. Failure to do so can result in synchronization issues.

In rare cases, syncing with only the NVIDIA G-SYNC can result in more stable synchronization. If all else fails, try disconnecting the reference signal from the Matrox board.