On Wed, May 4, 2016 at 4:34 PM, J. Liles wrote:
>
>
> On Wed, May 4, 2016 at 2:26 PM, johannes hanika wrote:
>
>> hi,
>>
>> i would agree that this looks like a bug in the markesteijn algorithm.
>> another thing to try is probably the green equilibration thing that
>> some bayer sensors suffered
On Wed, May 4, 2016 at 2:26 PM, johannes hanika wrote:
> hi,
>
> i would agree that this looks like a bug in the markesteijn algorithm.
> another thing to try is probably the green equilibration thing that
> some bayer sensors suffered from. that there was some spill from blue
> -> one green and
Hi,
I'm having a problem with the lens correction module where more than one
lens in the database matches the exif data. The GUI gives a menu to choose
between the different matches but the correction data used is always the
same.
When a lens is chosen from the menu only its name is saved into th
hi,
i would agree that this looks like a bug in the markesteijn algorithm.
another thing to try is probably the green equilibration thing that
some bayer sensors suffered from. that there was some spill from blue
-> one green and red-> the other green (same line of the sensor, maybe
during readout
Group,
I've been trying to figure out the source of these horizontal line
artifacts in x-trans demosaicing, but without much luck.
The artifact also appears with VNG, but Markesteijn seems to amplify it in
two ways: 1) by reducing the number of other artifacts but not this one and
2) by increasin
