[Nuke-users] Adding layer anything.height makes nuke expression "height" always return 0

2017-05-22 Thread Mario Maruska
Hey guys, Adding a layer in your script called anything.height makes the native nuke "height" command always return 0. If you've got any expressions/gizmos/groups using the image/format height this will obviously render them useless. Removing every instance of anything.height or even the entire

Re: [Nuke-users] Selective colour in nuke

2017-04-11 Thread Mario Maruska
Gives me a "vibrancy" error, gizmo/plugin within gizmo ? On Tue, Apr 11, 2017 at 3:43 PM motion artist wrote: > Forgot to include the selective colour settings in PS. > > Let me know what you guys think > > > All the best > > Stepan > > On Tue, Apr 11, 2017 at 2:41 PM,

Re: [Nuke-users] invert Hue

2016-10-07 Thread Mario Maruska
There's also the hueshift node which allows you to rotate the hue by any amount desired. On Fri, Oct 7, 2016 at 3:17 AM Gary Jaeger wrote: > Boom! that’s it. Thanks Nathan! > > *Gary Jaeger */ 650.728.7957 direct / 415.518.1419 mobile > http://corestudio.com > > On Oct 6,

[Nuke-users] Rotopaint column width

2015-11-25 Thread Mario Maruska
Hi, Is there any way of changing the width of the columns in the paintstroke/spline list in the roto/rotopaint nodes ? Got a show with lots of cleanup and not being able to see lifetime ranges for paintstrokes is infuriating. E.g. 1001-1058 turns into "100..." Cheers, Mario

Re: [Nuke-users] motion blur error / globally offsetting curve lifetime frames

2014-05-04 Thread Mario Maruska
, 2014-05-02 at 4:26a, Mario Maruska wrote: Hi all, I've got some scenes with frame ranges starting at over 1 000 000 (non normalised conform...) and the roto rotopaint nodes don't do motion blur sampling properly at such high frame numbers. Is there a way to globally offset the curves

[Nuke-users] motion blur error / globally offsetting curve lifetime frames

2014-05-02 Thread Mario Maruska
Hi all, I've got some scenes with frame ranges starting at over 1 000 000 (non normalised conform...) and the roto rotopaint nodes don't do motion blur sampling properly at such high frame numbers. Is there a way to globally offset the curves' lifetime start/end ? Those parameters don't seem to