QuickKey v2.2


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Cameron Carson
QuickKey is a HSV Keyer with a Color Picker and fine tuning controls similar to Resolve's.
Requirements:
11.0, 10.5, 10.0, 9.0, 8.0, 7.1, 7.0, 6.3 or later
Linux, Mac, Windows
08 Dec 2017
785

QuickKey is a HSV Keyer with a color picker and Fine tuning controls similar to the way Resolve's keyer works. It is designed for quickly grabbing keys without get all fancy. I use it primarily for color correcting Works great for Poorly generated Color Mattes or even just color correcting and area with a soft key. Anything where you need a quick key and don’t want to take the time to monkey with multiple nodes.

 

QuickKeyClosed

QuickKeySelection

Please login in order to download these files.

Comments   

 
0 # Lucas Pfaff 2015-04-02 14:40
This tool is awesome, thank you!
I thought of building something similar myself but had issues finding a start, and now I don't have to :)
 
 
0 # Cameron Carson 2015-04-22 23:12
Happy to help!
Thanks for the feedback.
 
 
0 # Evgeny Shpilivoi 2015-05-19 02:57
Tool is awesome!, but I have Error on reload or open scene, and data gizmo lost... tired to make it works...
 
 
0 # Cameron Carson 2015-05-19 03:27
Hi,

This is a Gizmo, not a Group node. It needs to be installed via the menu.py or init.py similar to any gizmo.

Typically that is done something like this...

nuke.menu( 'Nodes' ).addCommand( 'Other/QuickKey ', lambda: nuke.createNode ( 'C:/NukeStuff/G izmos/QuickKey' ) )

If you try and copy it to a group or change the gizmo to a group in the plaintext it will break.

Hopefully that solves it for you.
 
 
0 # Evgeny Shpilivoi 2015-05-19 04:22
Thank You! You are the best!
cheers :roll:
 
 
0 # Evgeny Shpilivoi 2015-10-07 01:14
Hey again, I got some issue with that tool, so I am have scene many keyers, and QuickKey v1.0, so when I render out image, its random make artefacts almost in each frame, does have any suggestions.. thanks
:roll:

Evgeny

Cheers
 
 
0 # Alexis Oblet 2017-12-06 15:17
It seems there is a bug.

In the knobChanged, range builtin function is erased by a float.
The scope is global so for example other nodes using knobChanged and using range function will raise error like Tracker node.
 
 
0 # Cameron Carson 2017-12-08 00:21
Thanks for mentioning this.
I cant see anywhere where I am erasing the default range function in the knobChanged but I am running on any knobs named "range" . It shouldn't cause any errors but is a few lines of inefficiency so I am fixing that by renaming the knob to "qRange" which should avoid most conflicts.
 
 
0 # Alexis Oblet 2017-12-11 17:05
In the version 2.0 there was:
range = (n['range'].value()*n['range'].value())/2

But now (version 2.2) it's replaced by cRange, so everything is good :)

Thanks.
 

You have no rights to post comments

We have 3255 guests and 91 members online