Viz Engine Release Notes

Version 4.4 | Published March 22, 2022 ©

Viz Engine Release Notes

Viz Engine 4.4.1

Release Date: 2022-03-22

These are the release notes for Viz Engine version 4.4.1. This document describes the user-visible changes that have been made to the software since release 4.4.0.

Installer Notes

The installation wizard guides you through the installation process. Make sure to close any running Viz application prior to the installation. In order to run Viz Artist or Viz Engine independent of a database server, you need to install the Viz Graphic Hub database software locally.

General

The Software ships with a bundle installer containing all necessary components. It is recommended to use the bundle installer when setup needs to be done manually.

  • The Setup application (both MSI and Bundle installer) must be run in Administrator mode.

  • Visual C++ Redistributable files are no longer part of the .msi setup file. These files are now installed with the bundle setup application (VIZENG-13210, VIZENG-12629, VIZENG-12701).

  • The new bundle setup application installs or upgrades Viz Artist together with its required Visual C++ Redistributable files (VIZENG-12936, VIZENG-13804). Upgrade is only possible when Major version is 4 (starting from minor version 1)

  • All files contained in the bundle setup application can be extracted using the /dump commandline option. This creates a sub-folder where the files are extracted (VIZENG-13020).

  • Multiple installations of Viz Engine are not supported.

  • If Adobe After Effects is installed after Viz Engine, then the Viz installer needs to be executed again to install the AE plug-in (VIZENG-7876).

  • The user account must have SeCreateGlobalPrivilege (SE_CREATE_GLOBAL_NAME) enabled.

  • The configuration profiles shipped with Viz Engine guarantee a correct Audio/Video delay to have a proper lip-sync setup or a correct video wall installation. A manual configuration (e.g. number of inputs, clips, etc.) is still necessary after applying these profiles (VIZENG-18861).

  • To use Global Illumination in Viz Artist/Viz Engine, at least Direct X version 9 is required. An installer can be found here: https://www.microsoft.com/en-us/download/details.aspx?id=8109 (VIZENG-19983).

  • The Basic, Viz DataPool, Viz PixelFX, Viz Maps, Viz Extension and Viz Socialize plug-ins are released together with Viz Engine starting with version 4.0.0 and are included in the bundle installer. The basic plug-ins are installed by default.

Windows

  • This software has been tested to run on Windows 10 (LTSC 1809) and Server 2019.

  • Windows transparency effects should be turned off (former known as Aero). In Windows 10 set Show transparency in Windows to Off in Settings > Display and Transparency effects to Off in Settings > Personalization > Colors > More options.

  • Power management and hibernation-mode must be turned off under Windows. You can execute powercfg -h off to remove hiberfil.sys from the hard disk.

  • It is recommended to install the latest Windows Security Updates and Patches, except Nvidia updates.

  • Installations on Windows 10 are only supported on their respective supported hardware (see Supported Systems).

  • Dot.NET framework 4.5 or higher is required (VIZENG-6036).

  • The minimum Windows Installer version is now 5.0.0 (VIZENG-10146).

To run Viz Engine without Administrator privileges you need to grant the following permissions:

  • SeIncreaseBasePriorityPrivilege

  • SeCreateGlobalPrivilege

  • SeCreatePagefilePrivilege

  • SeIncreaseWorkingSetPrivilege

UAC

  • Viz Engine 4.x is UAC aware. Configuration-files, profiles, log-files and additional files are stored in %VIZ_PROGRAMDATA%, which defaults to %ProgramData%\Vizrt\VizEngine. Temporary data is stored in %VIZ_TEMPDATA% which defaults to %TMP%\Vizrt\VizEngine. The default value can be changed in the command line of viz.exe.

  • Existing Lens files are copied from %ProgramFiles% install folder to the new UAC aware %ProgramData% folder during installation (VIZENG-8757).

  • Existing Viz configuration files are copied from %ProgramFiles% install folder to the new UAC aware %ProgramData% folder during installation (VIZENG-7472).

Cinema 4D

  • Cinema 4D LiveLink Installation: The installer searches the following location first: %ProgramFiles%\MAXON\CINEMA 4D R16\plugins (VIZENG-7965).

  • Cinema 4D LiveLink package can be installed any time later by using Viz Artist Installer in Repair mode. Its installation folder is not selectable anymore (VIZENG-8996).

  • Cinema 4D R23 or newer: LiveLink plugin is available at %ProgramFiles%\Vizrt\VizEngine\CINEMA 4D LiveLink\R23 (VIZENG-26332).

Driver Versions

These are the recommended driver versions for various hardware components:

Vendor

Driver Version

Nvidia Ampere, Turing, Volta, Pascal, Maxwell and Kepler GPUs

472.12
511.79 for A4500
419.17 for older boards

Matrox Topology based boards

10.2.102.26111

Bluefish

5.11.0.45

Bluefish Supernova Firmware

145

AJA

14.0.1.40

Codemeter Runtime Kit

7.40.4990

AV PCL/PCI Plura Timecode Reader

5.34

Sentinel Runtime (legacy)

8.11.42480

Nvidia Drivers

Information: Please refer to https://nvidia.custhelp.com/app/answers/detail/a_id/4777/~/nvidia-dch/standard-display-drivers-for-windows-10-faq for information about the DCH and Standard driver versions and how to install a missing Nvidia control panel.

Nvidia driver 472.12 is recommended for Quadro GPUs with Ampere, Turing, Volta, Pascal, Kepler or Maxwell Technology cards. Boards that do not support this version of the driver, should use Rev. 419.17.
This driver generation is the last one supporting Kepler GPUs.

Information: Some GPUs (like M6000) disable GPUDirect support if the wrong Nvidia driver is used!

Nvidia driver configuration (Manage 3D settings):

Setting

Vertical sync

Force Off (except Videowall and systems without video hardware)

Unified Back Buffer

Off

Power management mode

Prefer maximum performance

Antialiasing mode

Override any application setting

Antialiasing setting

4x (4xMS)

Profile

Workstation App - Dynamic Streaming profile (for systems with video hardware)
3D App - Video Editing (for systems without video hardware)

Important: Viz Engine will not start if an outdated driver is used.

Matrox Drivers

  • For Matrox video cards, driver version 10.2.102.26111 is required. This version is mandatory. Pre-Release versions are not supported.

  • Matrox drivers with _EV.exe extension are suitable for Windows 10/Server 2016 systems with secure boot.

  • Uninstall previous versions of Matrox DSXUtils prior to installing this driver.

  • Either DSX-TopologyUtils.exe or DSX-TopologyUtils_EV.exe must be used.

  • Install drivers only from a local drive.

  • Reboot between uninstall and install of drivers, and another time after the installation has finished.

  • The VfW codecs are included in this driver, so uninstall previous versions of the Matrox VfW codecs and do not install any Matrox VfW codecs over the regular driver installation.

Other Drivers

  • The latest firmware for Supernova and Supernova S+ is 145.

  • The latest firmware for Neutron is BlueFirmwareUpdate_Neutron_1i2o_V027, there is no 1in1out firmware any longer.

  • The recommended driver version for Plura AV timecodereader cards is 5.34.

Please refer to the Viz Engine Administrator Guide for which drivers and driver settings to use.

Given that a supported Matrox device is installed, the following codecs are supported for post-rendering with MatroxFileWriter and the ClipOut channels:

  • RLE (animation), playback only

  • H.264

  • Apple ProRes

  • HDV

  • XDCam

  • DVCPro

  • DNxHD (4849)

  • XAVC (UHD requires M264 board)

  • The clog command now includes all child processes. Upon abnormal end, all child processes are terminated before a restart is attempted (VIZENG-11361).

Virtual Environments

The following GPUs are currently supported (Kepler are only supported in Viz Engine Classic Render Pipeline):
The listed driver version is the one the system has been tested with

The following GPUs are supported in virtualized environments:

GPU

A40 (472.12) (2)

NVidia RTX6000 (472.12)

Nvidia Tesla V100 (425.31)

NVidia T4 Tensor Core (471.68)

NVidia M40 (377.35 only)

NVidia K2 (370.28 only) VDGA (1)

A10G (511.65)




NVidia M60 (471.68)

NVidia K2 (370.28 only) VGPU (K280Q, K260Q) (1)






NVidia K520 (370.35 only)(1)

(1) Classic Render Pipeline only.
(2) Tested on A40-8Q.


Viz Engine has been tested to run in the following virtual environments:


Viz Fusion Render Pipeline

Viz Classic Render Pipeline

Amazon Cloud (AWS)


images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg (2)


images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

Microsoft Azure


images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg


images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

fra.me/nutanix

not tested

images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

VMWare ESXi (6.0, 6.50, 7.02)

images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

Alibaba Cloud

not tested

images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

(1)g5.4xlarge, g5.2xlarge and g5.xlarge tested
(2) Tested only, AMD GPUs are not official supported

Note: Backup and Restore on Azure systems are currently not supported.

Bugfixes

Known Issues

General

  • Transition Logic scenes require to have GeomAutoFree = 1 set in the Viz Config file. With inactive GeomAutoFree, system stability is not guaranteed.

  • Interactive Applications within a GFX channel only work in DVE mode in Fullscreen or if the GFX channel has an offset in Fullscreen. Scaled GFX channels or plug-ins that rely on screen coordinates (Grafitti) are not supported.

  • Bones and Skin live motion data tracking requires Tracking Hub 1.1.2 (released together with Viz Engine 3.11).

  • Viz Engine REST interface does not start if a user is Non-Admin (VIZENG-23386).

  • On Air output shows wrong field-of-view if AuxRenderer is enabled, PP in scene editor is disabled and Viz Engine is not in On Air mode.

  • Viz One Browser clip preview might fail on Viz One Versions >=7.0

  • Toggle plugin can not handle backgroundloading of objects or scenes.

Installation

  • Do not use the C4D Version 15R2 patch file(s) unless you are using this version. Otherwise, it prevents Cinema 4D R16 from starting up.

  • When uninstalling Viz Engine, the installer might report that links could not be removed. Please check that none of the desktop.ini files of Windows have write protection. For example, Skype seems to change the permissions of some desktop.ini files with every update.

Windows 10

  • Sentinel runtime installer causes a blue screen when installed on Windows 10 with the latest Microsoft 2004 upgrade. Sentinel runtime 8.11 is required.

  • If the Windows render scaling factor is set to be higher than 100% (for UHD monitor resolutions) it may prevent the render window from showing. Setting the scaling factor back to 100% resolves this issue.

  • Right-clicking on the Taskbar icon of Viz Engine starts a new instance. Starting an additional VizGui process is prevented on Windows 10.

  • Error message "Windows Media Player Rich Preview Handler has stopped working while opening specific clips with Softclip x64". To fix open Windows Explorer > Tools > Folder options > View tab, and deselect Show preview handlers in the preview pane.

Videowall

  • It might happen that Viz Engine is running at half speed on videowall, but goes back to fullspeed if another window comes into focus. If so, start viz.exe -y -w, instead of the regular videowall mode viz.exe -n -w .

  • GFX channels with Alpha != 100% decrease render performance. On video wall setup, gfx_channels_antialiased = 0 should be turned off in the Viz Configuration section RENDER_OPTIONS.

  • Using GPU Direct can cause performance impacts. It is recommended to use use_threaded_IO = 1 on videowall setups, however, some systems like older Supermicro installations require use_threaded_IO to be turned off. It is recommended to run some performance tests with this flag turned on or off.

  • Windows scaling can lead to unwanted side effects.

  • The maximum resolution on videowall setups is limited to 16392px by 16392px.

  • Enabling video output for audio setups is not recommended for performance reasons. It is recommended to grab the audio from one of the HDMI/DP outputs of the Nvidia GPU and use an Audio embedder instead.

Configuration

  • Specifying a path in the configuration file including the # character is not supported. Such paths are cut before the # character.

Viz Classic Render Pipeline

  • Scene Transitions within GFX channels or Superchannels are not supported.

  • Soft Shadow intensity is currently not working together with Global Illumination.

  • We recommend using a warmup scene showing all needed assets once. Under certain circumstances, video and clip surfaces can show up red the first time being used.

  • Playing Audio clips on systems with no physical audio hardware available stops the renderer. You need to turn off audio in the configuration file.

  • On some systems with hybrid graphics, like laptops, the dynamic swapping must be disabled in the BIOS and the stronger GPU must be assigned as default.

  • Stencil-based shadows (Caster/Receiver) do not work on rotated geometry.

  • When changing CurlAuthUnsafe = 1, Viz One Browser does not work anymore.

  • VGA Fullscreen Output is only active if offscreen rendering is turned off. Setting offscreen = 0 in section RENDER_OPTIONS enables fullscreen output.

  • Blending cubemapped images are not supported.

  • Cubemapping with Browser plug-in is not supported.

  • Fonts need to be re-imported to use new Pathrendering or Razor fonts technology.

  • Masks are not supported on Path rendered Fonts (VIZENG-13737).

  • Do not send other commands than IS_RENDERER_READY and database connection commands before this command returns 1, otherwise the renderer and video output might not be initialized.

  • If you encounter stability issues with an Nvidia driver or issues during driver installation, uninstall the old Nvidia driver completely, delete the folder C:\Program Files\Nvidia Corporation\Installer2, install the new driver and select Custom installation, then check-mark the perform clean installation option and finish the installation.

  • Enabling background loading might decrease the render performance by up to 15 frames per second. This is due to OpenGL requirements.

  • M-Zone keyer only works with HD when rendering with full frames.

  • Decreased render performance in HD since Viz Engine 3.5.0 when the ringing filter is activated. Before Viz Engine version 3.5.1 there was no ringing filter for HD. Turn off the ringing filter via configuration or scene-setting to get the same performance.

  • Sporadic Nvidia driver error The Nvidia OpenGL driver lost connection with the display driver and is unable to continue. which in turn causes Viz Engine to freeze. Make sure that the driver profile Workstation App > Dynamic Streaming is selected. Always use the recommended Nvidia driver for your GPU.

  • Possible performance problems with scenes imported from Viz Engine 2.x. Check the following settings (applies to old 2.x scenes only):

    • Image Combining should be set to Multi Texturing in the Render options in the configuration (or flag combine_with_multitex = 1 in the configuration file) to avoid inefficient image combining.

    • Set Key Render Mode to Single Pass in the rendering options in the configuration. The Key Render Mode can also be set on scene level. Available options are:

  • Config (inherit the setting from the configuration).

  • Single Pass (fill and key are rendered in a single pass).

  • Double Pass (fill and key are rendered in separate rendering passes).
    Key rendering results differ between these options for compatibility reasons.

  • Use Single Pass scenes imported from Viz Engine 2.x and Double Pass for Viz Engine 3.x scenes.

  • The configuration flag exec_all_animations in the section RENDER_OPTIONS should be set to 0 if it is not necessary to execute hidden animations.

  • Turn off the VGA preview in On Air mode to avoid performance drops due to multiple rendering of the scene (applies only to video version of Viz Engine).

  • Hide containers that are not required for the current animation.

  • Re-import fonts directly with the Viz Engine.

  • Grid picking currently only works for Cube and Cylinder geometry.

  • The behavior of scripts with cyclic dependencies to other scripts is undefined. Avoid cyclic dependencies.

  • Bad performance when using multiple dynamic scenes, even if they are set inactive. To avoid unnecessary updates, change the Update mode in Dynamic Scenes to Auto instead of Always.

  • CLR LOAD command can crash Viz if not used correctly. Required function signature: static int pwzMethodName(String pwzArgument).

  • Alpha setting for DVEs is not correctly supported when a scene is used nested using a GFX channel (VIZENG-10212).

  • Glow plug-in drops performance when used on multiple containers and rendered within a GFX channel or viewport tile (VIZENG-11342).

  • Scene transitions do not work when dynamic images from different folders are involved. Dynamic images always need to be stored directly in the root folder dynamic and references must point there. Dynamic images in a subfolder of the dynamic folder or any other folder are not found.

  • Font option "lighted" has no effect on fonts rendered with type "vector" (VIZENG-18941)

  • 16-bit PNG images are not rendered properly when imported with compression.

  • Transition Logic scenes use Scene-in-Scene loading now instead of merged geometries. To switch back to the old merged geometries workflow, set TransitionLogicUseMergedGeometries = 1.

  • Classic Shadows are rendered incorrectly if Lens Distortion is active and Background Texture is used.

Post Renderer

  • Cause of performance issues rendering fullscreen sequences in UHD is not supported.

  • Ghosting effect in post-rendered interlaced video: Make sure that the Flicker Filter is set to 0 in the post-rendering options of the Video Render plug-in.

  • Post-rendering does not work properly if onair_no_videoout flag = 1 (Videowall mode).

  • Post-rendering does not work properly if TriCaster integration is active and output format is set to User Defined or Fullscreen.

  • DVCPRO expects 720x480 in NTSC resolution. Please set the correct output width in AVIRenderer.

  • The alpha channel cannot be rendered with Intel Indeo 5.10 codec. This codec is not supported.

Matrox

  • Clips in VideoIO4 and BitsperComponent = 10, Clips with Alpha need to have a ClipIn[n].ContainsAlpha = 1 configured.

  • The configuration ClipIn[n]. UseV210 and ClipIn1. ContainsAlpha are mutually exclusive and should not be enabled at the same time.

  • When using Video IO4, the overall delay is one field higher than IO3. This is caused by the required A/B buffer of IO 4.

  • A program output channel needs to be defined. Pure preview or Cleanfeed is not supported.

  • HDR output on UHD 2SI requires at least a Quadro P6000 GPU.

  • HDR input support is currently for HLG only.

  • Only two DVE UHD inputs are supported at 50Hz. For 60M formats, only two texture inputs are supported. (X.mio3)

  • Animating UHD DVE scaling might result in jittering. You need to increase the VideoDelayDVE setting to 2.

  • Mixing different frame rates with clips processed by a M.264 board is not supported and causes jittering.

  • Upgrading the FPGA can cause a PCI error during the boot process on certain systems. Unattended upgrading of the FPGA is not recommended.

  • Watchdog is only supported in 50/60M and 60Hz frequencies.

  • When using 3G formats (1080p/UHD) or the Zero-Frame-Delay Mixer, autosensing of the sync signal is not supported due to incompatible H-/V-phases, that are set in the process.

  • Instead, either Tri-Level or Blackburst must be used together with correct H-/V-Phase. This might result in a missing key signal (VIZENG-11708).

  • For dualchannel systems, please perform the following steps after enabling the watchdog to ensure the correct state is written to the Matrox Board:

    1. Start Channel 1.

    2. Wait until channel has started up and topology has been written.

    3. Start Channel 2.

    4. Wait until channel has started up and topology has been written.

    5. Exit channel 2.

    6. Exit channel 1.

    7. Start channel 1.

    8. Wait until channel has started up and topology has been written.

    9. Start channel 2.

  • ClipOut channel does not work when Matrox0.VideoOut1.FrameBufferDelay is set to zero (VIZENG-16373).

  • UHD Clip Playback with M264 S1/S2/S3 alone requires color conversion on the shader level. Use of GPU direct is not recommended (VIZENG-20700).

  • Two Sample Interleave (2SI) clips played as DVE not supported.

  • Cutting of Audio tracks should not be done at all, as this results in a crackling noise. Always use a crossfade to change audio sources.

  • 10-bit texture inputs are only supported in IO mode V4.

  • Monitoring live, clip and genlock status via SNMP is not supported (SNMP was deprecated and is no longer supported by Microsoft).

X.mio3 Boards

  • If the Viz instance is closed unexpectedly, the X.mio3 topology might get unusable. To reset the topology, enable ResetTopology in the config file, restart Viz, close it and start Viz again.

  • X.mio3 IP boards should have an active signal connected to SFP A prior to booting the system.

  • Turning on the Cleanfeed Feature increases the delay by one frame.

  • It is not recommended to change the framegroup of any input signal while Viz Engine is running.

  • Texture delay with PAL/NTSC, GPUDirect and Fast Texture Mode is five instead of four fields. Turn off GPUDirect for four fields delay (VIZENG-16955).

  • When using watchdog together with a clean feed, the watchdog triggers on the clean feed connector rather than the program output (VIZENG-16589).

X.mio5 Boards

  • Standard Definition (PAL and NTSC) resolutions are not supported by X.mio5 IP boards according to the 2110 standard.

  • Streampunk ledger RDS does not list the Matrox X.mio5 IP nodes. This is due to some old NMOS APIs that are partially deprecated.

  • Riedel Explorer fails listing the X.mio5 IP nodes. Riedel Explorer automatically selects NMOS API Version 1.3 instead of 1.2. It is possible to select the used API version manually if you switch to static mode and/or enable version downgrade in the Riedel Explorer.

  • The Matrox based NDI input implementation is not supported on X.mio5. Use the native NDI implementation instead (VIZENG-24454).

The X.mio5 IP board has been tested to support up to 12 Inputs (1080i 50 and 60M) on a 10GbE network.

The X.mio5 SDI board has been tested to support up to 6 UHD inputs (4x12G SDI + 2xSquare Division 3G inputs)

DSX.core Dongleless

  • In configuration mode the Matrox and Video Output: Clip Output sections are greyed out, because licenses are not acquired in Configuration Mode. The section is accessible through the configuration page of Viz Artist.

  • If used together with a DSX.core dongle, all DSX.core licenses are listed. Make sure to set the correct serial number in the configuration file.

  • When using the Engine in Artist mode the console might be flooded with the following warning during startup "WARNING: VizEngine-0[20456]:VideoClipInOut_SystemTopology::SequenceVizIn WaitForPBO timed out."

  • UHD resolutions cannot be selected in the output resolution list. However, UHD can be defined in the config file in SECTION VIDEO config flag name output_system, one of the following formats can be set based on the used setup:

    • 2160P_5000_SMPTE2036_UHDTV1

    • 2160P_5994_SMPTE2036_UHDTV1

Other Video Boards

  • When Viz Engine is in On Air mode, there might be audio distortions using Bluefish cards (VIZENG-8853).

  • Bluefish Supernova S+ cards can only be used in a Virtual Set Environment if GPUDirect is disabled and the board is synced to Blackburst/Trilevel.

  • GPUDirect is currently not supported in combination with AJA boards (VIZENG-15532).

  • Clips played with the DirectShow Clip Player might stutter with AJA boards on Windows 10 systems (VIZENG-10279).

  • Video inputs are not supported in IO mode V4 with Bluefish boards.

  • Fusion Render Pipeline is not supported with IO mode V3 using AJA boards.

  • Softwaremode SHM is only available in io_mode = V3 only

  • VML Player is available on io_mode = V4 only

Nvidia

  • When the computer is running out of virtual page size and the user keeps ignoring the low memory warnings in the console, the Nvidia driver may cause Viz Engine to crash.

  • The Nvidia driver doesn't recognize other GPUs under certain circumstances in combination with video wall mosaic installations. Remove and reinstall the driver.

Graphic Hub

  • Communication with the Graphic Hub Server might fail if virtual network adapters are active. Please disable all virtual adapters or increase the timeout.

  • If the connection to the Namingserver fails, please verify the communication port in the config file (Port 19396).

Changes

Upcoming Changes

  • Hardlock support for legacy licensing will be removed in 5.0.

Supported Hardware and Software

This software has been tested to run on:

  • Windows 10 (LTSC 1809)

  • Windows 10 (LTSC 21H2)

  • Windows Server 2019, Windows Server 2016

Note: Only English Operating System(s) are supported.

Supported Systems

System

Lenovo P620

DELL R3930

DELL Precision R7920

HP Z8

HP Z4

HP Z840

HP Z440

HP ZBook 17G6

HPE DL380 Gen9

Supported GPUs

Ampere GPUs

Turing GPUs

Volta GPUs

Pascal GPUs

Maxwell GPUs

Kepler GPUs (2)

RTX A6000

RTX 6000

GV100

NVidia Quadro P6000

Nvidia Quadro M6000

Nvidia Quadro K6000

RTX A5000

RTX 5000


NVidia Quadro P5200

Nvidia Quadro M4000

Nvidia Quadro K5000

RTX A4500 (1)

RTX 4000


Nvidia Quadro P4200

Nvidia Quadro M2000

Nvidia Quadro K5200

RTX A4000

RTX 3000


Nvidia Quadro P4000


Nvidia Quadro K4000

RTX A2000

T 1000


Nvidia Quadro P3200


Nvidia Quadro K4200




Nvidia Quadro P2200


Nvidia Quadro K2000




Nvidia Quadro P2000


Nvidia Quadro K2200




Nvidia Quadro P1000



Orange entries are recommended for rendering photo-realistic graphics on Viz Reality Fusion pipeline.

(1) Requires driver version 511.79.
(2) Please note that Nvidia driver branch 47x will be the last one supporting Kepler GPUs.


Supported Video Boards

Video Board

Configuration

Matrox X.mio5 SDI

up to 4 12G SDI input with up to 4 SDI 12G SDI outputs
variable configuration from 12in0out to 0in12out.

Matrox X.mio5 IP

Three IP Streams in, three IP Streams out (1080p60M)

Matrox X.mio3 Full Height

Various input/output configurations from 48 to 84

Matrox X.mio3 IP

Two IP Streams in, two IP Streams out

Matrox X.mio3 12G

Two 12G inputs, two 12G outputs

Matrox M.264 S1/S2/S3/S4

H.264 Encoder/Decoder board

Matrox DSX LE 4 /8

Various input/output configurations from 08 to 80

Matrox DSX LE 4 /4

Various input/output configurations from 04 to 40

Matrox DSX LE 4 IP

Various input/output configurations from 04 to 40

Bluefish Epoch Neutron

Two video inputs, two video outputs (fill & key)

Bluefish Epoch 4K Supernova

Two video inputs, two video outputs (fill & key)

Bluefish Epoch Supernova S+

Two video inputs, two video outputs (fill & key)

AJA IO4K (1)

Two video inputs, two video outputs (fill & key)

AJA IO4K Plus

Two video inputs, two video outputs (fill & key)

AJA Kona IP (1) (2)

One IP Stream in, one IP Stream out

AJA Kona 3G (1)

Two video inputs, two video outputs (fill & key)

AJA Kona 4

Two video inputs, two video outputs (fill & key)

(1) Set to end of life by vendor

(2) JPEG2000 license is end of life by vendor

Please refer to the Viz Engine Administrator Guide for which drivers and driver settings to use.


Viz Engine 4.4.0

Release Date: 2021-12-20

These are the release notes for Viz Engine version 4.4.0. This document describes the user-visible changes that have been made to the software since release 4.3.1.

Installer Notes

The installation wizard guides you through the installation process. Make sure to close any running Viz application prior to the installation. In order to run Viz Artist or Viz Engine independent of a database server, you need to install the Viz Graphic Hub database software locally.

General

The Software ships with a bundle installer containing all necessary components. It is recommended to use the bundle installer when setup needs to be done manually.

  • The Setup application (both MSI and Bundle installer) must be run in Administrator mode.

  • Visual C++ Redistributable files are no longer part of the .msi setup file. These files are now installed with the bundle setup application (VIZENG-13210, VIZENG-12629, VIZENG-12701).

  • The new bundle setup application installs or upgrades Viz Artist together with its required Visual C++ Redistributable files (VIZENG-12936, VIZENG-13804). Upgrade is only possible when Major version is 4 (starting from minor version 1)

  • All files contained in the bundle setup application can be extracted using the /dump commandline option. This creates a sub-folder where the files are extracted (VIZENG-13020).

  • Multiple installations of Viz Engine are not supported.

  • If Adobe After Effects is installed after Viz Engine, then the Viz installer needs to be executed again to install the AE plug-in (VIZENG-7876).

  • The user account must have SeCreateGlobalPrivilege (SE_CREATE_GLOBAL_NAME) enabled.

  • The configuration profiles shipped with Viz Engine guarantee a correct Audio/Video delay to have a proper lip-sync setup or a correct video wall installation. A manual configuration (e.g. number of inputs, clips, etc.) is still necessary after applying these profiles (VIZENG-18861).

  • To use Global Illumination in Viz Artist/Viz Engine, at least Direct X version 9 is required. An installer can be found here: https://www.microsoft.com/en-us/download/details.aspx?id=8109 (VIZENG-19983).

  • The Basic, Viz DataPool, Viz PixelFX, Viz Maps, Viz Extension and Viz Socialize plug-ins are released together with Viz Engine starting with version 4.0.0 and are included in the bundle installer. The basic plug-ins are installed by default.

Windows

  • This software has been tested to run on Windows 10 (LTSC 1809) and Server 2019.

  • Windows transparency effects should be turned off (former known as Aero). In Windows 10 set Show transparency in Windows to Off in Settings > Display and Transparency effects to Off in Settings > Personalization > Colors > More options.

  • Power management and hibernation-mode must be turned off under Windows. You can execute powercfg -h off to remove hiberfil.sys from the hard disk.

  • It is recommended to install the latest Windows Security Updates and Patches, except Nvidia updates.

  • Installations on Windows 10 are only supported on their respective supported hardware (see Supported Systems).

  • Dot.NET framework 4.5 or higher is required (VIZENG-6036).

  • The minimum Windows Installer version is now 5.0.0 (VIZENG-10146).

To run Viz Engine without Administrator privileges you need to grant the following permissions:

  • SeIncreaseBasePriorityPrivilege

  • SeCreateGlobalPrivilege

  • SeCreatePagefilePrivilege

  • SeIncreaseWorkingSetPrivilege

UAC

  • Viz Engine 4.x is UAC aware. Configuration-files, profiles, log-files and additional files are stored in %VIZ_PROGRAMDATA%, which defaults to %ProgramData%\Vizrt\VizEngine. Temporary data is stored in %VIZ_TEMPDATA% which defaults to %TMP%\Vizrt\VizEngine. The default value can be changed in the command line of viz.exe.

  • Existing Lens files are copied from %ProgramFiles% install folder to the new UAC aware %ProgramData% folder during installation (VIZENG-8757).

  • Existing Viz configuration files are copied from %ProgramFiles% install folder to the new UAC aware %ProgramData% folder during installation (VIZENG-7472).

Cinema 4D

  • Cinema 4D LiveLink Installation: The installer searches the following location first: %ProgramFiles%\MAXON\CINEMA 4D R16\plugins (VIZENG-7965).

  • Cinema 4D LiveLink package can be installed any time later by using Viz Artist Installer in Repair mode. Its installation folder is not selectable anymore (VIZENG-8996).

  • Cinema 4D R23 or newer: LiveLink plugin is available at %ProgramFiles%\Vizrt\VizEngine\CINEMA 4D LiveLink\R23 (VIZENG-26332).

Driver Versions

These are the recommended driver versions for various hardware components:

Vendor

Driver Version

Nvidia Ampere, Turing, Volta, Pascal, Maxwell and Kepler GPUs

472.12
419.17 for older boards

Matrox Topology based boards

10.2.102.26084

Bluefish

5.11.0.45

Bluefish Supernova Firmware

145

AJA

14.0.1.40

Codemeter Runtime Kit

7.21a

AV PCL/PCI Plura Timecode Reader

5.34

Sentinel Runtime (legacy)

8.11.42480

CodeMeter Drivers

  • The Server Search list may be reset when upgrading Codemeter Runtime. Please make sure that the Server Search list is correct after an upgrade.

  • Version 7.21a of CodeMeter driver is recommended due to security flaws in recent versions.

Nvidia Drivers

Information: Please refer to https://nvidia.custhelp.com/app/answers/detail/a_id/4777/~/nvidia-dch/standard-display-drivers-for-windows-10-faq for information about the DCH and Standard driver versions and how to install a missing Nvidia control panel.

Nvidia driver 472.12 is recommended for Quadro GPUs with Ampere, Turing, Volta, Pascal, Kepler or Maxwell Technology cards. Boards that do not support this version of the driver, should use Rev. 419.17.

Information: Some GPUs (like M6000) disable GPUDirect support if the wrong Nvidia driver is used!

Nvidia driver configuration (Manage 3D settings):

Setting

Vertical sync

Force Off (except Videowall and systems without video hardware)

Unified Back Buffer

Off

Power management mode

Prefer maximum performance

Antialiasing mode

Enhance the application setting

Antialiasing setting

4x (4xMS)

Profile

Workstation App - Dynamic Streaming profile (for systems with video hardware)
3D App - Video Editing (for systems without video hardware)

Important: Viz Engine will not start if an outdated driver is used.

Matrox Drivers

  • For Matrox video cards, driver version 10.2.100.26084 is required. This version is mandatory. Pre-Release versions are not supported.

  • Matrox drivers with _EV.exe extension are suitable for Windows 10/Server 2016 systems with secure boot.

  • Uninstall previous versions of Matrox DSXUtils prior to installing this driver.

  • Either DSX-TopologyUtils.exe or DSX-TopologyUtils_EV.exe must be used.

  • Install drivers only from a local drive.

  • Reboot between uninstall and install of drivers, and another time after the installation has finished.

  • The VfW codecs are included in this driver, so uninstall previous versions of the Matrox VfW codecs and do not install any Matrox VfW codecs over the regular driver installation.

Other Drivers

  • The latest firmware for Supernova and Supernova S+ is 145.

  • The latest firmware for Neutron is BlueFirmwareUpdate_Neutron_1i2o_V027, there is no 1in1out firmware any longer.

  • The recommended driver version for Plura AV timecodereader cards is 5.34.

Please refer to the Viz Engine Administrator Guide for which drivers and driver settings to use.

Given that a supported Matrox device is installed, the following codecs are supported for post-rendering with MatroxFileWriter and the ClipOut channels:

  • RLE (animation), playback only

  • H.264

  • Apple ProRes

  • HDV

  • XDCam

  • DVCPro

  • DNxHD (4849)

  • XAVC (UHD requires M264 board)

  • The clog command now includes all child processes. Upon abnormal end, all child processes are terminated before a restart is attempted (VIZENG-11361).

Upgrade Notes

  • The configuration file for Viz Engine has a new naming scheme starting with version 4.0, and can be found at %ProgramData%\Vizrt\VizEngine\VizEngine-{instance}.cfg.

  • Existing Viz 3 configuration files, Genlock and IP configuration settings are migrated automatically by Viz Engine.

  • Viz Engine version 4.x and later no longer support Viz IO.

  • The old Shared Memory output is not supported on the Fusion Pipeline.

  • Scenes using the BrowserCEF plug-in automatically migrate to use the new Browser plug-in.

  • For scenes utilizing the new Fusion Keyer (Virtual Sets) it is recommended to use the new Video IO mode V4 pipeline. Talent Reflection, Holdout Matte and fusion keyed assets within the scene tree do not work properly when using the v3_io.

Information: Viz Engine is not forward compatible. Opening scenes created in this version of Viz Engine might drop warnings when opening in previous versions.

Licensing Model

  • images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/warning.svg Starting with Viz Engine version 4.0.0 the VALID/Sentinel/Hardlock Dongle is not supported anymore, except for a WIBU license bound to VALID/Sentinel dongle ID.

  • The same set of WIBU licenses are available as in Viz Engine 3.10.0 and later. However, since the WIBU license format (data stored in the license) on which Viz Engine version 4.0.0 and later relies on changed, it may require a refresh/reactivation of existing licenses that lack this information. If an error with "This might be caused by an outdated WIBU license." is shown, the WIBU licenses in the container need to be updated/renewed. All licenses issued after the end of March 2019 should contain this data already.

  • The Codemeter Runtime (installed with the bundle installer) is required to use the WIBU license system. Details can be found in the manual in the WIBU-based Licensing System section of the Viz Engine Administrator Guide. Please refer to the documentation on how to apply a license container.

  • Cloud-based installations require a license server, standalone cloud installations are not supported.

  • images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/warning.svg When licenses are shared between different applications (for example, Viz Engine and Service Host on the same machine) then CodeMeter Runtime 7.10b needs to be used. In CodeMeter 7.20 or higher this does not work anymore and one license will be allocated per application. When only one application is consuming licenses (Viz Engine) on a machine the latest version of the CodeMeter Runtime can be used.

Other Upgrade Notes

  • X.open dongles are no longer supported as of missing USB driver support for Windows 10.

  • Viz Engine is not forward compatible! A scene saved with this version might look different if you open it in a previous version. This affects scenes containing more than four streaming channels.

  • Viz Engine does not support half-height rendering anymore.

  • Lens distortion uses a slightly different norm since revision 54263. If you need older lens files, please use use_lens_compatibility_mode = 1 in the config file.

  • Viz Artist is now being started by the Viz Engine process and not by command file anymore. If you start viz.exe and VizGui.exe independently, the Restart Current option fails.

A 64-bit version of each codec must be installed to work with Softclip64. Most codecs come with an installation manual on how to correctly install them.

Softclip64 has been tested to work with the following 64-bit codecs:

  • HuvYuff Version 2.1.1

  • Lagarith Version 1.3.27

  • Newtek SpeedHQ

Virtual Environments

The following GPUs are currently supported (Kepler are only supported in Viz Engine Classic Render Pipeline):
The listed driver version is the one the system has been tested with

The following GPUs are supported in virtualized environments:

GPU

A40 (472.12) (2)

NVidia RTX6000 (472.12)

Nvidia Tesla V100 (425.31)

NVidia T4 Tensor Core (471.68)

NVidia M40 (377.35 only)

NVidia K2 (370.28 only) VDGA (1)





NVidia M60 (471.68)

NVidia K2 (370.28 only) VGPU (K280Q, K260Q) (1)






NVidia K520 (370.35 only)(1)

(1) Classic Render Pipeline only.
(2) Tested on A40-8Q.


Viz Engine has been tested to run in the following virtual environments:


Viz Fusion Render Pipeline

Viz Classic Render Pipeline

Amazon Cloud (AWS)


images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg (2)


images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

Microsoft Azure


images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg
images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg


images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

fra.me/nutanix

not tested

images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

VMWare ESXi (6.0, 6.50, 7.02)

images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

Alibaba Cloud

not tested

images/s/dh98gj/8401/c8e689b733d823db3be6f6ba15b91b9c98719cfa/_/images/icons/emoticons/check.svg

(2) Tested only, AMD GPUs are not official supported

Note: Backup and Restore on Azure systems are currently not supported.

Changes

Upcoming Changes

  • 2SI based shader will be removed in the next Viz Engine version. Future versions will only support 2SI using hardware firmware.

  • Support for Aja Kona IP will be removed in the next version of Viz Engine.

  • Video IO mode V3 will be removed in the next Viz Engine version.

  • Classic Text support in Fusion Renderer will be removed in the next Viz Engine version. Fusion text will fully replace the old text solution.

  • The Video Renderer plug-in will be removed in the next Viz Engine version. Use the VFWRenderer post-render plug-in instead.

  • Softclip DrawPixels BG will be removed in the next version of Viz Engine.

Changes: Plug-ins

  • Pablo plugin has been removed

  • TreeProps plugin has been removed

  • Normal Shader has been removed

Known Issues

General

  • Intel® Xeon® Processor E5 v3 is known to have a major impact on stability and performance.

  • Transition Logic scenes require to have GeomAutoFree = 1 set in the Viz Config file. With inactive GeomAutoFree, system stability is not guaranteed.

  • Interactive Applications within a GFX channel only work in DVE mode in Fullscreen or if the GFX channel has an offset in Fullscreen. Scaled GFX channels or plug-ins that rely on screen coordinates (Graffiti) are not supported.

  • Bones and Skin live motion data tracking requires Tracking Hub 1.1.2 (released together with Viz Engine 3.11).

  • Viz Engine REST interface does not start if a user is Non-Admin (VIZENG-23386).

  • On Air output shows wrong field-of-view if AuxRenderer is enabled, PP in scene editor is disabled and Viz Engine is not in On Air mode.

  • Viz One Browser clip preview might fail on Viz One Versions >=7.0

Installation

  • Do not use the C4D Version 15R2 patch file(s) unless you are using this version. Otherwise, it prevents Cinema 4D R16 from starting up.

  • When uninstalling Viz Engine, the installer might report that links could not be removed. Please check that none of the desktop.ini files of Windows have write protection. For example, Skype seems to change the permissions of some desktop.ini files with every update.

Windows 10

  • Sentinel runtime installer causes a blue screen when installed on Windows 10 with the latest Microsoft 2004 upgrade. Sentinel runtime 8.11 is required.

  • If the Windows render scaling factor is set to be higher than 100% (for UHD monitor resolutions) it may prevent the render window from showing. Setting the scaling factor back to 100% resolves this issue.

  • Right-clicking on the Taskbar icon of Viz Engine starts a new instance. Starting an additional VizGui process is prevented on Windows 10.

  • Error message "Windows Media Player Rich Preview Handler has stopped working while opening specific clips with Softclip x64". To fix open Windows Explorer > Tools > Folder options > View tab, and deselect Show preview handlers in the preview pane.

Videowall

  • It might happen that Viz Engine is running at half speed on videowall, but goes back to fullspeed if another window comes into focus. If so, start viz.exe -y -w, instead of the regular videowall mode viz.exe -n -w .

  • GFX channels with Alpha != 100% decrease render performance. On video wall setup, gfx_channels_antialiased = 0 should be turned off in the Viz Configuration section RENDER_OPTIONS.

  • Using GPU Direct can cause performance impacts. It is recommended to use use_threaded_IO = 1 on videowall setups, however, some systems like older Supermicro installations require use_threaded_IO to be turned off. It is recommended to run some performance tests with this flag turned on or off.

  • Windows scaling can lead to unwanted side effects.

  • The maximum resolution on videowall setups is limited to 16392px by 16392px.

  • Enabling video output for audio setups is not recommended for performance reasons. It is recommended to grab the audio from one of the HDMI/DP outputs of the Nvidia GPU and use an Audio embedder instead.

Configuration

  • Specifying a path in the configuration file including the # character is not supported. Such paths are cut before the # character.

Viz Classic Render Pipeline

  • Scene Transitions within GFX channels or Superchannels are not supported.

  • Soft Shadow intensity is currently not working together with Global Illumination.

  • We recommend using a warmup scene showing all needed assets once. Under certain circumstances, video and clip surfaces can show up red the first time being used.

  • Playing Audio clips on systems with no physical audio hardware available stops the renderer. You need to turn off audio in the configuration file.

  • On some systems with hybrid graphics, like laptops, the dynamic swapping must be disabled in the BIOS and the stronger GPU must be assigned as default.

  • Stencil-based shadows (Caster/Receiver) do not work on rotated geometry.

  • When changing CurlAuthUnsafe = 1, Viz One Browser does not work anymore.

  • VGA Fullscreen Output is only active if offscreen rendering is turned off. Setting offscreen = 0 in section RENDER_OPTIONS enables fullscreen output.

  • Blending cubemapped images are not supported.

  • Cubemapping with Browser plug-in is not supported.

  • Fonts need to be re-imported to use new Pathrendering or Razor fonts technology.

  • Masks are not supported on Path rendered Fonts (VIZENG-13737).

  • Do not send other commands than IS_RENDERER_READY and database connection commands before this command returns 1, otherwise the renderer and video output might not be initialized.

  • If you encounter stability issues with an Nvidia driver or issues during driver installation, uninstall the old Nvidia driver completely, delete the folder C:\Program Files\Nvidia Corporation\Installer2, install the new driver and select Custom installation, then check-mark the perform clean installation option and finish the installation.

  • Enabling background loading might decrease the render performance by up to 15 frames per second. This is due to OpenGL requirements.

  • M-Zone keyer only works with HD when rendering with full frames.

  • Decreased render performance in HD since Viz Engine 3.5.0 when the ringing filter is activated. Before Viz Engine version 3.5.1 there was no ringing filter for HD. Turn off the ringing filter via configuration or scene-setting to get the same performance.

  • Sporadic Nvidia driver error The Nvidia OpenGL driver lost connection with the display driver and is unable to continue. which in turn causes Viz Engine to freeze. Make sure that the driver profile Workstation App > Dynamic Streaming is selected. Always use the recommended Nvidia driver for your GPU.

  • Possible performance problems with scenes imported from Viz Engine 2.x. Check the following settings (applies to old 2.x scenes only):

    • Image Combining should be set to Multi Texturing in the Render options in the configuration (or flag combine_with_multitex = 1 in the configuration file) to avoid inefficient image combining.

    • Set Key Render Mode to Single Pass in the rendering options in the configuration. The Key Render Mode can also be set on scene level. Available options are:

  • Config (inherit the setting from the configuration).

  • Single Pass (fill and key are rendered in a single pass).

  • Double Pass (fill and key are rendered in separate rendering passes).
    Key rendering results differ between these options for compatibility reasons.

  • Use Single Pass scenes imported from Viz Engine 2.x and Double Pass for Viz Engine 3.x scenes.

  • The configuration flag exec_all_animations in the section RENDER_OPTIONS should be set to 0 if it is not necessary to execute hidden animations.

  • Turn off the VGA preview in On Air mode to avoid performance drops due to multiple rendering of the scene (applies only to video version of Viz Engine).

  • Hide containers that are not required for the current animation.

  • Re-import fonts directly with the Viz Engine.

  • Grid picking currently only works for Cube and Cylinder geometry.

  • The behavior of scripts with cyclic dependencies to other scripts is undefined. Avoid cyclic dependencies.

  • Bad performance when using multiple dynamic scenes, even if they are set inactive. To avoid unnecessary updates, change the Update mode in Dynamic Scenes to Auto instead of Always.

  • CLR LOAD command can crash Viz if not used correctly. Required function signature: static int pwzMethodName(String pwzArgument).

  • Alpha setting for DVEs is not correctly supported when a scene is used nested using a GFX channel (VIZENG-10212).

  • Glow plug-in drops performance when used on multiple containers and rendered within a GFX channel or viewport tile (VIZENG-11342).

  • Scene transitions do not work when dynamic images from different folders are involved. Dynamic images always need to be stored directly in the root folder dynamic and references must point there. Dynamic images in a subfolder of the dynamic folder or any other folder are not found.

  • Font option "lighted" has no effect on fonts rendered with type "vector" (VIZENG-18941)

  • 16-bit PNG images are not rendered properly when imported with compression.

  • Transition Logic scenes use Scene-in-Scene loading now instead of merged geometries. To switch back to the old merged geometries workflow, set TransitionLogicUseMergedGeometries = 1.

  • Classic Shadows are rendered incorrectly if Lens Distortion is active and Background Texture is used.

Post Renderer

  • Cause of performance issues rendering fullscreen sequences in UHD is not supported.

  • Ghosting effect in post-rendered interlaced video: Make sure that the Flicker Filter is set to 0 in the post-rendering options of the Video Render plug-in.

  • Post-rendering does not work properly if onair_no_videoout flag = 1 (Videowall mode).

  • Post-rendering does not work properly if TriCaster integration is active and output format is set to User Defined or Fullscreen.

  • DVCPRO expects 720x480 in NTSC resolution. Please set the correct output width in AVIRenderer.

  • The alpha channel cannot be rendered with Intel Indeo 5.10 codec. This codec is not supported.

Matrox

  • Clips in VideoIO4 and BitsperComponent = 10, Clips with Alpha need to have a ClipIn[n].ContainsAlpha = 1 configured.

  • The configuration ClipIn[n]. UseV210 and ClipIn1. ContainsAlpha are mutually exclusive and should not be enabled at the same time.

  • When using Video IO4, the overall delay is one field higher than IO3. This is caused by the required A/B buffer of IO 4.

  • A program output channel needs to be defined. Pure preview or Cleanfeed is not supported.

  • HDR output on UHD 2SI requires at least a Quadro P6000 GPU.

  • HDR input support is currently for HLG only.

  • Only two DVE UHD inputs are supported at 50Hz. For 60M formats, only two texture inputs are supported.

  • Animating UHD DVE scaling might result in jittering. You need to increase the VideoDelayDVE setting to 2.

  • Mixing different frame rates with clips processed by a M.264 board is not supported and causes jittering.

  • Upgrading the FPGA can cause a PCI error during the boot process on certain systems. Unattended upgrading of the FPGA is not recommended.

  • Watchdog is only supported in 50/60M and 60Hz frequencies.

  • When using 3G formats (1080p/UHD) or the Zero-Frame-Delay Mixer, autosensing of the sync signal is not supported due to incompatible H-/V-phases, that are set in the process.

  • Instead, either Tri-Level or Blackburst must be used together with correct H-/V-Phase. This might result in a missing key signal (VIZENG-11708).

  • For dualchannel systems, please perform the following steps after enabling the watchdog to ensure the correct state is written to the Matrox Board:

    1. Start Channel 1.

    2. Wait until channel has started up and topology has been written.

    3. Start Channel 2.

    4. Wait until channel has started up and topology has been written.

    5. Exit channel 2.

    6. Exit channel 1.

    7. Start channel 1.

    8. Wait until channel has started up and topology has been written.

    9. Start channel 2.

  • ClipOut channel does not work when Matrox0.VideoOut1.FrameBufferDelay is set to zero (VIZENG-16373).

  • UHD Clip Playback with M264 S1/S2/S3 alone requires color conversion on the shader level. Use of GPU direct is not recommended (VIZENG-20700).

  • Two Sample Interleave (2SI) clips played as DVE not supported.

  • Cutting of Audio tracks should not be done at all, as this results in a crackling noise. Always use a crossfade to change audio sources.

  • 10-bit texture inputs are only supported in IO mode V4.

  • Monitoring live, clip and genlock status via SNMP is not supported (SNMP was deprecated and is no longer supported by Microsoft).

X.mio3 Boards

  • If the Viz instance is closed unexpectedly, the X.mio3 topology might get unusable. To reset the topology, enable ResetTopology in the config file, restart Viz, close it and start Viz again.

  • X.mio3 IP boards should have an active signal connected to SFP A prior to booting the system.

  • Turning on the Cleanfeed Feature increases the delay by one frame.

  • It is not recommended to change the framegroup of any input signal while Viz Engine is running.

  • Texture delay with PAL/NTSC, GPUDirect and Fast Texture Mode is five instead of four fields. Turn off GPUDirect for four fields delay (VIZENG-16955).

  • When using watchdog together with a clean feed, the watchdog triggers on the clean feed connector rather than the program output (VIZENG-16589).

X.mio5 Boards

  • Standard Definition (PAL and NTSC) resolutions are not supported by X.mio5 boards according to the 2110 standard.

  • Streampunk ledger RDS does not list the Matrox X.mio5 nodes. This is due to some old NMOS APIs that are partially deprecated.

  • Riedel Explorer fails listing the X.mio5 nodes. Riedel Explorer automatically selects NMOS API Version 1.3 instead of 1.2. It is possible to select the used API version manually if you switch to static mode and/or enable version downgrade in the Riedel Explorer.

  • The Matrox based NDI input implementation is not supported on X.mio5. Use the native NDI implementation instead (VIZENG-24454).

The X.mio5 IP board has been tested to support up to 12 Inputs (1080i 50 and 60M) on a 10GbE network.

The X.mio5 SDI board has been tested to support up to 6 UHD inputs (4x12G SDI + 2xSquare Division 3G inputs)

Other Video Boards

  • When Viz Engine is in On Air mode, there might be audio distortions using Bluefish cards (VIZENG-8853).

  • Using GPUDirect together with a Bluefish Supernova S+ might freeze the system due to a low-level driver error (VIZENG-16618). Please refer to the Viz Engine Administrator Guide on how to enable GPUDirect for Bluefish boards.

  • Bluefish Supernova S+ cards can only be used in a Virtual Set Environment if GPUDirect is disabled and the board is synced to Blackburst/Trilevel.

  • GPUDirect is currently not supported in combination with AJA boards (VIZENG-15532).

  • Clips played with the DirectShow Clip Player might stutter with AJA boards on Windows 10 systems (VIZENG-10279).

  • Video inputs are not supported in IO mode V4 with Bluefish boards.

  • Fusion Render Pipeline is not supported with IO mode V3 using AJA boards.

  • Softwaremode SHM is only available in io_mode = V3 only.

  • VML Player is available on io_mode = V4 only.

Nvidia

  • When the computer is running out of virtual page size and the user keeps ignoring the low memory warnings in the console, the Nvidia driver may cause Viz Engine to crash.

  • The Nvidia driver doesn't recognize other GPUs under certain circumstances in combination with video wall mosaic installations. Remove and reinstall the driver.

Graphic Hub

  • Communication with the Graphic Hub Server might fail if virtual network adapters are active. Please disable all virtual adapters or increase the timeout.

  • If the connection to the Naming server fails, please verify the communication port in the config file (Port 19396).

Supported Hardware and Software

This software has been tested to run on:

  • Windows 10 (LTSC 1809)

  • Windows Server 2019, Windows Server 2016

Note: Only English Operating System(s) are supported.

Supported Systems

System

Lenovo P620

DELL R3930

DELL Precision R7920

HP Z8

HP Z4

HP Z840

HP Z440

HP ZBook 17G6

HPE DL380 Gen9

Supported GPUs

Ampere GPUs

Turing GPUs

Volta GPUs

Pascal GPUs

Maxwell GPUs

Kepler GPUs

RTX A6000

RTX 6000

GV100

NVidia Quadro P6000

Nvidia Quadro M6000

Nvidia Quadro K6000

RTX A5000

RTX 5000


NVidia Quadro P5200

Nvidia Quadro M4000

Nvidia Quadro K5000

RTX A4000

RTX 4000


Nvidia Quadro P4200

Nvidia Quadro M2000

Nvidia Quadro K5200

RTX A2000

RTX 3000


Nvidia Quadro P4000


Nvidia Quadro K4000


T 1000


Nvidia Quadro P3200


Nvidia Quadro K4200




Nvidia Quadro P2200


Nvidia Quadro K2000




Nvidia Quadro P2000


Nvidia Quadro K2200




Nvidia Quadro P1000



Orange entries are recommended for rendering photo-realistic graphics on Viz Reality Fusion pipeline.

Supported Video Boards

Video Board

Configuration

Matrox X.mio5 SDI

up to 4 12G SDI input with up to 4 SDI 12G SDI outputs
variable configuration from 12in0out to 0in12out.

Matrox X.mio5 IP

Three IP Streams in, three IP Streams out (1080p60M)

Matrox X.mio3 Full Height

Various input/output configurations from 48 to 84

Matrox X.mio3 IP

Two IP Streams in, two IP Streams out

Matrox X.mio3 12G

Two 12G inputs, two 12G outputs

Matrox M.264 S1/S2/S3/S4

H.264 Encoder/Decoder board

Matrox DSX LE 4 /8

Various input/output configurations from 08 to 80

Matrox DSX LE 4 /4

Various input/output configurations from 04 to 40

Matrox DSX LE 4 IP

Various input/output configurations from 04 to 40

Bluefish Epoch Neutron

Two video inputs, two video outputs (fill & key)

Bluefish Epoch 4K Supernova

Two video inputs, two video outputs (fill & key)

Bluefish Epoch Supernova S+

Two video inputs, two video outputs (fill & key)

AJA IO4K (1)

Two video inputs, two video outputs (fill & key)

AJA IO4K Plus

Two video inputs, two video outputs (fill & key)

AJA Kona IP (1) (2)

One IP Stream in, one IP Stream out

AJA Kona 3G (1)

Two video inputs, two video outputs (fill & key)

AJA Kona 4

Two video inputs, two video outputs (fill & key)

(1) Set to end of life by vendor
(2) JPEG2000 license is end of life by vendor

Please refer to the Viz Engine Administrator Guide for which drivers and driver settings to use.

Documentation

Documentation for Viz Engine, Viz Artist and Viz Plugins are available at the Vizrt Documentation Center:

Support

Support is available at the Vizrt Support Portal.