Floating licenses

The Remote Control Software and DSP Control Software are both available as floating licenses (52-8564 and 52-8566).

A floating license is a license stored in one device (if available, on its microSD card) but can be applied to each device in the same Toolbox project and DHD network. When a user wishes to run an application that requires licensing and a floating license is available, it is requested from the device carrying the license and applied to the device the user wishes to connect. When the user finished using the application, the license is made available to other users and devices again.

This works as long as the device carrying the license is connected to the network. The device carrying the floating license can be seen as kind of a “licensing server”.

The DHD system always tries to keep a floating license available. The floating license will only be used when all local licenses on the requested devices are already in use.

Examples

  • Device 1 has 1 Device License for Remote Control (Remote License RL1)
  • Device 2 has 1 Device License for Remote Control (Remote License RL2) and 1 Remote Floating License (FRL)

In OSOM are 2 Remote Views existing:

  • Remote View 1 shows the Mixer from Device 1 and needs RL1.
  • Remote View 2 shows the Mixer from Device 2 and needs RL2.

Using the License

Scenario 1

The system always tries using a Device License first, if available. Is no Device License available, the Floating License is used.

  1. Client 1 opens Remote View 1 and uses RL1
  2. Client 2 opens Remote View 2 and uses RL2
  3. Client 3 can now open Remote View 1 and/or Remote View 2 and uses 1 FRL
  4. Client 4 can not open Remote Views, because all Licenses are used.
Scenario 2

If a Device License is used, a matching and available Floating License is used instead and the Device License is realeased.

  1. Client 1 opens Remote View 1 and uses RL1
  2. Client 2 opens Remote View 2 and uses RL2
  3. Client 1 opens Remote View 2, which is not accepted with RL2 but with FRL. Because with one FRL all RemoteViews can be opened, RL1 is released for other clients.
  4. Client 3 can open only Remote View 1, because all licenses are now used.

Releasing the License

Scenario 1

The Floating Licenses are always released first.

  1. Client 1 opens Remote View 1 and uses RL1
  2. Client 2 opens Remote View 2 and uses RL2
  3. Client 3 can now open Remote View 1 and/or Remote View 2 and uses 1 FRL
  4. Client 4 can not open Remote Views, because all Licenses are used.
  5. Client 3 closes Remote View 1/Remote View 2 and releases FRL for another client
Scenario 2

When a Device License is released, the system tries to reassign the already used Floating Licenses to the free Device License.#

  1. Client 1 opens Remote View 1 and uses RL1
  2. Client 2 opens Remote View 2 and uses RL2
  3. Client 3 can now open Remote View 1 and/or Remote View 2 and uses 1 FRL
  4. Client 4 can not open Remote Views, because all Licenses are used.
  5. Client 1 closes Remote View 1 and releases RL1. The system tries to reassign the FRL from client 3 to the released RL1. This is not accepted because Remote View 2 needs RL2 and this license is not released yet.
  6. client 2 closes Remote View 1 and releases RL2. The FRL from client 3 is now changed to RL1 and RL2 and the FRL is now available for other clients again.