↳

1. B PIPE Keep every layer operation piping in to the B pipe stream (your main branch) - this means, among other benefits, you can dissable the merge and the image stream will still flow. In terms of include/exclude mask ops like the popular in Shake 'inside' and 'outside' - you will have to get used to using 'mask' and 'stencil'. 2. BBOX Make sure you are optimising your bounding box on any element you have in the comp. If the image is full frame, take care it doesn't grow larger (from blurs, transforms etc) than the full format, and if it smaller than full frame make sure you have a bounding box that sits tightly around the element. When merging it is important to chose the 'set bbox to' option that is the most optimised for what you are trying to achieve, with the goal of the smallest bbox possible as paramount. If it is a CG pass, your 3D department should be rendering exr's with bounding boxes built in, but if not then you can create them yourself. AutoCrop can analayse zero data pixels in a frame and drawn a bounding box around the element. You will then need to take this AutoCrop data and copy that data into a crop node to make use of this data. When rendering out and exr file sequence, of say a precomp of an element, you can check the autocrop option on the write node. Bear in mind that his option only appears when you are rendeirng out exrs. This is quite a slow process as it consumes quite a bit of memory, but the beauty is that if you do it once, you won't need to do it again and when you bring in the sequence as a read node you will now have the bounding box baked in. 3. CONCATENATING TRANSFORMS Geometric transforms should concatenate to retain the integrity of your plates and elements. Why? Ultimately whenever you filter pixels (transforms, convolves / blurs etc) You are approximating new pixels with filter algorithms that are essentially a visual cheat, and a cheat that degrades the image integrity - albiet normally ever so slightly but if these degradations pile up on top of each other you start to see unwanted artifacts in your plates / elements. Concatenate means that the mathmatics behind multiple transform nodes can be 'folded' into one operation. It is useful to have multiple transform nodes to have the upmost control of transform operations, and the 3d environment in Nuke will concatenate with 2d transforms. Say you wanted move an element around but have independent control on movement in X/Y, scale and rotate. By splitting these operations into three transform nodes you can have total control on adjusting, removing or just quickly disabling these now independent transforms. If Nuke didn't concatenate the three transforms, you would be degrading the image every transform. Luckily it does, but only if you follow the golden rule: keep transforms one after each other and don't 'break' them by placing color correction nodes or merges between them! In Shake, there was a handy green line that would appear connecting transform nodes to give you visual feedback that your transforms were concatenation, alas Nuke doesn't do this (yet? hopefully!). 4. CARD3D Use Card3D's when you can instead of cards in a 3D setup with a scanline renderer. Much, much faster to render and you are essentially doing the same thing if you just have a single card. 5. BLUR INSTEAD OF DEFOCUS Although Nuke's Defocus node is pretty fast, a blur beats it for speed. And you should only need to use the defocus node when you want optical 'bokeh' effects (the blooming of highlights when defocused. Don't use defocus nodes on mattes, or to just soften images when you aren't after the said optical effect. 6. EXPOSURE = MULT This isn't really an optimisation but remember that the exposure node is only a RGB multiply grade operation like the mult in a grade node, only difference is that the parameters are to an exposure scale. Handy if you are used to working in stops or printer lights, or if you have been instructed by your superviso Less

↳

I showed the shader and explained

↳

Yes, No problem at all.

↳

Play and know lol mechanics seriously.

↳

Just telling the truth, the programs I know, the experience, and deep thirst for learning. Less

↳

I answered with my own personal opinion regarding two separate FX, explained why I thought it could use improvement. Apparently, the main guy who was interviewing me made that particular FX and didn't seem to like my feedback. Less

↳

as they promised Ramp up and there was none only crunch

↳

They were very relevant and felt to me like the people interviewing me knew about the specificity and goals of my position, which I appreciated a lot. Less

↳

As a junior, there is no baseline, so I bid the bare minimum to survive.