Open Beep6581 opened 9 years ago
Also: when I move black point to the right, the shadow contrast is reduced.
Reported by pinhuer
on 2015-02-04 16:53:46
I expirience this on 4.2.0. I believe that it is common behaviour for most versions.
It is the same in changeset a3a3cbc1a977.
This altering cannot be called "gamma" as a term of power function, it is something
different.
Reported by pinhuer
on 2015-02-04 23:46:24
It makes me think that data scale does not match curve scale in certain circumstances.
Reported by pinhuer
on 2015-02-04 23:58:54
>This altering cannot be called "gamma" as a term of power function, it is something
different.
Indeed, it is a matter of some gamma function, I changed my mind.
Reported by pinhuer
on 2015-02-05 12:39:15
This is an interesting find and I hope someone looks into it.
pinhuer how do you make those curve diagrams?
ps. "2) open in RT, select all neutral settings and gamma 1 input profile;"
At neutral settings, black=0 and shadow compression=50 but grayed-out. When you change
black so black!=0, shadow compression should be 50, not 0. Can you confirm?
Reported by entertheyoni
on 2015-02-05 12:48:27
>pinhuer how do you make those curve diagrams?
You will like it. Just open the PSD.
http://filebin.net/5a9ms7ge4d
>Can you confirm?
Yes, my .pp3 corresponds to that. You may check it yourself, I attached it.
Reported by pinhuer
on 2015-02-05 15:31:07
I am trying to dig the code right now but I am not able to find the data array which
corresponds to Custom Tone Curve 1. Could you point at it?
Reported by pinhuer
on 2015-02-05 15:33:56
pinhuer: Do you need a hint where the Custom Tone Curve 1 is applied or a hint where
its data is stored?
Ingo
Reported by heckflosse@i-weyrich.de
on 2015-02-05 15:58:39
pinhuer: q&a will be much faster if you join #rawtherapee on IRC
Reported by heckflosse@i-weyrich.de
on 2015-02-05 16:03:21
OK
Reported by pinhuer
on 2015-02-05 16:05:10
I found out that LUT data arrays are the same for TIF and DNG.
Must go deeper.
Reported by pinhuer
on 2015-02-05 18:11:08
For an illustration one should take a photo with deep shadows, let everything neutral
and set gamma 1 profile as input (however, camera-matched profile gives the same result),
export to TIF and then set same curve for both TIF and DNG file - just rise the black
point. The output will differ, most visibly in shadows.
Reported by pinhuer
on 2015-02-05 18:36:05
All 4 curve modes produce equally unequal result of DNG export compared to TIF export.
Reported by pinhuer
on 2015-02-05 20:40:53
Tone curve 1 and 2 yield same result.
Reported by pinhuer
on 2015-02-05 20:44:01
pinhuer, I can give you a hint in irc
Reported by heckflosse@i-weyrich.de
on 2015-02-05 20:48:56
Latest comment from heckflo was that there is inverse gamma in Improcfun.cc which linearises
the image data and that image data from rawimagesource and from stdimagesource have
different gamma (scale).
Custom tone curves were applied before iGamma and thus had different effect on TIFs
and DNGs.
Reported by pinhuer
on 2015-02-06 16:18:37
For non raw images the inverse gamma in rgbproc() is completely skipped.
Reported by heckflosse@i-weyrich.de
on 2015-02-06 16:36:31
Will it be tolerable to make current profiles for TIF files incompatible?
Or: is it critical to check for type of imagesource (raw vs std) and adjust behavior
accordingly?
Reported by pinhuer
on 2015-04-03 14:49:08
You can check the PP3 version tag and keep the old behavior for old PP3s, and new behavior
for new ones. I would suggest you first submit a patch with the new behavior and explain
why it's better, and then proceed to code support for the old behavior when using old
PP3s only if the team agrees that the new behavior is an improvement and is usable.
Reported by entertheyoni
on 2015-04-03 21:54:24
The plot is in that curves are currently linear for TIF files (and for RGB curves of
Bayer files) and gamma-scaled for Bayer files (because of the position of iGamma).
It makes sense to make tone and RGB curves to behave in the same way, it is expected
(by me at least).
Keeping old behaviour for old PP3s does not seem good to me - because there is no way
of escaping it and proceeding to new processing version.
I think that I will code the check for type of imagesource and set the curves scale
accordingly if the curves scale is not written to pp3 already.
Reported by pinhuer
on 2015-04-03 22:10:38
Some weeks ago you were working on curve modes - gamma-corrected X, Y, or both. The
details escape me. If you finish that patch, the user will have a combobox with a choice
of curve scaling, correct? If so, then that would help here: if the PP3 version is
old and the image is non-raw, set the curve scaling to linear when opening the image,
and gamma-corrected when raw. If the PP3 version is newer than foo, set the curve scaling
to whatever the new default will be. I think that would be clear to the user and be
backwards-compatible.
Reported by entertheyoni
on 2015-04-03 22:39:31
Pinhuer, to get used to backwards compatibility, search for ppVersion in procparams.cc
and also have a look at ppversion.h!
Ingo
Reported by heckflosse@i-weyrich.de
on 2015-04-03 22:50:56
>If you finish that patch, the user will have a combobox with a choice of curve scaling,
correct?
Yes.
>Pinhuer, to get used to backwards compatibility, search for ppVersion in procparams.cc
and also have a look at ppversion.h!
That is another way.
But: is version information included in partial profiles and in RTC files?
Reported by pinhuer
on 2015-04-04 13:28:17
Started by Pinhuer.
Reported by entertheyoni
on 2015-04-04 18:38:19
Started
Originally reported on Google Code with ID 2657
Reported by
pinhuer
on 2015-02-04 16:52:16