Ben McEwan:
As you have previously purchased a course of mine, I wanted to reach out and invite you to the pre-release of my new course, The Math of Comp. It's an information-dense short course, aimed at heightening your technical understanding of what the common tools in Nuke are doing to the pixels in your images.
You can donate, I recommend you do.
Great work.
This was my first shot on Mank. My first taste of monochrome compositing.
Conrad Olson
With some Covid-induced time off recently, I’ve made a concerted effort to try and learn Python. I’ve tried several times before and it has never really stuck, but I’ve always felt that I should be able to grasp it. So I was determined to use this time productively and crack it this time.
Its a good time to learn some new tricks.
Ben Mcewan:
Towards the end of 2016, I had a revelation; I made a conscious decision to seek out people I enjoyed working with in the past, and to do my best to continue working with those people. As it turns out, this was the single-most impactful career decision I’ve made!
You should have a look here
Mr. Lauridsen has been nice enough to share some scripts and python for nuke.
Mike Seymour:
Nuke started life at Digital Domain (DD) and then moved to The Foundry. The awards honor both the early work and the continuing R&D that has made this software the cornerstone of so many serious pipelines. Today, Foundry's Nuke has become a ubiquitous tool used across the motion picture and visual effects industries. It's nodal approach to compositing and effects has enabled novel and sophisticated workflows at an unprecedented scale and is used the world over.
While I have complaints about Nuke and The Foundry, Nuke is a amazing piece of software. If you can think it you can do it with enough time and money.
Mads writing over at hagbarth.net
One of the (many) things that can slow down Nuke scripts is a extensive use of Roto brushes. Nuke does not do any smart cleanup of brushes after you lay them out, and that sadly leads to a ton a redundant roto points, that does nothing but take up space and make your script slower to process and autosave.
I have always said that the RotoPaint node is very slow. I generally keep all RotoPaint nodes to 100 strokes or less. After 100 it really doesn't matter how much python you throw at it. Mads thanks for pointing out this script on GitHub it should be useful to some TD's that are building there own paint tools.
Just as a side note. Please, please don't hand animate your paint strokes. Use a tracker. Mads has some great tools for doing tracking for beauty work. Mocha and other Nuke tools will do a better job and it will be faster.