Stamps v1.1
This location is for Registered Users Only.
Perhaps you need to login or register.
13.1, 12.2, 12.1, 12.0, 11.3, 11.2, 11.1, 11.0, 10 or later
Linux, Mac, Windows
* Now compatible with Nuke 13
Stamps is a production-ready node connection system for Nuke, that enables placing the main assets in a single place on the Node Graph, through distinct nodes with hidden inputs that reconnect themselves when needed. |
Auto-Reconnection
Auto-Reconnection avoids having to think about copying and pasting nodes (or even node trees) and maintaining their connections, even between different nuke scripts. You can also feel confident that you can always find where the stamp needs to be connected to thanks to the Advanced Reconnect functionality.
Single contextual hotkey
Using Stamps for the artist is as easy as remembering a single hotkey.
The hotkey is context-dependent, so it performs many different actions based on what’s selected.
Production-ready
Stamps has been thoroughly used in production and is currently used in studios of all sizes, and its development has been shaped by the feedback from compositors with different workflows and backgrounds. Trixter was the first studio to implement Stamps studio-wide in the compositing pipeline.
Quick selection functionality
The tag system allows for organising the stamps into categories for super quick access to every Stamp from any part of the node graph. The Anchor Selection Panel will let you quickly search for the Stamp you want, sorting based on different filters like their tags, the labels of the backdrops where they live, or their popularity (how many times you've used them).
More...
The user guide and tutorial videos are an in-depth look into all the features and workflows of Stamps, the benefits of using it, why we believe it gives a solution to the common problems of working with hidden inputs and why it is now a core part of out compositing workflow. They also show how to set up smart templates, the extra stuff included with stamps like W_Hotbox buttons, as well as all the customisation options for each specific pipeline's requirements.
Latest pre-release fixes will be here: https://github.com/adrianpueyo/Stamps
Update Log:
Stamps v1.1.0 - 18 May 2021
New features:
- Postage Stamp thumbnail option for the node graph on “Type 2D” Stamps.
- Anchor Stamp Selector: multi-select by right clicking the OK buttons before a left click.
Bug fixes and enhancements:
- Compatible with Nuke 13 / Python 3.
- Anchor Stamp Selector: “Popular” dropdown behaviour fixed.
- DummyCam updated to v1.2
- Import method improved for user friendliness.
Comments
Hope that all companies will introduce it in their workflow
Excellent work!
Do you think, in a future version, we could get a postage stamps when we stamps a read node?
I was wondering what if I got this installed but one of my colleagues open my script and he hasn't the tool yet?
I fixed it for working on Nuke 13
DOWNLOAD BELLOW.
I fixed it for working on Nuke 13
DOWNLOAD BELLOW.
VIDEO DEMO: https://vimeo.com/547186457
DOWNLOAD HERE: https://bit.ly/3vZ9tv3
**Remember:
1. Modification has not been consulted by the author. This is an unofficial version from the artist.
2. This script has been modded for my personally.
I just published the v1.1.0 release.Do not hesitate to fork it as needed
https://github.com/adrianpueyo/Stamps/releases/tag/v1.1.0
I love it. I will try it and I will remove my link.
The line that hides the stamps when out of the GUI seems to be the problem:
if nuke.GUI:\n try:\n .......etc deadline things is a path and change them to " if nuke.GUI:/n try:/n i guess.
NameError: name 'stamps' is not defined
We are using Deadline v10.1, Stamps v1.1, Nuke v13.1
This happens whenever an artist updates the source that is connected to an anchor, allegedly, then when they submit to deadline, it errors-- but with a resubmit, it goes through without the Name Error.
Weird? Maybe there is a way to 'refresh' the stamp when that happens? I would love to know if anyone has any input on that.
thanks for this awesome Toolkit. I already worked with it in several pipelines and it is such a great way to deal with your connections!
There is one small issue that happened, when I shared a script with an artist, who didn't have the whole toolkit installed: The moment you try to change the slightest thing in the anchor or wire, Nuke is giving out a lot of Python errors, which lead to a few seconds of freeze sometimes.
I guess it is connected to the "knobChanged"-k nob, which tries to run the command "import stamps; stamps.wiredKno bChanged()" - and this fails. And this knob activates multiple times during a position change. Is there a way to limit this check?
All the best!
one more thing that happened to one of our artists:
You are able to copy a stamp into a group and this even works for the moment (no idea, how this gets connected). But it breaks the script when you save and reload it. Nodes then get pushed around and into the group. I know that this is really forced, but it can happen that you create a group with some nodes and a stamp is in there. Perhaps there is a way to avoid this by checking if stamp and anchor are on the same "level".
Can you add function for cg passes where instead of postage stamp I can get a shuffle node
Can you add function for cg passes where instead of postage stamp I can get a shuffle node
I can't use the postage stamp show when i add a new nodetype on my workflow.
Can you replace it?
Thanks!I very love it.
I installed it in my Nuke 14.0 v14 and I couldn't get it to work, every time that I press F8 or select the "stamps" throught tab commant I get this message from Nuke.
'NoneType' object is not subscriptable.
Do you know how can I fix that? I'm really excited to use Stamps but actually I can't. : (
Thank you!
So I guess it's maybe a nuke indie limitation, because even if I'm having the nuke indie I get this non-commercial error" The Non-Commercial mode 10-node limit for Node objects accessible in Python has been reached" and after that I get " File "", line 1, in
File "C:/Users/mynam e/.nuke/stamps\ stamps.py", line 2370, in goStamp
extra_tags = stampCreateAnch or(n, extra_tags = extra_tags) # Create anchor via anchor creation panel
File "C:/Users/mynam e/.nuke/stamps\ stamps.py", line 1748, in stampCreateAnch or
na = anchor(title = anchor_title, tags = anchor_tags, input_node = node, node_type = node_type)
File "C:/Users/mynam e/.nuke/stamps\ stamps.py", line 687, in anchor
n["name"].setValue(name)
TypeError: 'NoneType' object is not subscriptable".
I guess those are created due to that limitation
But yes you are correct, from nuke site:
Limited Python API Support
Calling greater than 10 nodes is not supported, limiting the ability for automation within scripts. Automating the creation and processing of Nuke scripts is not supported. Python tools freely available on sites such as Nukepedia may or may not work depending on complexity.
RSS feed for comments to this post