On 1 sep 2011, at 22:12, Ned Wilson wrote:
I'm honestly not sure. The node was called CameraHold, and I know
it was written within the last couple of years ( after 2008 ).
Having this as a node is nice ut you basically need to do it as a C++
plugin, which in turn warrants maintenance on
Yup, already wrote some python that adds a tab to camera nodes with options
to freeze and choose frame. What I really want are all the time nodes to
accept 3D nodes as valid inputs.
On Fri, Sep 2, 2011 at 9:21 AM, Julik Tarkhanov ju...@hecticelectric.nlwrote:
On 1 sep 2011, at 22:12, Ned
I think it's time we revive this question, now that there's support for both
LogC and PLogLin (the Josh Pines formula) in Nuke 6.3.
I'm currently doing a film when we want to read plates in Log C using the Pines
math. The main reason for doing this in Nuke is that Arri's own Log C LUT (as
well
Good day all!
Before I start this topic (also my first), I wish to make it clear that I am
not ranting, or trolling, or moaning for the sake of it, I'm a brand-new user
to Nuke, and I just don't get it.
I'm looking to hopefully get into the FX industry one day, and have noted that
a lot of
The short of it is this:
AE is a prosumer tool, good for the infrequent user (consumer), and good for
pros. As a result AE has alot of quick solutions for basic fx work which Nuke
does not.
Nuke on the other hand is exclusively a professional Compositing tool, flexible
enough for the most
Some things that may help you understand Nuke:
1) Everything is a node. This is one of the fundamentals of node-based
compositing. There is no import video option or media library or insert
your favorite name for a central media location here. Image files are read in
and written out via the
The Switch From a layer based compositing App to a Node based on is going to
take some getting used to. The thinking is different. You have to start
thinking in Nodes not layers.
Here are some resources:
http://www.thefoundry.co.uk/training/display_training_articles.php
Hi,
Has anyone else experienced the auto-created expressions linking to the
wrong tracker (assuming multiple trackers in the script) when you use link
to with an individual point in the new grid warp in 6.3v2? I need to go in
there manually and correct them.
On a related note, it would be cool
