☢️ Available on Nukepedia I made a small gizmo to transform the input image with two points that “look at” each other. This makes it much easier to attach stuff that has two anchor points or rotate and scale something around a fixed point. I got the idea when I was trying to rotate stock footage of a flare around the center of the screen. But why not use it for lightsabers? Or laser beams? ...
I made a stupid thing. But it was fun and I learned some stuff about QPropertyAnimations along the way. Here’s the code import sys from random import randint try: from PySide import QtCore, QtGui, QtGui as QtWidgets except: from PySide2 import QtCore, QtGui, QtWidgets class DodgeButton(QtWidgets.QPushButton): def __init__(self, parent=None): super(DodgeButton, self).__init__(parent=parent) # PROPERTIES self.origSize = [self.size().width(), self.size().height()] self.aniSpeed = 120 self.aniPosition = QtCore.QPropertyAnimation(self, b"pos") self.aniPosition.setDuration(self.aniSpeed) self.aniScale = QtCore.QPropertyAnimation(self, b"size") self.aniScale.setDuration(self.aniSpeed) # EVENTS self.clicked.connect(self.win) # INIT xPos = parent.width()/2-self.width()/2 yPos = parent.height()/2-self.height()/2 self.move(xPos, yPos) def win(self): print("ALRIGHTY!") def enterEvent(self, event): self.randomScale() self.randomMove() def randomMove(self): """ move to a random position """ randX = randint(0+self.width(), self.parent().width()-self.width()) randY = randint(0+self.height(), self.parent().height()-self.height()) # Move self.aniPosition.setStartValue(self.pos()) self.aniPosition.setEndValue(QtCore.QPoint(randX, randY)) self.aniPosition.start() def randomScale(self): """ scale to random size """ randMult = float(randint(50,200))/100.0 # Scale self.aniScale.setStartValue(self.size()) newSize = scalePropo([self.origSize[0], self.origSize[1]], self.origSize[0]*randMult) sizeX = newSize[0] sizeY = newSize[1] self.aniScale.setEndValue(QtCore.QSize(sizeX, sizeY)) self.aniScale.start() class MainWindow(QtWidgets.QDialog): def __init__(self, buttonName="Analyze", parent=None): super(MainWindow, self).__init__(parent) layout = QtWidgets.QVBoxLayout() self.setLayout(layout) self.setFixedSize(500, 500) # INIT self.button = DodgeButton(self) self.button.setText(buttonName) def scalePropo(oldSize=None,newWidth=None): ''' Scales an input size proportionally to the new desired width. :param oldsize : : The current size [x,y] :param newsize : : The new desired width ''' oldWidth = float(oldSize[0]) oldHeight = float(oldSize[1]) newHeight = (oldHeight/oldWidth)*float(newWidth) newSize = [newWidth,newHeight] return newSize def setup(): app = QtWidgets.QApplication(sys.argv) win1 = MainWindow("Analyze") win2 = MainWindow("Are you sure?") win3 = MainWindow("Are you really sure?") win1.button.clicked.connect(win2.exec_) win2.button.clicked.connect(win3.exec_) win1.exec_() # app.exec_() sys.exit(0) if __name__ == '__main__': setup()
🦑 Download it here Edit 2 July 10, 2021 It’s been a while but I’ve just stumbled upon this little video that actually explains a very simple way to just expression link layers together to copy their style. Haven’t tried it so I’m not sure how many styles are actually supported but thought I’d link it here because it’s relevant to the topic: https://youtu.be/5hTVqDleABU Edit 1 Sooo, this turned into a larger R&D session about text layers than I had expected. It seems that the JavaScript API’s access to text layer’s properties has some limitations as well. I spent some time reading the docs once more and testing every property and made a simple overview of what won’t sync so You won’t get unpleasantly surprised: ...
🦑 Get it on GitHub | 🏷️ latest I got tired of digging through piles of print statements to find a bug or formatting messages to the console so they are semi-readable. The python logging module fixed part of the problem, but quickly I also got tired of setting up handlers, formatters and didn’t want 20 lines of code at the top of every script just to be able to log. So I created neatlog - a small Python module to create readable logs, print them to the console in colors and even save them to a file ...
Introduction In the course of the last year I’ve been a part of producing Visual Effects for two feature-length films with each around 100-200 VFX shots as a visual effects artist, supervisor and pipeline TD. To begin with we only had a small amount of ‘automated’ pipeline stuff, so almost everything was written from scratch. To make everyone’s day, including my own, way more fun and productive I set out to write a bunch of scripts and tools to make the repetitive and annoying tasks disappear beneath user interfaces. The following is a presentation of the tools I’ve developed and some background info and about how they work and were made. ...
🐙 Get the script on GitHub The past weeks I’ve been working on a python script to make working with ‘special comps’ generated by Nuke Studio less of a pain. When I set up comps for a project, I usually import an EDL from edit into Nuke Studio, relink the clips, rename them and then generate comps with ‘Create Special Comp’. That way I’m sure that the plates in the comp are aligned correctly in time and that the write node’s path is set correctly. This saves a huge amount of time for the artists that are going to work on the show. ...
Sometimes when Nuke’s caching gets super slow it might be caused by a sneaky Viewer node hiding somewhere inside a Group, slowing everything down. This script quickly gets rid of them and only leaves those in the “main” Node Graph. Get it from my 🦑 GitHub
🖥️ Software used: Photoshop, Illustrator, After Effects, Cinema4D Breakdown of the intro and other elements
I’ve been playing around with expressions lately and am working on a semi-useless-but-fun group to map a sinus ripple onto a point position pass (although any world position data will do) and displace it with some noise. Here’s a preview made with some basic nuke geo and turning ALL the knobs on the group: