Versions Compared

    Old Version 6

    changes.mady.by.user Unknown User (czerouni)

    Saved on

    compared with

    New Version 7

    changes.mady.by.user Unknown User (czerouni)

    Saved on

    Key

    • This line was added.
    • This line was removed.
    • Formatting was changed.

    Contents

    Table of Contents

    Table of Content Zone
    locationtop

    Types of Licenses

    PipelineFX currently supplies two types of licenses for Qube!:

    • Unlimited - These licenses will allow you to put any number of any kind of job onto a single Worker at the same time. You need one per Worker.
    • Designer - The only restriction Designer licenses have is that they will only allow a single instance of a job on a Worker at one time. They are intended for use in studios where the primary application being used does not support running more than one job on a host, such as Adobe After Effects and Autodesk 3ds Max. The PipelineFX website has

    ...

    ...

    •  about Designer licenses.

    You cannot mix license types on a network - all the Workers must have one type or the other. If there is a mixture installed, they all fall back to Designer licenses.

    Qube! comes with 2 Designer licenses "built in", which can be used for evaluation or for very small networks, without restriction.

    The License File

    The Qube! license file contains the keys for both the Supervisor and Worker, and:

    • Must be installed on the supervisor. The location is documented later on this page -

    ...

    Qube! license keys can be installed either with the WranglerView utility or creating and editing the license file by hand.  License file updates take effect immediately, there is no need to restart the Supervisor or Workers. 

    Installing with Qube! WranglerView

    The simplest way to install the Qube! license is with the WranglerView utility, via the Admin -> Install license menu item.  This option is greyed out if you are not on the Supervisor.

    Warning

    Windows users: you must start WranglerView with "Run as Administrator", even when you are logged in as an admin-equivalent or local administrator. This is due to Window's "elevated privileges" security policy.

    Image Modified

    A dialog will appear, prompting you to copy & paste your license strings.  You have the option of either adding the keys to your existing licenses or overwriting the license file.

    Image Modified

    Note

    Please note that the license string does not include "------------- < snip - do not include this line in the license file > -------------" lines that are in your license email.

    Anchor
    byhand
    byhand
    Installing Licenses by Hand

    You can also install license keys by editing the license file directly.  

    Warning

    You must use a text editor capable of saving out plaintext.

    The license file must end with the extension ".lic".

    Saving the license file with a .rtf, .txt, .doc, extension or in any format other than plaintext will render your license file will be invalid.

    Make a backup copy of the license file before editing it.

    License file location

    Depending on the supervisor's operating system, the qb.lic file is located in:

    • Linux & OSX: /etc/qb.lic
    • Windows Win2K8, Vista, Win7: C:\ProgramData\Pfx\qube\qb.lic
    • Windows XP, XP-64, Win2K3: C:\Windows\qb.lic

     

    Verifying license installation

    With WranglerView 

    Immediately after installing the license, the WranglerView title bar should update and reflect the new license count.

    Image Modified

    Command-line

    You can verify the license count with

    ...

    the qbping

    ...

     utility.

    jburk-15-mbPro:LaunchAgents jburk$ qbping
    supervisor - active - tag: 10.0.1.101 14:10:9F:E3:70:FD 6.4-4 bld-custom osx - - host - 0/10 licenses.

    The license count displayed here means: "0 of 10 licenses in use".

    "I only have 2 licenses now..."

    If after license installation you now show only 2 licenses, this means that your license file was either saved in the wrong format, with the wrong name or extension, or had invalid data added to it.  Restore your original license file (you made a backup copy beforehand, right?), and try again.