In December I used my spare time to learn Pyside2 in order to be able to do GUI with Python3. ‘What better way to learn than actually coding?’ I thought, so I created a little tool to manage the assets of my personal projects.
The software allows taking control of the assets you create and have in your project. It creates a general database for all the assets, where it stores the asset name, type, and last modified date. It also creates an additional database for each asset to store more specific information about the ‘asset files’ (the software files used to develop and create the asset). In addition, to be able to store notes about each asset file, it also allows the user to open the asset file by double-clicking in the table.
The naming convention and folder structure that I have chosen is the one that I use in my personal projects. It’s far from being perfect but I think that it’s quite clear and easy to follow.
As for the interaction with the different software, right now the user has to version up the files on its own following the naming convention and the version number. After that, clicking ‘Update’ in the Asset Browser will allow the user to add those asset files to the asset’s database with some notes (if wanted).
Here you have a (boring) video where I show how it works:
due to some Twitter conversation with Guillermo García, I decided to create a tool that allows storing a node selection to go back to it whenever necessary. It creates a tag inside the selected nodes and creates a menu where the different selections are stored with the name that you have given to them. Sadly, the menu is erased each time you close Nuke, but there is a workaround. You can give the same names that you had before to empty selections, as the tags inside the nodes haven’t been erased, it will restore those selections.
a month ago I developed a gizmo to allow me creating mattes from ID passes quickly and easily when there is no Cryptomatte in the studio’s pipeline. It’s a dynamic gizmo that allows adding as many ID passes as you need and selecting which channels will be part of the alpha. You can download the code from my Github site.
I have also recorded a video showing how this gizmo works. As always, feedback will be welcome and appreciated 🙂
this is the first of a series of gizmos that I’m developing right now. This one is an enhanced Keyer gizmo that apart from having the usual Nuke’s keyer operations and options, it has some more keying operations and options that can help in keying process. In the following lines, I will explain in more detail these improvements and I will finish this post by sharing the code of the gizmo. However, if you prefer, you could download it from Nukepedia and start trying it. Please, I will really appreciate your feedback. Continue reading “XA Gizmos: Keyer”→
Sometimes there are critical changes in production. The resolution of the plate may change (it’s not a common thing, but it may happen). Lest say that we have been working doing some roto and cleanup for a 2K DCP plate and the, they give us a 4K DCP plate. The aim of this script is to modify the roto/rotopaint nodes to adapt them to the new resolution, without having to redo all the work.