 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
As far as I understand this slider action, I would prefer:
- Either two sliders, the left one being used to set the correspondence between the 8-bit value zero and some HDR values and the right one being used to set the correspondence between the 8-bit value 255 and some higher HDR values.
- Or no slider at all, APP being able to determine the best fit, that is the setting where the largest number of HDR values in the panorama correspond to "visible values" of the [0..255] 8-bit interval.
If neither is possible, then I missed something...
Offline
Hello GURL !
What you ask is to disable HDR display for HDR data. HDR data cannot be fully displayed on screen correctly because of it's wide dynamic range.
We could lower the contrast enough to display all the dynamic range on the screen, but the resulting image would look flat and dull, and you would loose the ability to check each zone with the hdr slider.
This particular slider is here to adjust display, not output.
What you ask is already provided by tone mappers : convert a high dynamic range image to a low dynamic range displayable on a screen.
Offline
f.simond wrote:
This particular slider is here to adjust display, not output.
What you ask is already provided by tone mappers : convert a high dynamic range image to a low dynamic range displayable on a screen.
So that tone mappers actions do not depend of this slider setting ?
(A quick and dirty test I just did seems to confirm that the answer is: YES)
Last edited by GURL (2006-03-02 12:05:28)
Offline
I've misunderstood this too - if the slider only effects display is it best to go straight to tone mapping? What value is there in having it?
Bill
Offline
You are right, it's not really cleverly designed. I'll redesign it for the v1.3 version.
The slider is just here to be able to get something displayable. It doesn't affect tone mapper.
Offline