Please take a moment to read our troubleshooting section and check for common errors. If you continue to have issues installing, please contact support and we will be happy to help you. If your organization needs to run a firewall, you will need to check if the ports for the RLM server are open for use.
Check your purchase order to make sure everything matches up version wise. This is especially important for legacy software. If you have more than one Mocha license installed on the server or client machine check to make sure they are not expired licenses.
While rare, sometimes these licenses can conflict with any current ones you have on your system. If your client machine does not connect to the server based on the server name, try replacing the server name with the IP address of the server instead in the license file. You can easily do this via the License Manager or via a text editor.
Check logs and their paths: Read the logs from Mocha and from your server, they will tell you all about what is happening to your machine. If your client machine is not able to connect to the server you may have a networking issue. Try changing the server name in the client license to the IP address of the server instead, or check to see if your host has ".
You can also do this in any text editor by opening up the client license and server license and manually editing the server name. You might roll your eyes at this one, but try uninstalling, restarting your machine, and installing the software again from scratch.
Make sure you follow installation directions off our website exactly. Contact us! Our support team are more than happy to help you fix any floating license issues you may have.
This section will discuss the installation of floating render licenses and how they differ from standard interactive floating licensed. A render license is a specific kind of floating license that only allows rendering of Mocha project output, be it inside a plugin or in the standalone application.
When you are using a floating license, it is broken into two parts: The interactive portion and the rendering portion.
If you are back in the host and not using interactive elements such as layer choosing or opening the GUI, you are using the rendering portion of the license. If you open the Mocha Pro standalone application and a license is available you are entering the interactive portion. If you have the Mocha Pro standalone application closed and are using the mocharender. See the Python guide for more details on rendering with mocharender.
If the interactive license is in use elsewhere or missing, the Mocha GUI will become unlicensed and attempting further work may encrypt your project if you choose to save. If you have no interactive floating licenses available to render with, additional render licenses can be helpful to let you free up interactive licenses elsewhere. If only one person is using Mocha on the network, there are 4 interactive and 10 render licenses still available to use.
If only that one person was using Mocha on the network, they would have 15 render machines available for use including the one they were working with. If another person started working and all machines were in use for rendering, their version of Mocha would be unlicensed, as there would be no available seats. If another user tries to work on a 6th machine, they will open Mocha unlicensed, because all interactive licenses are in use.
They open an existing project with Mocha in it or render from the command line , they will be able to render, because all render licenses are available. If 5 people are using Mocha on the network already, there would be 11 render machines available for use including the one the user was presently working with.
If another person stopped working in Mocha, the interactive license would be released, and a new machine would then be free to either use for work interactive or render non-interactive by another user. The installation of a render license is exactly the same as that of a standard interactive floating license.
See the 'Installing Floating Licenses' for a complete guide. If you are planning to render either via the Mocha render scripts, an Adobe watch folder or a render farm for example in Nuke , there are some file workflows you need to adopt. You will need to make sure the necessary source footage is available for all machines. This includes anything you have imported into the Mocha GUI such as clean plates, insert clips and other imported files.
You can unsubscribe from the Boris FX newsletter at any time by clicking a link we include in every message. We use a third-party service, Pardot, to deliver our newsletters, please see our privacy policy for more information.
Installing Node-Locked Licenses Node-locked Installation Make sure you have downloaded the correct version of Mocha for your operating system. You will need to install the Mocha package: Apple OS: Double-click the dmg package and drag the application to your application folder Windows: Double-click the exe package and follow the instructions Linux: Double-click the installation rpm file and follow the on screen instructions.
To activate:. Similarly, replacing a failed machine can be done without needing to contact technical support for the license to be released. Floating licenses are easy to set up if you are familiar with configuring network services, but if you need any help with the process, please contact technical support. Copy and paste your Silhouette Activation Key license that you received from your license email into the License activation key field.
Then, click Next. Your Ethernet address will auto-populate in the License Server or Node-lock hostid field. Accept the auto-populated Ethernet address. Enter the number of licenses that should be locked to this server in the License count for floating licenses field. Or just enter 0 to assign all licenses to the specified server. Click Next. A default license location will auto-populate in the License File to create or edit field. Accept the default license location and click Next. The license server should now be set up.
In cases where you cannot install the license via an Activation code normally where the server is not connected to the Internet you can manually install your license:. Install the License Manager on both the machine that has an Internet connection and the offline server you intend to run on. The Ethernet address of the machine you are on will auto-populate in the License Server or Node-lock hostid field.
You will need to overwrite it with the Ethernet address of the offline license server. To find the Ethernet address on the offline license server:. Replace the default location to a location that you can easily write to and access the file, such as your Desktop or the Downloads folder.
In the server license example above, you would enter camelot. The file name is not important, as long as the. See example below. It uses the usual RLM syntax, e. As with any software, problems may arise during the installation process.
Please take a moment to read our troubleshooting section and check for common errors. If you continue to have issues installing, please contact support and we will be happy to help you. If your organization needs to run a firewall, you will need to check if the ports for the RLM server are open for use. Check your purchase order to make sure everything matches up version wise. This is especially important for legacy software. If you have more than one Silhouette license installed on the server or client machine check to make sure they are not expired licenses.
While rare, sometimes these licenses can conflict with any current ones you have on your system. If your client machine does not connect to the server based on the server name, try replacing the server name with the IP address of the server instead in the license file.
You can easily do this via the License Manager or via a text editor. Check logs and their paths: Read the logs from Silhouette and from your server.
They will tell you all about what is happening to your machine. If your client machine is not able to connect to the server you may have a networking issue. You might roll your eyes at this one, but try uninstalling, restarting your machine, and installing the software again from scratch.
Make sure you follow installation directions off our website exactly. Contact us! Click "Next". Accept the default license location and click "Next". You will use the online machine to get the license for your offline server. Step 5 : Enter activation. Step 7 : Copy and paste your Sapphire Activation Key license that you received from your license email into the "License activation key" field.
You will need to overwrite it with the Ethernet address of the offline license server. The command will print out the results -- Get the first mac address from the first line: "Hostid of this machine:". Step 9 : Enter the number of licenses that should be locked to this server in the "License count for floating licenses " field.
0コメント