<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><base href="x-msg://15/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I must say that I never thought about it this way, but really… just having separate "clamping" node with options of "clamping whites" and "clamping blacks": would solve most of the issues… No matter what my guru:Troy says… :-)<div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Bartek Skorupa</div><div><br></div><div><a href="http://www.bartekskorupa.com">www.bartekskorupa.com</a></div></div></span></span></span>
</div>
<br><div><div>On 23 maj 2014, at 18:12, Sean Kennedy <<a href="mailto:mack_dadd2@hotmail.com">mack_dadd2@hotmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="hmmessage" style="font-size: 12pt; font-family: Calibri; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div dir="ltr">While I understand that internally, all numbers are valid, I agree with Bartek. In everyday film compositing, clamping is necessary. I use it all the time on the math and mix nodes, and even though I know it's not there, I still ALWAYS looks for it on the curves node.<div><br></div><div>I would even go so far as to suggest a clamp node. We have the map value node, and in some instances, that does the job, but not all. I love the idea of a clamp node with individual "clamp white" and "clamp black" check boxes. </div><div><br></div><div> At R&H, every single compositing setup on every single movie we did had, at the very end of the default compositing template, a clamp node. It made sure that no matter what a compositor did, the blacks wouldn't go too dark and the brights would never get superbright.</div><div><br></div><div>sean</div><div><br><div><hr id="stopSpelling">Date: Fri, 23 May 2014 06:09:54 -0700<br>From:<span class="Apple-converted-space"> </span><a href="mailto:troy.sobotka@gmail.com">troy.sobotka@gmail.com</a><br>To:<span class="Apple-converted-space"> </span><a href="mailto:bf-compositor@blender.org">bf-compositor@blender.org</a><br>Subject: Re: [Bf-compositor] Clamping (Mix, Math, RGB Curves)<br><br><div style="margin: 0px; padding: 0px; "><br>On May 23, 2014 4:46 AM, "Bartek Skorupa (priv)" <<a href="mailto:bartekskorupa@bartekskorupa.com">bartekskorupa@bartekskorupa.com</a>> wrote:</div><div style="margin: 0px; padding: 0px; ">> In many cases when using nodes we'd like to clamp output values to visual range (or to range between 0.0 and 1.0).</div><div style="margin: 0px; padding: 0px; ">There is no “visual range” in Blender's scene referred internal model. All values are valid, and 1.0 has no special meaning.</div><div style="margin: 0px; padding: 0px; ">The default sRGB output tone response curve only considers 0..1.0, but there is also one that preserves approximately 2 and a bit stops more (values of 4.5 IIRC).</div><div style="margin: 0px; padding: 0px; ">The transform to a display referred output is a creative decision on what values will become diffuse white. There is no real idea of white in a scene referred model, and again, 1.0 has no significance.</div><div style="margin: 0px; padding: 0px; ">> Some nodes like Mix or Math nodes have the checkbox for this and it's fantastic.</div><div style="margin: 0px; padding: 0px; ">Would seem like a bug for scene referred data. Difficult to deal with HDR IBL work.</div><div style="margin: 0px; padding: 0px; ">> However in many cases we have a need for clamping just "whites" or just "blacks".</div><div style="margin: 0px; padding: 0px; ">There is no value that is white in a scene referred model. LDR display referred imagery may have a previous diffuse white located at 1.0 when transferred as display linear, but it is merely achromatic in a scene referred model.</div><div style="margin: 0px; padding: 0px; ">> RGB Curves node in compositor doesn't clamp and when used in Cycles materials it clamps, so we have inconsistency. I'm aware that those are different nodes even though look almost exactly the same.</div><div style="margin: 0px; padding: 0px; ">Not sure why the Cycles one would clamp, and would seem a bug if it did.</div><div style="margin: 0px; padding: 0px; ">With respect,<br>TJS</div><br>_______________________________________________ Bf-compositor mailing list<span class="Apple-converted-space"> </span><a href="mailto:Bf-compositor@blender.org">Bf-compositor@blender.org</a><a href="http://lists.blender.org/mailman/listinfo/bf-compositor">http://lists.blender.org/mailman/listinfo/bf-compositor</a></div><div><br></div><div><br></div><div><pre style="line-height: 21.30000114440918px; white-space: normal; color: rgb(68, 68, 68); background-color: rgb(255, 255, 255); position: static; z-index: auto; ">Hey,<br><br>In many cases when using nodes we'd like to clamp output values to visual range (or to range between 0.0 and 1.0).<br>Some nodes like Mix or Math nodes have the checkbox for this and it's fantastic.<br>However in many cases we have a need for clamping just "whites" or just "blacks".<br>Would it be possible to split clamping such that we have two checkboxes: "Clamp Whites" and "Clamp Blacks"? Maybe the names are not the best especially for Math nodes, but I hope you get the idea.<br><br>Another thing is that RGB Curves node has no option for clamping at all. It would be very helpful to have this option.<br>When talking about RGB Curves - we have another issue: RGB Curves node in compositor doesn't clamp and when used in Cycles materials it clamps, so we have inconsistency. I'm aware that those are different nodes even though look almost exactly the same.<br>I understand that in most cases you wouldn't want to clamp in compositor and would want to clamp when setting materials, but it would be great to have an option (both in compositing and materials). Splitting clamping whites and blacks would be even better.<br><br>What do you think about it?<br><br>Cheers<br>Bartek Skorupa</pre></div></div></div>_______________________________________________<br>Bf-compositor mailing list<br><a href="mailto:Bf-compositor@blender.org">Bf-compositor@blender.org</a><br><a href="http://lists.blender.org/mailman/listinfo/bf-compositor">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br></div></blockquote></div><br></div></body></html>