Difference between revisions of "Support:Licensing"

From DigitalVision
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 29: Line 29:
 
You can send the ID shown to the ''licensing'' department and they will send you a license.
 
You can send the ID shown to the ''licensing'' department and they will send you a license.
  
==== Otherwise : ====
+
==== Using Getmac ====
  
 
To find out your system MAC address on Windows :
 
To find out your system MAC address on Windows :
Line 63: Line 63:
  
 
'''NOTE:''' Run "rlmhostid -h" for help on options.
 
'''NOTE:''' Run "rlmhostid -h" for help on options.
 +
 +
==== RLM Dongle ====
 +
 +
Version 2019.2 and later use the RLM licensing system and support RLM '''hardware dongles''' (contact DVW Sales).
 +
 +
You will need to install the "RLM Sentinel LDK Runtime" :
 +
 +
* https://sentinelcustomer.safenet-inc.com/sentineldownloads/
 +
** e.g. Sentinel HASP/LDK - Windows GUI Run-time Installer
 +
 +
Once installed, the dongle appears under ''Universal Serial Bus Controllers'' and should be visibly "found". The hardware ID is retrieved using "rlmhostid" :
 +
 +
* Type : <tt>rlmhostid.exe rlmid1</tt>
 +
<pre>
 +
rlmhostid v12.4
 +
Copyright (C) 2006-2018, Reprise Software, Inc. All rights reserved.
 +
 +
Hostid of this machine: rlmid1=62db0f65
 +
</pre>
  
 
== License File ==
 
== License File ==
Line 84: Line 103:
 
e.g. 00217059af37.lic. Note the extension.
 
e.g. 00217059af37.lic. Note the extension.
  
 +
'''NOTE:''' A license file can be named anything but we often name it after the host it licenses (e.g. 00217059af37.lic).<br/>'''THE EXTENSION IS IMPORTANT HOWEVER'''.
  
 
A license file can contain more than one license string (e.g. for different software versions) but each license string must be separated from any others with a newline.
 
A license file can contain more than one license string (e.g. for different software versions) but each license string must be separated from any others with a newline.

Latest revision as of 14:29, 5 August 2019

Darrow-up.png

Licensing

Requesting a License

To request a license, send a mail to Digital Vision :

licenses@digitalvision.world

With the mail, please include details :

  • What product you want licensed
  • Your system MAC address (see below)
  • Your name, company name, address and contact details

System MAC Address

If you start the application and get a license error, the error dialog will display the System ID we are looking for.

License-error-dialog.png

The dialog tells you the System ID (MAC address) the application is looking for e.g. in the above dialog we have (for example) :

System ID:
00217059af37

You can send the ID shown to the licensing department and they will send you a license.

Using Getmac

To find out your system MAC address on Windows :

  • Click the Start button
  • Type : cmd (and press enter)

This starts a command console. In the command console :

  • Type : getmac /v > mac.txt

This creates a file mac.txt containing details of your system MAC address.

  • Email us this file, alongside product required, at the address above.

2019.2 and Later

Releases from 2019.2 (008) use the Reprise License Manager (RLM). You can use the RLM tool "rlmhostid" to determine the system ID required. This is installed in :

  • C:\Nucoda\Utilities\Reprise
  • Run by opening a CMD window in the above folder and typing :
    • rlmhostid ether

This will output all possible MAC addresses we can use e.g.

C:\Nucoda\utilities\reprise>rlmhostid.exe ether
rlmhostid v12.4
Copyright (C) 2006-2018, Reprise Software, Inc. All rights reserved.

Hostid of this machine: b8ac6f8bc7ea 0a002700000d

NOTE: Run "rlmhostid -h" for help on options.

RLM Dongle

Version 2019.2 and later use the RLM licensing system and support RLM hardware dongles (contact DVW Sales).

You will need to install the "RLM Sentinel LDK Runtime" :

Once installed, the dongle appears under Universal Serial Bus Controllers and should be visibly "found". The hardware ID is retrieved using "rlmhostid" :

  • Type : rlmhostid.exe rlmid1
rlmhostid v12.4
Copyright (C) 2006-2018, Reprise Software, Inc. All rights reserved.

Hostid of this machine: rlmid1=62db0f65

License File

2019.1 and Earlier

Licenses are placed into a text file called :

  • MAC.flic

e.g. 00217059af37.flic. Note the extension.

2019.2 and Later

Releases from 2019.2 (008) use the Reprise License Manager (RLM).

Licenses are placed into a text file called :

  • MAC.lic

e.g. 00217059af37.lic. Note the extension.

NOTE: A license file can be named anything but we often name it after the host it licenses (e.g. 00217059af37.lic).
THE EXTENSION IS IMPORTANT HOWEVER.

A license file can contain more than one license string (e.g. for different software versions) but each license string must be separated from any others with a newline.

License File Location

The license file is expected to be in a folder as given by the environment variable :

NUCODA_LICENSE_DIR For Nucoda products

e.g. C:\Nucoda\License

PHOENIX_LICENSE_DIR For Phoenix products

e.g. C:\Phoenix\License

LOKI_LICENSE_DIR For Loki products

e.g. C:\Loki\License

BIFROST_LICENSE_DIR For Bifrost products

e.g. C:\BifrostQC\License

Version 2010.0 and earlier

For version 2010.0 and before, the environment variable is DV_LICENSE_DIR. This will probably be set to C:\Digital Vision\License.

Product Licenses

2019.1 and Earlier

A license has the following format :

Product Version MAC DateCreated Duration Options Code

e.g.

NucodaLook 2016.1 B8AC2F8BC7EA 19-Aug-2016 5 Enh Res ExtFormats 210BBC7FB1674F7FF969 

Note :

  • This license was created on 19-Aug-2016 and is valid for 5 days.
  • The duration includes the date it was created on, so the license will expire at the end of 23rd August.
  • The license includes three options : Enh Res ExtFormats

2019.2 and Later

A license has the following format :

LICENSE digitalvis nucoda 2019.2 23-aug-2019 uncounted
hostid=009988001177 issued=22-jul-2019 options="Enh Res ExtFormats"
_ck=9e48d6bd6a sig="60PG4580S1G1XC4M0UBA5RHSDB11R4Q4WW4FWBRA08A14SMA
X0BH1N6Q1QPTMFJCSD915CX7S9TG"
  • The license was created ("issued") on 22-jul-2019
  • The license will expire on 23-aug-2019
  • The license includes three options : Enh Res ExtFormats

Options Licenses

From Release : 2016.1

An "Options" license is a license string where the product is replaced with the string Options e.g.

Options 2016.1 B8AC2F8BC7EA 19-Aug-2016 5 Enh 210BBC7FB1674F7FF969

or for 2019.2 and later (using RLM licenses) :

LICENSE digitalvis options 2019.2 21-aug-2019 uncounted
hostid=009988001177 issued=05-aug-2019 options=Enh
_ck=2e4829b202 sig="60P0451JAWQ8CPWAHJJ206RR7QV7VN6970MRYG022GJ01SV1
HGMYEP3JHXJ2TW26VXNKHWAVS0"

An Options license adds one or more product options to a base (normal) license for a specified period. The base license can be any Digital Vision product (e.g. Nucoda Look, Phoenix Refine etc.).

In the example above, we add the option DVO Enhance to a base license for 5 days (old style) or expiring on 21-aug-2019 (new RLM style).

An Options license is only valid with a base license string and can not be used on its own.

License Transfer

If you want to transfer your license to a different computer, download the license transfer form :

Complete the form, make sure it is signed, then scan it and send it back to us.

Troubleshooting

Follow these steps if you are having problems getting your license to work :

1. To find the license file, we look in a folder given by an environment variable (based on product) e.g.
  • NUCODA_LICENSE_DIR
  • PHOENIX_LICENSE_DIR
  • LOKI_LICENSE_DIR
  • BIFROST_LICENSE_DIR

For Nucoda (as an example), this would be set as :

  • C:\Nucoda\License

and we expect the license file to be called license.flic in the above location.

2. Make sure that the environment variable (e.g. NUCODA_LICENSE_DIR has no odd spaces (e.g. at start or end).

As an example, the following would be wrong :

  • NUCODA_LICENSE_DIR set as "C:\Nucoda\License\ " (note space at end of string)
3. The license file is called MAC.flic (2019.1 and earlier) or MAC.lic (2019.2 and later).

Make sure that there are no hidden extension (e.g. .txt).

To check this : In a file browser, select : Tools / Folder options / View tab / Hide extensions for known file types - make sure this is un-checked.

4. Make sure the license.flic file is the only .flic file in the folder. We check all .flic files in alphabetical order.
5. Make sure the date and time is correct on your computer. Never put the computer clock back!
6. Make sure that the system ID (MAC) in the license string (third field e.g. 003048671219 or "hostid=" field for RLM licenses) is correct for the machine you run on. See above for getting your ID (MAC).
7. The system ID (MAC) must be on an active network interface i.e. it must not be disabled.
8. For 2019.1 and earlier licenses, make sure that the license string is in the license.flic file on one line only (a single line per license string)
9. If the license string has been given to you split over 2 lines with a "\" line continuation character used - delete it when placing the string on a single line i.e.
 Nucoda 2014.2 001F294EAEBC 12-Aug-2009 14 \
 Avid Enh Res Conv 89D82D4CD40EA4234668 

Should be :

 Nucoda 2014.2 001F294EAEBC 12-Aug-2009 14 Avid Enh Res Conv 89D82D4CD40EA4234668 
10. Make sure that the version of software you have installed and are running matches the version in the license.
11. We read the license.flic file from top to bottom and choose the first valid license. If this is an old license, we will use it, and you may still get expiration warnings. Make sure any new license line is before old ones.
12. The 2019.1 license file has format :
  • PRODUCT VERSION MAC DATE DAYS ..

where :

  • DATE = date license created and
  • DAYS = number of days license is valid for

So make sure that DATE + DAYS is a within your active period (license is not expired).

For 2019.2 and later, make sure the date field (fifth, after version) is not in the past.

13. Make sure you are running the correct application, as specified in the license file i.e. run "Phoenix Finish" when the license.flic file specifies "PhoenixFinish" as the product name.
14. Some virtualisation products (e.g. vmware, virtualbox) can interfere with the network devices we find and try and attach to. They may be the cause of license failures. You should uninstall these products and retry the application.