Bug Fixes: Renderer

22 issues

Bug Fixes: Video IO

9 issues

Bug Fixes: Plug-ins

4 issues

Changes: VideoIO

• The version check for the installed Matrox driver is now less restrictive (for example, any 10.1.1xx.xx version can now be used).

• The combination of Matrox and NDI outputs is only possible on system topology based boards (X.mio3 and above).

• NDI output requires the flag NdiOut1.Enable = 1 in Viz Config files. This has been introduced due to performance problems on preview servers.

Changes: Plug-ins

• VideoWall plug-in was renamed to Presets . The location moved from Scene plug-ins > MSE to Scene plug-ins > Control .

• Only the 64bit version of Browser plugin has been updated. The Browser plugin in x86 is the old version

Installation

• Parallel installation of different Viz Engine versions are not supported!

• 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 downgrading the engine to an older version that comes with an older dongle driver, the installation may fail. The dongle driver installer does not allow driver downgrades, so please uncheck the dongle feature in the Viz Engine installer.

• 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.

Hardlock Dongles (Legacy)

• If a license dongle reports license ID 0, or you have a parallel port dongle, or Viz Engine reports a license error and hangs during initialization of the dongle, then uninstall and reinstall the driver: Download and extract Sentinel hardlock driver 6.50, close all Viz applications, manually uninstall the dongle driver via Windows device manager, run haspdinst.exe -fremove -purge. Afterwards, you can manually install the Dongle driver from the Viz installation directory.

• Error message "Unable to start hardlock service with parameters 1119 1058 1. Error code: 48 5 595 1058" during hardlock dongle driver installation. Reboot and try to install Viz Engine again.

• Hardlock driver 7.54 causes a bluescreen on Windows 10 Rev. 2004. Please use version 8.11.4248 included in the Bundle Installer.

Windows 10

• 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.

• With Windows 10 Fall Creators Update (version 1709), Microsoft introduced a new option in Storage sense to automatically delete files from the Downloads folder or delete temporary files that are not being used. This can affect various areas (e.g. temporary downloaded items are no longer available). It is recommended to turn this option off and manually delete temporary files if they are not needed anymore.

Videowall

• Videowall with NDI inputs are currently not supported!

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

• Bezelcorrection in combination with colorcorrection can lead to offsets. This affects Windows 7 only. (VIZENG-11847)

• GFX channels with Alpha != 100% decrease render performance. On videowall setup, gfx_channels_antialiased = 0 should be turned off in 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. We recommend running some performance tests with this flag turned on or off.

• Windows scaling can lead to unwanted side effects.

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

• The video cutout option for videowall setups is not supported any longer because of technical limitations.

• 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.

• It is highly recommended to use a warmup scene utilizing all required Videoinput and Clip surfaces during the initialization process.

Configuration

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

Renderer

• Background loading for geometries or images is only supported for objects stored on Viz Graphic Hub.

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

• Using Transition Logic inside GFX Channels or Superchannels is not supported.

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

• We recommend to use 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 config 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 for VGA versions. Setting offscreen=0 in section RENDER_OPTIONS enabled fullscreen output.

• Blending cubemapped images are not supported.

• Cubemapping with WebBrowser plug-in is not supported.

• Fonts need to be reimported to use new Pathrendering or Razor fonts technology.

• Textures, Masks and Shaders are not (yet) supported on Razor Fonts and 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 a 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 checkmark 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 engine 3.5.0 when the ringing filter is activated. Before 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 the engine to freeze. Make sure that the driver profile Workstation App > Dynamic Streaming is selected. Always use the recommend 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 3.x.

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

• Irregular render performance with the Standard PC version of the engine: Turn off Force Sleep in the rendering options in the configuration. This option only needs to be active on slow systems to keep the Engine responsive.

• 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.

Post Renderer

• Audio is not supported with Matrox File Writer.

• Wrong size of WindFlows plug-in during post render in VGA version.

• Cause of performance issues rendering fullscreen sequences in UHD is not supported (32-bit only).

• 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.

• Quicktime post renderer might fail when Quicktime and Quicktime Alternative are installed at the same time. Uninstall Quicktime Alternative to avoid this.

• Post-rendering does not work properly if onair_no_videoout flag = 1 is set. (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

• 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 M264 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.

• Clip play back without Ringbuffer is not supported when using an X.open only. (VIZENG-10271)

• 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.

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 Engine, close it and start Viz Engine 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

• X.mio5 boards must be synced to a PTP Clock.

• Currently only two of the four SFPs are supported on the Q25 cards.

• Key inputs are not yet supported.

• Audio configuration must match the flow settings - number of tracks, audio packet duration.

• SMPTE ST2022-7 (Seamless Switching aka Redundancy) is not yet supported on the input.

• Ancillary Data flows are not yet supported on the inputs.

• Best Master Clock Algorithm (BMCA) is not yet supported. PTP signals must be received on SFP A.

Other Video Boards

• When Viz Engine is in OnAir 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.

• 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.

• Bluefish Supernova S+ stop during exit on 1080p systems when GPUDirect is turned on, due to an error in the driver in combination with GPUDirect. (VIZENG-16618)

• 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)

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. Install an Nvidia driver later than 182.67. Please also check the console for low memory conditions and adapt your scenes accordingly if necessary.

• 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 connection to the namingserver fails, please verify the communication port in the config file (Port 19396).

Plug-ins

• RTT Shaders consume about 300-400 MB of RAM once they are initialized. If you do not use them or if you don't own a license, it is recommended to disable the plug-ins in the configuration panel in section Plugins. (VIZENG-10224)

• Lagarith Codecs are playing slower on Windows Server Operating Systems. This issue can be solved by enabling Use Multithreading option in Lagarith codec configuration.

Supported Systems

Supported GPUs

Supported Video Boards

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

New Features: Renderer

No issues found

New Features: Video IO

3 issues

Bug Fixes: Renderer

8 issues

Bug Fixes: Video IO

9 issues

Bug Fixes: Plug-ins

6 issues

Changes: VideoIO

• The combination of Matrox and NDI outputs is only possible on system topology based boards (X.mio3 and above).

• NDI output requires the flag NdiOut1.Enable = 1 in Viz Config files. This has been introduced due to performance problems on preview servers.

Changes: Plug-ins

• VideoWall plug-in was renamed to Presets . The location moved from Scene plug-ins > MSE to Scene plug-ins > Control .

Installation

• Parallel installation of different Viz Engine versions are not supported!

• 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 downgrading the engine to an older version that comes with an older dongle driver, the installation may fail. The dongle driver installer does not allow driver downgrades, so please uncheck the dongle feature in the Viz Engine installer.

• 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.

Hardlock Dongles (Legacy)

• If a license dongle reports license ID 0, or you have a parallel port dongle, or Viz Engine reports a license error and hangs during initialization of the dongle, then uninstall and reinstall the driver: Download and extract Sentinel hardlock driver 6.50, close all Viz applications, manually uninstall the dongle driver via Windows device manager, run haspdinst.exe -fremove -purge. Afterwards, you can manually install the Dongle driver from the Viz installation directory.

• Error message "Unable to start hardlock service with parameters 1119 1058 1. Error code: 48 5 595 1058" during hardlock dongle driver installation. Reboot and try to install Viz Engine again.

Windows 10

• 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.

• With Windows 10 Fall Creators Update (version 1709), Microsoft introduced a new option in Storage sense to automatically delete files from the Downloads folder or delete temporary files that are not being used. This can affect various areas (e.g. temporary downloaded items are no longer available). It is recommended to turn this option off and manually delete temporary files if they are not needed anymore.

Videowall

• Videowall with NDI inputs are currently not supported!

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

• Bezelcorrection in combination with colorcorrection can lead to offsets. This affects Windows 7 only. (VIZENG-11847)

• GFX channels with Alpha != 100% decrease render performance. On videowall setup, gfx_channels_antialiased = 0 should be turned off in 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. We recommend running some performance tests with this flag turned on or off.

• Windows scaling can lead to unwanted side effects.

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

• The video cutout option for videowall setups is not supported any longer because of technical limitations.

• 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.

• It is highly recommended to use a warmup scene utilizing all required Videoinput and Clip surfaces during the initialization process.

Configuration

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

Renderer

• Background loading for geometries or images is only supported for objects stored on Viz Graphic Hub.

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

• Using Transition Logic inside GFX Channels or Superchannels is not supported.

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

• We recommend to use 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 config 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 for VGA versions. Setting offscreen=0 in section RENDER_OPTIONS enabled fullscreen output.

• Blending cubemapped images are not supported.

• Cubemapping with WebBrowser plug-in is not supported.

• Fonts need to be reimported to use new Pathrendering or Razor fonts technology.

• Textures, Masks and Shaders are not (yet) supported on Razor Fonts and 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 a 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 checkmark 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 engine 3.5.0 when the ringing filter is activated. Before 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 the engine to freeze. Make sure that the driver profile Workstation App > Dynamic Streaming is selected. Always use the recommend 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 3.x.

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

• Irregular render performance with the Standard PC version of the engine: Turn off Force Sleep in the rendering options in the configuration. This option only needs to be active on slow systems to keep the Engine responsive.

• 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.

Post Renderer

• Audio is not supported with Matrox File Writer.

• Wrong size of WindFlows plug-in during post render in VGA version.

• Cause of performance issues rendering fullscreen sequences in UHD is not supported (32-bit only).

• 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.

• Quicktime post renderer might fail when Quicktime and Quicktime Alternative are installed at the same time. Uninstall Quicktime Alternative to avoid this.

• Post-rendering does not work properly if onair_no_videoout flag = 1 is set. (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

• 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 M264 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.

• Clip play back without Ringbuffer is not supported when using an X.open only. (VIZENG-10271)

• 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.

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 Engine, close it and start Viz Engine 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

• X.mio5 boards must be synced to a PTP Clock.

• Currently only two of the four SFPs are supported on the Q25 cards.

• Key inputs are not yet supported.

• Audio configuration must match the flow settings - number of tracks, audio packet duration.

• SMPTE ST2022-7 (Seamless Switching aka Redundancy) is not yet supported on the input.

• Ancillary Data flows are not yet supported on the inputs.

• Best Master Clock Algorithm (BMCA) is not yet supported. PTP signals must be received on SFP A.

Other Video Boards

• When Viz Engine is in OnAir 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.

• 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.

• Bluefish Supernova S+ stop during exit on 1080p systems when GPUDirect is turned on, due to an error in the driver in combination with GPUDirect. (VIZENG-16618)

• 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)

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. Install an Nvidia driver later than 182.67. Please also check the console for low memory conditions and adapt your scenes accordingly if necessary.

• 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 connection to the namingserver fails, please verify the communication port in the config file (Port 19396).

Plug-ins

• RTT Shaders consume about 300-400 MB of RAM once they are initialized. If you do not use them or if you don't own a license, it is recommended to disable the plug-ins in the configuration panel in section Plugins. (VIZENG-10224)

• Lagarith Codecs are playing slower on Windows Server Operating Systems. This issue can be solved by enabling Use Multithreading option in Lagarith codec configuration.

Supported Systems

Supported GPUs

Supported Video Boards

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

Installation

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

• When downgrading the Engine to an older version that comes with an older dongle driver, the installation may fail. The dongle driver installer does not allow driver downgrades, so please uncheck the dongle feature in the Engine installer.

• 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.

Hardlock Dongles (Legacy)

• If a license dongle reports license ID 0, or you have a parallel port dongle, or Viz Engine reports a license error and hangs during initialization of the dongle, then uninstall and reinstall the driver: Download and extract Sentinel hardlock driver 6.50, close all Viz applications, manually uninstall the dongle driver via Windows device manager, run haspdinst.exe -fremove -purge . Afterwards, you can manually install the Dongle driver from the Viz installation directory.

• Error message "Unable to start hardlock service with parameters 1119 1058 1. Error code: 48 5 595 1058" during hardlock dongle driver installation. Reboot and install Viz Engine again.

Windows 10

• 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.

• With Windows 10 Fall Creators Update (version 1709), Microsoft introduced a new option in Storage sense to automatically delete files from the Downloads folder or delete temporary files that are not being used. This can affect various areas (e.g. temporary downloaded items are no longer available). It is recommended to turn this option off and manually delete temporary files if they are not needed anymore.

Videowall

• Videowall with NDI inputs are currently not supported!

• 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 -n, instead of the regular videowall mode viz.exe -n -w.

• Bezelcorrection in combination with colorcorrection can lead to offsets. This affects Windows 7 only. (VIZENG-11847)

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

• GFX channles as texture will render in the videowall default resolution. To avoid performance problems, the size should be limited to the maximum shown dimensions.

• 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. We recommend running 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.

• The video cutout option for videowall setups is not supported any longer because of technical limitations.

• 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 config file including the # character is not supported. Such paths are cut before the # character.

NDI

• Activating/ Deactivating NDI streams in scene is currently not working. (VIZENG-22388)

Renderer

• EXR images need to be imported without any compression. (VIZENG-22584)

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

• Using Transition Logic inside GFX Channels or Superchannels is not supported.

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

• We recommend to use 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 config 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 for VGA versions. Setting offscreen=0 in section RENDER_OPTIONS enabled fullscreen output.

• Blending cubemapped images are not supported.

• Cubemapping with WebBrowser plug-in is not supported.

• Fonts need to be reimported to use new Pathrendering or Razor fonts technology.

• Textures, Masks and Shaders are not (yet) supported on Razor Fonts and 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 a 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 engine 3.5.0 when the ringing filter is activated. Before 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 the engine to freeze. Make sure that the driver profile Workstation App > Dynamic Streaming is selected. Always use the recommend 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 the engine).

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

• Re-import fonts directly with the Viz Engine 3.x.

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

• Irregular render performance with the Standard PC version of the engine: Turn off Force Sleep in the rendering options in the configuration. This option only needs to be active on slow systems to keep the Engine responsive.

• 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.

Post Renderer

• Audio is not supported with Matrox File Writer.

• Cause of performance issues rendering fullscreen sequences in UHD is not supported (32-bit only).

• Quicktime post renderer might fail when Quicktime and Quicktime Alternative are installed at the same time. Uninstall Quicktime Alternative to avoid this.

• 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

• AVCIntra50 clips played on a M264 board do not render correctly. (VIZENG-22552)

• Saving scenes containing DVE effects on a machine without DVE hardware will drop the DVE information. Save is disabled in this case, but scenes can be saved under a new name (losing the DVE information).

• 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 will need to increase the VideoDelayDVE setting to 2.

• Mixing different frame rates with clips processed by a M264 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.

• Clip play back without Ringbuffer is not supported when using an X.open only. (VIZENG-10271)

• 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.

X.mio3 Boards

• If the Viz instance is closed unexpected, 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

• X.mio5 boards must be sync'd to a PTP Clock.

• Key inputs are not yet supported.

• Audio configuration must match the flow settings - number of tracks, audio packet duration.

Other Video Boards

• When Viz Engine is in OnAir 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.

• 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.

• Bluefish Supernova S+ stop during exit on 1080p systems when GPUDirect is turned on, due to an error in the driver in combination with GPUDirect. (VIZENG-16618)

• 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)

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. Install an Nvidia driver later than 182.67. Please also check the console for low memory conditions and adapt your scenes accordingly if necessary.

• 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 connection to the namingserver fails, please verify the communication port in the config file (Port 19396).

• Icons of EXR images are shown grey.

Plug-ins

• RTT Shaders consume about 300-400 MB of RAM once they are initialized. If you do not use them or if you don't own a license, it is recommended to disable the plug-ins in the configuration panel in section Plugins. (VIZENG-10224)

• Lagarith Codecs are playing slower on Windows Server Operating Systems. This issue can be solved by enabling Use Multithreading option in Lagarith codec configuration.

Key Features

1 issue

New Features: Renderer

No issues found

New Features: Video IO

4 issues

Bug Fixes: Video IO

3 issues

Bug Fixes: Plug-ins

8 issues

Changes: Video IO

• Viz Engine now uses Newtek NDI SDK 3.8. (VIZENG-21939)

• The NDI source created by Viz Engine is now called VizEngine-<instance number>. (VIZENG-22122)

• The list of available NDI sources is now continuously updated in the background. (VIZENG-21956)

• NDI-related Engine commands are now less verbose.

• All commands that begin with NDI*INPUT_CHANNELS are deprecated. (VIZENG-21982). Please refer to the documentation about the NDI related commands.

• The warning messages in Softclip64 have been optimized. (VIZPL-1241)

Installation

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

• When downgrading the Engine to an older version that comes with an older dongle driver, the installation may fail. The dongle driver installer does not allow driver downgrades, so please uncheck the dongle feature in the Engine installer.

• 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.

Hardlock Dongles (Legacy)

• If a license dongle reports license ID 0, or you have a parallel port dongle, or Viz Engine reports a license error and hangs during initialization of the dongle, then uninstall and reinstall the driver: Download and extract Sentinel hardlock driver 6.50, close all Viz applications, manually uninstall the dongle driver via Windows device manager, run haspdinst.exe -fremove -purge . Afterwards, you can manually install the Dongle driver from the Viz installation directory.

• Error message "Unable to start hardlock service with parameters 1119 1058 1. Error code: 48 5 595 1058" during hardlock dongle driver installation. Reboot and install Viz Engine again.

Windows 10

• 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.

• With Windows 10 Fall Creators Update (version 1709), Microsoft introduced a new option in Storage sense to automatically delete files from the Downloads folder or delete temporary files that are not being used. This can affect various areas (e.g. temporary downloaded items are no longer available). It is recommended to turn this option off and manually delete temporary files if they are not needed anymore.

Videowall

• Videowall with NDI inputs are currently not supported!

• 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 -n, instead of the regular videowall mode viz.exe -n -w.

• Bezelcorrection in combination with colorcorrection can lead to offsets. This affects Windows 7 only. (VIZENG-11847)

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

• GFX channles as texture will render in the videowall default resolution. To avoid performance problems, the size should be limited to the maximum shown dimensions.

• 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. We recommend running 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.

• The video cutout option for videowall setups is not supported any longer because of technical limitations.

• 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 config file including the # character is not supported. Such paths are cut before the # character.

Renderer

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

• Using Transition Logic inside GFX Channels or Superchannels is not supported.

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

• We recommend to use 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 config 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 for VGA versions. Setting offscreen=0 in section RENDER_OPTIONS enabled fullscreen output.

• Blending cubemapped images are not supported.

• Cubemapping with WebBrowser plug-in is not supported.

• Fonts need to be reimported to use new Pathrendering or Razor fonts technology.

• Textures, Masks and Shaders are not (yet) supported on Razor Fonts and 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 a 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 engine 3.5.0 when the ringing filter is activated. Before 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 the engine to freeze. Make sure that the driver profile Workstation App > Dynamic Streaming is selected. Always use the recommend 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 the engine).

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

• Re-import fonts directly with the Viz Engine 3.x.

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

• Irregular render performance with the Standard PC version of the engine: Turn off Force Sleep in the rendering options in the configuration. This option only needs to be active on slow systems to keep the Engine responsive.

• 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.

Post Renderer

• Audio is not supported with Matrox File Writer.

• Cause of performance issues rendering fullscreen sequences in UHD is not supported. (32-bit only)

• Quicktime post renderer might fail when Quicktime and Quicktime Alternative are installed at the same time. Uninstall Quicktime Alternative to avoid this.

• 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

• Saving scenes containing DVE effects on a machine without DVE hardware will drop the DVE information. Save is disabled in this case, but scenes can be saved under a new name (losing the DVE information).

• 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 will need to increase the VideoDelayDVE setting to 2.

• Mixing different frame rates with clips processed by a M264 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.

• Clip play back without Ringbuffer is not supported when using an X.open only. (VIZENG-10271)

• 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.

X.mio3 Boards

• If the Viz instance is closed unexpected, 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

• X.mio5 boards must be sync'd to a PTP Clock.

• Key inputs are not yet supported.

• Audio configuration must match the flow settings - number of tracks, audio packet duration.

Other Video Boards

• When Viz Engine is in OnAir 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.

• 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.

• Bluefish Supernova S+ stop during exit on 1080p systems when GPUDirect is turned on, due to an error in the driver in combination with GPUDirect. (VIZENG-16618)

• 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)

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. Install an Nvidia driver later than 182.67. Please also check the console for low memory conditions and adapt your scenes accordingly if necessary.

• 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 connection to the namingserver fails, please verify the communication port in the config file (Port 19396).

Plug-ins

• RTT Shaders consume about 300-400 MB of RAM once they are initialized. If you do not use them or if you don't own a license, it is recommended to disable the plug-ins in the configuration panel in section Plugins. (VIZENG-10224)

• Lagarith Codecs are playing slower on Windows Server Operating Systems. This issue can be solved by enabling Use Multithreading option in Lagarith codec configuration.

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.

• SNMP support comes as an optional software component within the bundle installer. (VIZENG-18652)

• To run Viz Engine in a virtual hosted environment, the Codemeter Runtime library must be installed. The Bundle installer automatically installs all necessary libraries.

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

• Visual C++ Redistributable files and the Hardlock Dongle driver 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)

• 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)

• Matrox drivers are only supported on 64-bit Windows systems.

• Multiple installations of Viz Engine are not supported.

• The installer automatically upgrades (replaces) any existing Viz Artist/Viz Engine 3.6.x/3.7.x installation. However, downgrading is currently not supported. (VIZENG-7098)

• FsMon version 1.1-B53 and MediaFtp version 2.8-B22 are installed to the Viz Engine install folder. (VIZENG-11166)

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

• The installer package is digitally signed. (VIZENG-7378)

• 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 videowall 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)

Windows

• This software has been tested to run on Windows 7, Server 2012 R2, Windows 10 and Server 2016 (64-bit only).

• Aero should be turned off.

• 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 and Hardlock updates.

• Windows 7/10/Server 2016 or Windows Server 2012 R2/SP1 is required, Windows XP is no longer supported.

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

• Minimum Windows Installer version is now 5.0.0 (released with Windows Server 2008 R2 and later and Windows 7 and later.) (VIZENG-10146)

• In case of an error 0xc000007b on Windows 7 system, the update KB2999226 must be installed.

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

• SeIncreaseBasePriorityPrivilege

• SeCreateGlobalPrivilege

• SeCreatePagefilePrivilege

• SeIncreaseWorkingSetPrivilege

Windows 10

• Installations on Windows 10 are only supported on their respective supported hardware. (Z8, Z4, Z840, Z440, Dell 7910, Dell 7920, ML360)

UAC

• Viz version 3.14.0 is UAC aware. Configuration-files, profiles, log-files and additional files are stored in %VIZ_PROGRAMDATA%, which defaults to %ProgramData%\vizrt\viz3. Temporary data is stored in %VIZ_TEMPDATA% which defaults to %TMP%\vizrt\Viz3. The default value can be changed in viz.cmd or on 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)

• Allow starting of viz.exe with UAC turned off as temporary workaround upon a customer demand. It works only on Windows 7 and is not recommended. (VIZENG-12882)

  Old location	New location
  ./VIZ-<Computername>-x-0.cfg	%VIZ_PROGRAMDATA%/VIZ-<Computername>-x-0.cfg (VIZENG-7651)
  ./KeyerData.txt	VIZ_PROGRAMDATA%/KeyerData.txt (VIZENG-7778)
  ./FontNameReplace.txt	%VIZ_PROGRAMDATA%/FontNameReplace.txt (VIZENG-7746)
  ./ignoreOpenGLErrors.txt	%VIZ_PROGRAMDATA%/ignoreOpenGLErrors.txt (VIZENG-7775)
  ./Camera%d.lcb	%VIZ_PROGRAMDATA%/Camera%d.lcb (VIZENG-7833)
  ./SceneList.txt	%VIZ_PROGRAMDATA%/SceneList.txt (VIZENG-8303)
  ./ScriptPlugins/	%VIZ_PROGRAMDATA%/ScriptPlugins/ (VIZENG-7806)
  ./plugin/Data/Topography/	%VIZ_PROGRAMDATA%/Plugin/Topography/ (VIZENG-7875)
  ./plugin/data/BrowserCef	%VIZ_PROGRAMDATA%/Plugin/Topography/ (VIZENG-7875)
  ./plugin/Data/Topography/	%VIZ_PROGRAMDATA%/Plugin/BrowserCEF/BrowserCef.cfg (VIZENG-7653)
  ./plugin/data/BrowserCef/cache	%VIZ_TEMPDATA%/Plugin/BrowserCEF/cache (VIZENG-7653)

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 any more. (VIZENG-8996)

• Starting with Cinema 4D R20, Cinema 4D can configure multiple plug-in directories. So for these newer versions, the user has to add the Viz3/CINEMA 4D LiveLink/R17 path to the Cinema 4D plug-in configuration (VIZENG-20393)

Matrox Driver 10.1.020.24097

Matrox stopped supporting 32-bit platforms. Therefore, there is no 32-bit video version of Viz Engine.

New Licensing Model

Viz Engine 3.10 introduced a new licensing model based on WIBU Codemeter technology. If you upgrade your existing installation, the old licensing model (hardlock) is taken into account. On a fresh installation, the new licensing model is used.

The location of your license can either be a local dongle, a file based license or it can be a license server hosting your licenses. To add a license server, the WIBU Codemeter Web Configuration tool is being used (usually accessible via http://localhost:22352/). Add the desired server in Configuration > Basic > Server Search List.

You can choose between different cores, by default ENG_ENG_CORE is being used. ENG_PRV_CORE is being used for preview purposes only and ART_ARTIST_FREE is being used for the free version of viz engine.

Once you have switched to the new licensing model, you need to restart Viz Engine to fetch all available licenses from your license location. After that, the Viz Config tool presents a list of licenses that might be activated. Once you have configured a license, it is acquired, not matter if you use it or not.

• The Codemeter Runtime License System is required to use the WIBU license model. Please refer to the documentation how to apply a license container.

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

• The Viz preview license server is no longer taken into account and hardlock dongles were never supported in a VM environment. (VIZENG-16760)

• Hardlock dongles should only be renewed by starting Viz Config.

Other Upgrade Notes

• XOpen 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.

• Viz 3.14.0 comes with a native 64-bit codec Softclip plug-in.

  • To exchange the 32-bit version with the new 64-bit one, please run Active_SoftClip_x64.ps1 or Active_SoftClip_win32.ps1 to switch back.

  • The batch files are located in \plugins\disabled.

  • The execution of these scripts require administrator privileges.

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 it.

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

• HuvYuff Version 2.1.1

• Lagarith Version 1.3.27

• Newtek SpeedHQ

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

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

Supported Systems

Supported GPUs

Supported Video Boards

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

Key Features

3 issues

New Features: Renderer

No issues found

New Features: Video IO

4 issues

New Features: Plug-ins

No issues found

Bug Fixes: Renderer

No issues found

Bug Fixes: Video IO

6 issues

Bug Fixes: Plug-ins

3 issues

Changes: Renderer

Changing the textsize box in On Air mode has been disabled due incompatibilities with Windows 10 and Viz Trio. (VIZENG-21106)

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 downgrading the engine to an older version that comes with an older dongle driver, the installation may fail. The dongle driver installer does not allow driver downgrades, so please uncheck the dongle feature in the engine installer.

• 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.

Hardlock Dongles (Legacy)

• If a license dongle reports license ID 0, or you have a parallel port dongle, or Viz Engine reports a license error and hangs during initialization of the dongle, then uninstall and reinstall the driver: Download and extract Sentinel hardlock driver 6.50, close all Viz applications, manually uninstall the dongle driver via Windows device manager, run haspdinst.exe -fremove -purge. Afterwards, you can manually install the Dongle driver from the Viz installation directory.

• Error message "Unable to start hardlock service with parameters 1119 1058 1. Error code: 48 5 595 1058" during hardlock dongle driver installation. Reboot and try to install Viz Engine again.

Windows 10

• 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.

• With Windows 10 Fall Creators Update (version 1709), Microsoft introduced a new option in Storage sense to automatically delete files from the Downloads folder or delete temporary files that are not being used. This can affect various areas (e.g. temporary downloaded items are no longer available). It is recommended to turn this option off and manually delete temporary files if they are not needed anymore.

Videowall

• Videowall with NDI inputs are currently not supported!

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

• Bezelcorrection in combination with colorcorrection can lead to offsets. This affects Windows 7 only. (VIZENG-11847)

• GFX channels with Alpha != 100% decrease render performance. On videowall setup, gfx_channels_antialiased = 0 should be turned off in 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. We recommend running some performance tests with this flag turned on or off.

• Windows scaling can lead to unwanted side effects.

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

• The video cutout option for videowall setups is not supported any longer because of technical limitations.

• 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 config file including the # character is not supported. Such paths are cut before the # character.

Renderer

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

• Using Transition Logic inside GFX Channels or Superchannels is not supported.

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

• We recommend to use 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 config 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 for VGA versions. Setting offscreen=0 in section RENDER_OPTIONS enabled fullscreen output.

• Blending cubemapped images are not supported.

• Cubemapping with WebBrowser plug-in is not supported.

• Fonts need to be reimported to use new Pathrendering or Razor fonts technology.

• Textures, Masks and Shaders are not (yet) supported on Razor Fonts and 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 a 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 checkmark 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 engine 3.5.0 when the ringing filter is activated. Before 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 the engine to freeze. Make sure that the driver profile Workstation App > Dynamic Streaming is selected. Always use the recommend 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 3.x.

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

• Irregular render performance with the Standard PC version of the engine: Turn off Force Sleep in the rendering options in the configuration. This option only needs to be active on slow systems to keep the Engine responsive.

• 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.

Post Renderer

• Audio is not supported with Matrox File Writer.

• Cause of performance issues rendering fullscreen sequences in UHD is not supported (32-bit only).

• 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.

• Quicktime post renderer might fail when Quicktime and Quicktime Alternative are installed at the same time. Uninstall Quicktime Alternative to avoid this.

• Post-rendering does not work properly if onair_no_videoout flag = 1 is set. (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

• 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 M264 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.

• Clip play back without Ringbuffer is not supported when using an X.open only. (VIZENG-10271)

• 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.

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 Engine, close it and start Viz Engine 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

• X.mio5 boards must be synced to a PTP Clock.

• Currently only two of the four SFPs are supported on the Q25 cards.

• Key inputs are not yet supported.

• Audio configuration must match the flow settings - number of tracks, audio packet duration.

• SMPTE ST2022-7 (Seamless Switching aka Redundancy) is not yet supported on the input.

• Ancillary Data flows are not yet supported on the inputs.

• Best Master Clock Algorithm (BMCA) is not yet supported. PTP signals must be received on SFP A.

Other Video Boards

• When Viz Engine is in OnAir 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.

• 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.

• Bluefish Supernova S+ stop during exit on 1080p systems when GPUDirect is turned on, due to an error in the driver in combination with GPUDirect. (VIZENG-16618)

• 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)

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. Install an Nvidia driver later than 182.67. Please also check the console for low memory conditions and adapt your scenes accordingly if necessary.

• 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 connection to the namingserver fails, please verify the communication port in the config file (Port 19396).

Plug-ins

• RTT Shaders consume about 300-400 MB of RAM once they are initialized. If you do not use them or if you don't own a license, it is recommended to disable the plug-ins in the configuration panel in section Plugins. (VIZENG-10224)

• Lagarith Codecs are playing slower on Windows Server Operating Systems. This issue can be solved by enabling Use Multithreading option in Lagarith codec configuration.