Passing real float values

In my quest to build a simple 32bpc CC filter, I can't seem to create a color with overbrights, which means I can't make things brighter, only darker.

Nodes like Levels and Blend should not clip overbrights.

-Stu

--
www.theorphanage.com
prolost.blogspot.com

It's common in 32bpc systems to either not clip or provide the option. This is how it works in After Effects, Motion, Combustion, etc.

But anyway, I'd be more than happy to use another node -- all I'm trying to do is gain up my image by 100. Which node should I use?

Thanks for the help,

-Stu

Thanks uberzev,

Looks like you and I have different definitions of Gain. To me, gain is multiply. I.e. to gain your red channel by 2 is to multiply the values by 2.0.

That's what I'm trying to do -- multiply my data (or slider input) by 100.

-Stu

What I'd like to do is multiply an image by, say, 0.75 in red, 0.95 in green, and 1.35 in blue. This will tint the image cyan by darkening red and brightening blue. If there are any values in the image that are 100% in the blue channel, those values will become overbrights at 135%.

-Stu

Close, but the idea is that a slider value of 0.0 results in black, 1.0 results in no change, and 2.0 results in twice as bright. A simple multiply.

-Stu

Hey, I really apreciate you exploring this with me!

This one still doesn't quite work because if you set Red Levels all the way to zero, you still see the very brightest parts of the image poking through.

That tone curve thing is just bizzare! Its sliders are completely counterintuitive.

-Stu

Grr...

Quote
uberzev wrote: Grr...

Yes, feel my pain.

This should definitely NOT be a hard thing to do.

-Stu

Quote
ProLost wrote: In my quest to build a simple 32bpc CC filter, I can't seem to create a color with overbrights, which means I can't make things brighter, only darker.

Color channels have the range of 0...1, the overbrights are clipped. However, since everything is calculated in double-precision floating point, you can work around the clipping by narrowing the dynamic range of your input, performing all necessary operations in the narrowed range, then increasing the range to its original "width" (this will clip the overbrights).

The problem with this approach is that FF currently doesn't have a math component that multiplies color channels by numbers greater than one 9a Gain operation you discussed in another thread). This component is already planned.

Quote
Vladimir Golovin wrote: Check it out -- it has a lot in common with FF.

Looks cool, thanks for the link! However, despite the fact that both Conduit and Filter Forge use node-based approach (which isn't new or unique), they are quite different in some of their key assumptions.

Conduit is built for people with "compositing mindset", and is based on many assumptions, concepts and terms well known among compositing professionals.

Filter Forge, on the other hand, is built with the "Photoshop mindset" in mind, because we market it as a Photoshop plugin. Look at our Adjustment components (see, we don't even use the term "nodes" in our official terminology) -- all of our Adjustments (Brightness/Contrast, Levels etc) were designed to be immediately familiar to anyone who used Photoshop.

Check my reply at http://www.filterforge.com/forum/read...=5&TID=623