There are many things I love about it, especially when used in a teaching context. I am not near Nuke now, so this is from memory...
1: I love being able to adjust the same value by RGB, HSV, TMI and watching the values change live in each. Swopping easily between these values is great in practice and good to teach the difference between these values. 2: I love the fact that it has TMI included as a set. To be able to move the T slider and watch how the R and B sliders move in opposition to each other is a good way of showing how color correction works. Very useful indeed. 3: I love it's flexibility. How each component can be removed / cycled. Not love? I often have to rescue students from getting lost in some of its quirkiness. Again from memory. 1: Configurations do not seem to be consistently persistent. I feel I am always having to wrestle it into the form that I need every time I use it. 2: The slider sets sometimes appear very close together... Visually difficult to discern. The students read the complete set as a collection of ten, closely packed sliders. 3: The button to open / close the slider sets are not placed in a location that seems natural. 4: The color wheels seems over dependent on the size of the pallet. 5: Swatches are not persistent (or weren't last time I looked). Swatches aren't a big deal to compositors, but when you need them, you need them. 6: The wheels cycle but the sliders switch on and off. This mix of behavior is confusing to some students. One of my students mocked up a re think of the pallet. Will hunt for it next time I am in office. Sent from my iPad On 10 Apr, 2013, at 8:48 PM, Lewis Saunders <[email protected]> wrote: > Ean Carr wrote: >> ...and if you use a Card3D, make sure to crop it (and 'intersect') >> downstream or you're in for some show-stopping bbox issues sooner or >> later. > > +1, kinda wish the Write node had a crop option for EXRs. Even after > adding that to in-house stuff people still occasionally try to render > 50,000x50,000 bboxes which never ends well. > > I dunno about y'all, but I find that running ScanlineRender at higher > resolution and resizing back down runs many times faster than using > lots of samples. Motion blur implications aside. > > -- > Lewis Saunders > Chief Edge Detective > London > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
