YOUR ACCOUNT

Login or Register to post new topics or replies
Beat
Beat
Posts: 165
I don't get the remapping of the value (wheel). And I don't get it's normal functioning either, I'm afraid.

If I connect the value component to e.g. Source A of an Add component. I set Source B to 0
As expected, with Values <=0 I get black as Result.
With value 1 I get white. All right.
I also have connected the same Value component to a Log component, with Base set to the natural Log (2.718).
As it should b, with Value 1, the result is as it should be, black (0).
But with Value 3, the result should be a bit more than 1 (so white), but it is dark grey, so nowhere the value it should be IMHO. Only around value 2600, I get white.

So far the normal behavior. Now the Remapping :
How can I stop the wheel from turning to a value (I mean the value the user gets to see) above or below the max and min I have set in the remapping.
I think it's very confusing if the user turns the wheel above the max value, but can keep on turning, but nothing happens behind the scenes, as the program (by means of remapping) clips the value to the max. But the user is not informed about that.
I think the wheel should not be made possible to move past the max or min settings in the remapping.

Kind regards, Beat
The Stone Age did not end because they ran out of stones. Niels Bohr
  Details E-Mail
Sphinx.
Filter Optimizer

Posts: 1750
Filters: 39
Try the standard slider instead, it sounds like it does what you want smile:-)

(if not, try posting a filter that shows the problem)
  Details E-Mail
Beat
Beat
Posts: 165
Actually the standard slider behaves even more wrong with Log (goes the wrong way).

But that is not the heart of my question. I would like a better understanding of the relation and differences between the Standard Slider (1-100)and the Value wheel (-n to +n). Could I say that the value of the value wheel times 100 is the same as the value of the Standard Slider? E.g. value 0,9 = Slider 90? It seems so when I use the Add component.
What confuses me is maybe that there are different ways of using numbers in HDR and LDR.
Is it always that in LDR 127,5 means 50 in Slider value and 0,5 in Value wheel value?

After some more experimentation I think I get my head around it a bit.
If I get it right, FF has 3 interpretations for numbers : Slider 1-100 , Value (= 1/100 of Slider) and the RGB ColorValues, where 255= 1 (in Value wheel) and 100 (in Slider). Is this correct?

It still leaves my remarks in the original post about the remapping.

Thanks, Beat
The Stone Age did not end because they ran out of stones. Niels Bohr
  Details E-Mail
emme
Posts: 718
Filters: 8
Yes, LDR works in the 0-1 range (0-255 in RGB values). HDR for anything beyond that. By default the Slider and IntSlider output is in the 0-1 range, but can be remapped to any values. The value Control is unlimited in range, so like Sphinx said, perhaps better use the standard sliders if you want to limit the UI range. The downside is that the user won't see the actual value coming out the control - only a relative value. The 0-100 range of the slider is kind of arbitrary, but can be thought of as 0-100 percent. Check out the FF manual for more info.

My guess is that you accidentally used base 2718 for the log instead of 2,718. The math adds up smile:)
  Details E-Mail
Beat
Beat
Posts: 165
The downside is indeed that with a Slider the user only sees relative values.

Emme, you're right in that I must have left out the comma in the base of the Log. I was sure I had put 2,718, but obviously not. Now Log works fine. Thanks for pointing out my mistake.
The Stone Age did not end because they ran out of stones. Niels Bohr
  Details E-Mail

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,711 Registered Users
+18 new in 30 days!

153,531 Posts
+39 new in 30 days!

15,347 Topics
+72 new in year!

Create an Account

Online Users Last minute:

17 unregistered users.