- 1 Licensing
- 1.1 Requesting a License
- 1.2 License File
- 1.3 License File Location
- 1.4 Product Licenses
- 1.5 Options Licenses
- 1.6 License Transfer
- 1.7 Troubleshooting
Requesting a License
To request a license, send a mail to Digital Vision :
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.
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.
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.
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 :
- 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.
Licenses are placed into a text file called :
e.g. 00217059af37.flic. Note the extension.
2019.2 (008) and After
Releases from 2019.2 (008) use the Reprise License Manager (RLM).
Licenses are placed into a text file called :
e.g. 00217059af37.lic. Note the extension.
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
|PHOENIX_LICENSE_DIR||For Phoenix products
|LOKI_LICENSE_DIR||For Loki products
|BIFROST_LICENSE_DIR||For Bifrost products
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.
A license has the following format :
Product Version MAC DateCreated Duration Options Code
NucodaLook 2016.1 B8AC2F8BC7EA 19-Aug-2016 5 Enh Res ExtFormats 210BBC7FB1674F7FF969
- 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
|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
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.
An Options license is only valid with a base license string and can not be used on its own.
If you want to transfer your license to a different computer, download the license transfer form :
- DV_license_transfer_form.doc (Word format)
Complete the form, make sure it is signed, then scan it and send it back to us.
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.
For Nucoda (as an example), this would be set as :
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 :
|3.||The license file is called license.flic.
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) 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.||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 (second field e.g. 2014.1)|
|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 license file has format :
So make sure that DATE + DAYS is a within your active period (license is not expired).
|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.|