Skip navigation
Currently Being Moderated

Green Equilibrilation on Olympus E-M5

Aug 15, 2012 5:36 AM

Tags: #green #moire #olympus #om-d #e-m5 #equilibrilation

Hello,

 

I noticed that LR4.1 seems to use green equilibrilation on raw files coming from the Olympus OM-D E-M5 albeit it is not needed. This results in additional moire and loss of very fine detail compared to what other software is capable of delivering out of E-M5 raw files.

 

As far as I know LR applied green equilibrilation on all Olympus files in the past, because it was necessary. Now I wonder if this is a left-over/bug or if it is still done deliberately?!

 

Thanks,

Timur

 
Replies
  • Currently Being Moderated
    Aug 15, 2012 10:53 AM   in reply to Timur Born

    Not doubting you Timur, but purely as a point of interest, how can you tell green equilibration is being applied? Is it purely the moire and loss of detail?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 15, 2012 2:17 PM   in reply to Timur Born

    Hi Timur,

     

    I'm not sure your assertion that it is not necessary is actually correct.  I checked a DNG and the BayerGreenSplit value is 250, so you are correct that it is being applied.  I took said DNG file and edited it to set the BayerGreenSplit value to 0.  The result was mazing artifacts in the sky.  In fact looking at the default file (250) it appears close to an optimal choice for the split value as there is just the very slightest hint of mazing in the sky and the detail loss in the rest of the image is very low.  At least in my sample image I'm not seeing a difference in Moire between the 0 and 250 setting, though I've only got a few features with Moire in the scene.  Based on that I'm thinking someone very intentionally and carefully set the BayerGreenSplit value being used.

     

    What is your basis for deciding it isn't necessary?  Be aware that examining RAW histograms of a grey target and see the channels the same is not sufficient.  The split is not just required for different luminance sensitivities but also for cases in which spectral response is different.  A better test is to shoot blue and red patches or ramps and then carefully examine the G1 and G2 values.  Sometimes even though they were equal on a grey target they differ on a blue or red target.

     

    Ken

     

    EDIT: Here is the two versions, 0 on the left, default of 250 on the right:

     

    http://www.kenandchristine.com/photos/i-zDZK7xX/0/O/i-zDZK7xX.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 19, 2012 8:19 PM   in reply to Timur Born

    Hi Timur,

     

    I just wanted to follow up and say that I've examined G1 and G2 samples from a variety of color patches and found no case in which they differ.  So my earlier caveat about there possibly being different spectral responses even if the gains appeared equal on grayscales does not appear to apply.  It really looks like G1 and G2 are identical as you stated.

     

    Still sort of curious about the increased mazing when BayerGreenSplit is set to 0 rather than the default of 250.  I really can not see a significant difference in detail between the two, but I do see additional mazing.  I wonder if the BayerGreenSplit parameter is being tuned by sight or a test pattern by Adobe regardless of whether the G1 and G2 channels are actually different?  Or is it just an oversight from previous cameras as you suspect?

     

    Would love to hear a clarification from the Abobe folks on this one...

     

    Ken

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 4:49 AM   in reply to kwalsh74

    My understanding from someone at Adobe is that, for current versions of LR and ACR, the BayerGreenSplit value functions only as a on/off switch, zero being off and anything non-zero being on. In earlier versions, the value was meaningful, but in the latest versions the algorithm in effect autotunes itself to an optimal value.

     

    Note also that if LR/ACR recognize the camera model in a DNG file, they will ignore the BayerGreenSplit value anyway.

     

    Sandy

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 6:53 AM   in reply to sandy_mc

    Thanks Sandy and Timur for the follow up information.  It does sound like ACR/LR is using this parameter on purpose in cases other than where there are actual G1/G2 differences.

     

    Timur, be aware of the rather different default sharpening algorithms used in ACR/LR compared to both RT and DXO.  If you want to make a better detail comparison be sure to crank up the "Detail" slider in LR/ACR to 100 or close to it.  That will get the ACR/LR sharpening algorithm to act more like the RT/DXO algorithm and give much more comparable results.  The default position in LR/ACR is a bit conservative and in my opinion biased a bit towards portraiture and wedding photographers who really aren't interested in fine detail.

    sandy_mc wrote:

    Note also that if LR/ACR recognize the camera model in a DNG file, they will ignore the BayerGreenSplit value anyway.

     

     

    Hmmm, I'd say my example clearly demonstrates this isn't that case.  All I did was take a LR generated DNG and edit the BayerGreenSplit value and then reimport into LR and the rendering is clearly different.  So I'd say at least in this version of LR that LR is definitely reading the BayerGreenSplit value and applying it even when it recognizes the camera information in the DNG file.

     

    Ken

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 9:02 PM   in reply to Timur Born

    Timur Born wrote:

     

    Thank for the hint, but my demonstration images 1,2 and 4 did not use any kind or sharpening or noise filtering at all.

     

     

    No, actually you did!  That was my point, there is no such thing as demosaicing without sharpening. The demosaicing kernels sharpen to a degree no matter what and depending on the software there will be more inherent sharpening in the demosaicing algorithm. Zero isn't zero, it is just as arbitrary a point as randomly setting the sharpening slider is and varies just as much between software.

     

    Thank you very much for the details on set 3. That I think is the more illuminating way to compare the tools and does a much better job showing what recoverable detail there is than a zero sharpening (i.e. arbitrary and not equivalent) setting. I haven't looked at different RAW converters in about two years and it is really helpful to see your results as you've clearly got some good experience with a selection of them.

     

    Ken

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 16, 2012 3:11 AM   in reply to Timur Born

    Hi Timur,

     

    Been a bit since I did it, but if I recall correctly you need to use two tools.

     

    First get exiftool and run it with the -htmlDump option on the DNG file.  This will create a HTML file you can open up in a web browser that breaks out all of the EXIF, TIFF and DNG tags in an easy to read format.  It includes even those tags that exiftool usually doesn't display or let you edit.  This HTML display also shows you the hex address offset into the DNG file for all these tags.

     

    Next, choose a binary hex editor of your choice, open the DNG file, go to the address for the BayerGreenSplit tag indicated in the HTML file and edit it to whatever value you choose.  Save the change.

     

    That is a bit round about, but it was the fastest way I could do it with the tools I had on hand without writing actual code to do it.  In theory any TIFF tag editor should be able to change the value as well, but I haven't found a good one of those.

     

    Hope that helps!

     

    Ken

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points