![codemeter arena license codemeter arena license](https://cdn.wibu.com/fileadmin/images/2-Products/CodeMeter/Available_Platforms_for_CodeMeter.jpg)
Matrox DSX.Core installer corrupts an existing CodeMeter Runtime installation and causes a crash on Engine startup. As a workaround, please use only IP addresses and add them manually using the registry editor.Īdd servers in registry or with the command line utility with IP-Addresses.
#CODEMETER ARENA LICENSE LICENSE#
Matrox DSX.Core license requests cause a crash if hostnames are used in the server search. OEM for VALID/Sentinel/Hardlock dongles is still supported.Īll additional licenses consumable to a core license must come from the same container as the core license. The new WIBU licensing supports OEM starting with Viz Engine 3.12.1 and newer. The binary yes/no VM license introduced in 3.9.1 does not work anymore. Only one license system can be used (VALID/Sentinel/Hardlock or WIBU/CodeMeter). Logs warnings two weeks and every hour prior to license expiration as dedicated Graphic Hub journal message with level 920.Ĭonfigurable WIBU license container location (local, network).Īrtist/Engine startup was changed and no startup helpers are needed anymore (cmd files, started executables). Logs license errors (any grace state or if expired) to the Graphic Hub journal as dedicated log messages with level 820.
#CODEMETER ARENA LICENSE HOW TO#
In Viz Engine 4.0.0/3.14.1 or newer license errors are logged to the Graphic Hub journal (see here how to enable E-Mails). Grace periods for allocated licenses to avoid immediate expiration on network or service interruptions. With Viz Engine 4.0.0 the VALID/Sentinel/Hardlock Dongle will not be supported anymore.ĭongle-less operation on clients with monitoring and logging capabilities. The license system to run on can be configured. VALID/Sentinel/Hardlock Dongle is still working without any changes. Set Up Redundancy for a WIBU License Server Setup Redundancy for a WIBU License Server Setup Graphic Hub Journal-based E-Mail Notifications Starting Viz Engine with Transition License - WIBU license bound to VALID/Sentinel dongle ID Starting Viz Engine with SDI/IP OUT or SDI/IP IN Starting Viz Engine with Frameserver Functionality (MUX Ports) Starting Viz Engine with NDI OUT and/or NDI IN Starting Viz Engine with MezzIP OUT and/or 1xMezzIP IN Starting Viz Engine with WIBU License System Summary of Key Concepts in the New Licensing Systemĭifferences Compared to the Old VALID/Sentinel/Hardlock Licensing Monitor the License System in the Viz Engine Configuration UIĬonfiguration Entries in the Viz Engine Configuration File Why Do We Need to Configure the Licenses?Ĭonfiguring the License System in the Viz Engine Configuration UI Key Features and Workflow of the New Licensing System This section contains the following information:
![codemeter arena license codemeter arena license](http://documentation.vizrt.com/viz-engine-guide/4.2/images/download/attachments/72113336/image2019-8-14_17-24-56.png)
The old VALID/Sentinel/Hardlock Dongle licensing still works, as is. It replaces the previous VALID/Sentinel/Hardlock Dongle licensing system and allows Viz Engine to be used without a physical dongle on each machine, by allocating licenses from a license server on the network.
![codemeter arena license codemeter arena license](https://i.ytimg.com/vi/5qNd8pPnFl0/sddefault.jpg)
This chapter describes management and usage of the licensing system based on CodeMeter from WIBU Systems available in Viz Engine 3.10 and later.