![]() To add our Alexa LUT to Nuke Studio, we need to create our own custom OCIOConfig. Just like everything in Nuke Studio, am I right? For you, this process is going to be a little more work. That means setting the "colorspace" on our Write node to "AlexaV3LogC", regardless of the file format. Set your "in" to "linear" and your "out" to "AlexaV3LogC"Īnd, just so we're clear, if we're working on an Alexa colorspace clip, as a Good VFX Artist, we're going to send back a render that is also in Alexa colorspace.After the OCIOFileTransform node, add an OCIOColorSpace node.Leave the "direction" on "forward" and "interpolation" on "linear". Set your "working space" to "AlexaV3LogC".Create a OCIOFileTransform node and add the downloaded LUT file.To get started, create a new Nuke project. If, however, you also use Nuke Studio or Hiero, you'll want to ignore this section and skip ahead to the OCIOConfig version. If you only use Nuke/NukeX, adding the Input Process is relatively simple, and bares a striking resemblance to a lot of the Defaults customization we've done in the past. You can download it here, or build your own with Arri's online LUT generator. No, this is not the same LUT that comes with the application. ![]() The first thing we're going to need is the Alexa Viewer LUT. But we don't want to bake that Rec709 conversion into our render, we just want to view it in the corrected colorspace. We could toss a OCIOColorSpace node at the end of our script and work in between it and our Read. There is no built-in Viewer Input Process to properly view Alexa footage. In DaVinci Resolve, these 2 steps are performed at the same time. The footage gets its gamma linearized in the Read node before work is done, then, after our work has been added, the footage needs to be converted to Rec709 colorspace. The Alexa's LogC footage needs to be gamma corrected and tone-mapped to a Rec709 colorspace. Head over to the Downloads page to get the full updated Node Sets v1.2 code. It's rare that the solution to an issue I encounter while working is so simple to create that it's quicker to just make the tool than capture a note to create it later, but that was the case with this one and I'm very happy to have this new option. NumPan = nuke.toNode('preferences')Īnd the additional line to add the tool to the menu is: nsets.addCommand('Node Set: Show Selection', 'showOnlySelectedNodes()', icon='NodeSetsMenu-show.png') The full function, called showOnlySelectedNodes(), looks like this: def showOnlySelectedNodes(): Writing this blog post has already taken several orders of magnitude longer than writing the code. In the function's for loop, I changed nuke.allNodes() to lectedNodes(). Specifically, I duplicated and renamed the "Node Set: Show Nodes" code, and changed one word. Like I mentioned at the top of this post, the code for this new addition was exceptionally simple. So, when working on a smaller section of the animation, I can select a block of nodes and run the new command "Node Set: Show Selection" to open the tagged nodes contained within. A terrible workflow.Ī solution that solves this problem in a much simpler, smarter way is to use a selection of nodes to narrow the search for tags. A fine idea that I never personally implemented because the tags are hard coded into the tool and there's no way to add more tags without closing the app, modifying the menu.py file, and cluttering up the toolset with a lot of similarly named tools. Each of these blocks would have its own set of animated nodes, building a piece of the overall animation.īut the comp I was working on yesterday had 140 tagged animated nodes and, while it would technically still work to open all of them every time I need to make a timing change, it's slow and unwieldy to have 140 node property panes open at the same time.Ī solution I proposed to this issue in the v1.0 blog post was the ability to use a different tag for different types or groups of nodes and open them each independently. One of the main benefits of a node-based workflow is the ability to create any number of blocks of operations, separate from the main process tree, then connect and combine them as necessary. The problem I encountered involves this methodology's inability to scale with the modularity of larger projects. The idea being, you'll need to open not only the nodes that need to be adjusted, but also all of the other relevant animated nodes for timing and context. The original intended use for the Node Sets tagging tools was that animated nodes would be tagged as you work and, when you need to adjust an animation's timing, you would run the "Show Nodes" command to open all of the tagged nodes. A rare combination when it comes to my code. ![]() Yesterday, while trying to address a note on a near-finished animation, I discovered the need for a new tool in my Node Sets toolbox that was both useful and trivially simple to create.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |