because it's looking at neighbour pixels with different values. and value above 1 are still different to 1. stop down the viewer to see the shades that are otherwise appearing as pure white
On Sep 9, 2011, at 11:03 AM, Nick Guth wrote: > Yep that was the culprit. I'm curious as to why the edge detect would still > detect those edges, even past a value of 1? Hrm, weird. Thanks! > _______________________________________________ > 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
