Screen is also a multiplicative operation, it's just inverted images
multiplied together and re-inverted.
On Wed, Jan 28, 2015 at 8:35 AM, Ron Ganbar ron...@gmail.com wrote:
The math used in Nuke for Screen makes it inheritingly clamp (it doesn't
really clamp, but can not produce colors
The math used in Nuke for Screen makes it inheritingly clamp (it doesn't
really clamp, but can not produce colors brighter than 1).
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/
On Wed, Jan 28, 2015 at
But i guess that leads back to the original question.
I can't find a single reason (artistically or technically) why they changed
this to clamp between 0-1.
On Wed, Jan 28, 2015 at 6:03 PM, Ivan Busquets ivanbusqu...@gmail.com
wrote:
For more crude / unclamped versions of some merging
Ohh, interesting.
Thanks a lot!
Sendt fra min iPhone
Den 28/01/2015 kl. 18.03 skrev Ivan Busquets ivanbusqu...@gmail.com:
For more crude / unclamped versions of some merging operations (including
overlay), you can also use the olde Merge node (as opposed to the default
Merge2.
Merge {
Maybe there should be a clamp option in 'merge3'. I think divide has similar
issues. That would allow for backward compatibility to 'merge2'.
Clamping for matte purposes is valid isn't it?
Howard
On 28 Jan 2015, at 7:53 pm, Deke Kincaid d...@thefoundry.co.uk wrote:
Mads:
When you say
I've been seeing this too on OS X at a place I'm working right now.
Thought it was something internal. It's driving me crazy.
On Wed, Jan 28, 2015 at 7:15 PM, adam jones adam@mac.com wrote:
Hi guys
I apologies if this has been posted prior I have just not come across it
on the forum.
Havent seen this issue on Windows
On Wed, Jan 28, 2015 at 4:25 PM, John Mangia j...@johnmangia.com wrote:
I've been seeing this too on OS X at a place I'm working right now.
Thought it was something internal. It's driving me crazy.
On Wed, Jan 28, 2015 at 7:15 PM, adam jones
Is it reading the deep data though, or just the non-deep channels? That
fooled us in nuke 8 ('hey look! regular reads can load mantra deep exrs! oh
wait, where's all my deep data gone?').
On 29 January 2015 at 10:16, Michael Hodges mhod...@morganfalls.com wrote:
If I’m not mistaken it looks
Hi guys
I apologies if this has been posted prior I have just not come across it on the
forum.
I am using nuke 9.0v3 in a studio and seems that the undo and redo feature is
not working in the release or is it something that in the studios pipeline
might have broken this.
There is no undo at
ah we are on windows and have it also
On Jan 29, 2015, at 11:44 AM, Brent Veal naslund.fan...@gmail.com wrote:
Havent seen this issue on Windows
On Wed, Jan 28, 2015 at 4:25 PM, John Mangia j...@johnmangia.com wrote:
I've been seeing this too on OS X at a place I'm working right now.
Looks like the nuke screen algorithm has a low pass to allow for values
over 1 to comp more naturally. You can see the difference if you expose
down.
On Wed, Jan 28, 2015 at 10:37 AM, Mads Lund madshl...@gmail.com wrote:
Ahh ok, so the Screen operation in the merge node does not just screen.
Ahh ok, so the Screen operation in the merge node does not just screen.
Screen is the same as the Merge
http://help.thefoundry.co.uk/nuke/9.0/content/reference_guide/merge_nodes/merge.html
node,
only with operation set to screen by default. It layers images together
using the screen compositing
If I’m not mistaken it looks like Nuke 9 seems to read my Arnold Deep EXRs with
both “Read” and Deep Read” nodes. Is this a new functionality?
Dan Michael Hodges
Atlanta
___
Nuke-users mailing list
Nuke-users@support.thefoundry.co.uk,
I wondered how the screen would need to be calculated differently since the
invert function might get you some crazy values in float space.
It makes sense that they changed it to give us a visually accurate result
when a mathematical one would look like an error.
On Wed, Jan 28, 2015 at 10:49 AM,
It's just bad with the overlay thing, as it is a pretty useful way to add grain
and do dodge/burn effects. It works out of the box in Photoshop, Fusion and
AfterEffects but you have to make your own overlay gizmo to make it work in
Nuke.
Den 28/01/2015 kl. 17.11 skrev Daniel Short
Build your own Overlay?...
You know the math...
Ron Ganbar
email: ron...@gmail.com
tel: +44 (0)7968 007 309 [UK]
+972 (0)54 255 9765 [Israel]
url: http://ronganbar.wordpress.com/
On Wed, Jan 28, 2015 at 6:34 PM, Mads Hagbarth Lund madshl...@gmail.com
wrote:
It's just bad with the
Hi guys,
I am trying to solve cameras of still images along with LIDAR data
acquired. Ideally I would like to solve each still camera positions and
lock in with the LIDAR data in terms of scale and accuracy, and then
triangulate the positions of multiple HDR panos.
I first created 6+ user tracks
Mads:
When you say we changed it, did we at one time have a merge2 node that did
not clamp and we changed the formula on the Merge2 node to then clamp?
I suspect this predates The Foundry's involvement in Nuke (Merge2 node was
introduced before 2007) and anyone who did make the modification has
18 matches
Mail list logo
