Yes, you need a model of an object or a scene to perform tracking.
No, it shouldn’t. But the better model you have the better results you obtain from every key frame.
The model should fit the scene. Minor details aren’t very important and could have negative impact on tracking performance
You may use 3D surface mask to exclude semi-transparent or reflective parts from tracking process.
If the overlapped area is relatively small GeoTracker will handle it. Otherwise you may use a 2D mask to exclude overlapping from tracking process.
GeoTracker’s output is the transformed input geometry.
No. As soon as you’ve done tracking you may export the results as a usual Nuke node (TransformGeo or Camera node) to pass them to other machines.
You can export the results as a TransformGeo or a Camera node on the Results tab.
You can export the results from the exported TransformGeo or Camera node as a .chan file.
There are a few videos demonstrating the basic tracking process and some major features. More detailed tutorials will be available later.
Yes, it's waiting for you in our Medium blog
Yes, you can build a model using a video instead of a sequence of photos. Actually, there is no difference between the two ways.
Using all the pins from all the keyframes FaceBuilder recalculates the resulting model's shape and model's position in each keyframe.
Unfortunately, no. All the photos should have the same resolution. But we might change it in future releases.
Unfortunately, it's not possible now.
No, it's not possible now, but we have it in our plans.
Yes, use Nuke internal WriteGeo node.
Currently it should be a model built by FaceBuilder node. The input can be connected directly to a FaceBuilder node, or to a ReadGeo node, if you have the FaceBuilder model built and saved to a file.
You can change anything but vertices count and order. You can manually move vertices if FaceBuilder's result doesn't suit you, remove or add faces, change normals and UVs.
Press ‘center geo’ button to position the object in front of the camera.
Click with right mouse button on a pin to remove it.
Nuke default camera is used in that case. The same as in ScanlineRender. Is has aperture of 1 and focal length of 1.
As the default camera with aperture of 1 is used when ‘cam’ input is not connected, small (< 1) focal length values are absolutely normal.
ReadRiggedGeo’s goal is to introduce deformable geometry to Nuke so that the geometry can be deformed and animated. ReadRiggedGeo doesn’t imply making a fully functional 3D Creation Software from Nuke.
Currently it is not possible to export rigged geometry otherwise than as a sequence of rigid geometries or as an FBX with animated points.
ReadRiggedGeo supports a lot of geometry formats. FBX and Collada formats may be used to load rigged geometry when many others may be loaded with ReadRiggedGeo when ReadGeo in not enough. For example: Autodesk (.fbx), Collada (.dae), Blender 3D (.blend), 3ds Max 3DS (.3ds), Wavefront Object (.obj), Stanford Polygon Library (.ply), and some others...
No. You can activate licenses manually from another computer with internet access using Manual Installation page. The Hardware ID can be found if you launch the License Server with the "run" command.
Host: services.keentools.io, port: 443. It happens when a license is being installed and when a running instance of License Server is checking installed licenses from time to time.
This may happen with licenses of a wrong type. Only floating licenses work with License Server.
Check there are no firewalls between the user's machine and the machine with the license server. The default port used by License Server is 7096.
Please, check there are no other processes using that port on the machine where License Server is being run.
You can redirect stdout to the License Server executable, i.e.
"cat licenses.txt | ./KeenToolsLicenseServer install"
"echo 'license1 license2 license3 ...' | ./KeenToolsLicenseServer install"
The licenses are being read during the startup, so you need to restart the existing License Server process to make newly installed licenses available for users.
There's no difference if you know how to use the OS of your choice as a server.
The simplest way to install KeenTools is to run the installer.
The installer copies KeenTools files to Nuke plugins directory:
• OSX: /Library/Application Support/NUKE/x.x/plugins/
• Linux: /usr/local/NUKE/x.x/plugins/
• Windows: C:\Program Files\Common Files\NUKE\x.x\plugins\
where x.x is Nuke version (10.5 for example).
You should check you’ve installed the correct KeenTools bundle (i. e. OS and Nuke versions match yours). If versions match and you can’t see KeenTools in Nuke try to perform manual installation.
Remove KeenTools folder from Nuke plugins directory to uninstall KeenTools.
No, Non-commercial version doesn’t support third-party plug-ins.
‘manual’ directory is only for performing manual installation. It isn’t required if you’re using the installer (i. e. you can only share the installer if it suits your needs).
• copy KeenTools folder from ‘manual’ directory to any place you want
• add the path to KeenTools folder to Nuke path by adding nuke.pluginAddPath('PATH_TO_KEENTOOLS') to init.py file.
• copy KeenTools folders from ‘manual’ directories for every Nuke version and operating system you want to any place you want;
• add the path to all that folders to Nuke path.
For example if you want to work with different versions of Nuke on Windows you may:
• unpack WIN_KEEN_TOOLS.zip to C:/KeenTools (could be any directory);
• write the next lines to %HOMEPATH%/.nuke/init.py:
KeenTools will automatically choose which installation should be loaded.
KeenTools won’t be loaded and an error message will be written to Nuke console.
Making changes in KeenTools installation may break it’s operability.
You can find menu.py file in KeenTools directory and edit it as you see fit.
Currently there are three non-free nodes in KeenTools: GeoTracker, FaceTracker and FaceBuilder. FaceTracker license allows using Facebuilder as well. You can use personal, commercial or floating license for it. Each license is valid for one year from the date of its installation.
Personal license can only be purchased by an individual and used by a single person.
Yes, you can use your personal license for commercial work.
No. Non-Commercial Nuke doesn't support any plugins.
No, personal license allows you to use the full set of node features.
No, a personal license can only be purchased by an individual.
No, and our EULAs explicitly prohibit the reimbursement of personal licenses by companies.
Yes, you are free to use your personal license for any purpose.
No, you can’t use the same license simultaneously on multiple machines. But you may transfer the license from one machine to another on several occasions.
Concurrent usage is not allowed by commercial licenses. This mean that two users cannot use one license at the same time.
However, it is possible for two users to share a license if they do not work simultaneously. In case two or more users work simultaneously each active user must have their own license.
Each active user must have their own license. In other words, if all 10 compositors need to run our software at the same time, you need 10 commercial licenses. See the question above for additional clarification.
If you're a representative of a school, please drop us a message at firstname.lastname@example.org to get free licenses for educational purposes or a discount. If you're a student, please ask a representative of your school to contact us.
You may pay using PayPal or a card.
We deliver licenses by email.
Your license will be delivered in a few minutes.
If you didn’t receive the purchased license in a few hours after the purchase, write us an email.
License key allows to install license on a node. License file describes a license locked to a node.
No. At the moment we only have one year licenses.
To use floating license you should install license server, install floating license on it and connect to the server from the node.
License server download contains step by step guide on how to use floating licenses.
No, you can generate a license file on a machine connected to the Internet and install the license file on the target machine. Use a hardware ID from the target machine to generate the license file.
You only need one license to use one node type (e.g. GeoTracker) from any KeenTools installation on a single machine.