Why are Auto and Auto so different?

NN122830UL1

• May 21, 2011 17:20

Why are the results from the Auto button (top right on the tool bar) and the Auto button on the Levels toolbox so different on the same image?

I have got the Auto button on the tool bar set so that only Levels is enabled with my intention being once all of the images have been corrected for colour and exposure, etc, to select all of them and use the Auto button at the top right on the tool bar to do a batch, Automatic correction of Levels.

When I do this, a batch correction is certainly made but on some images, it is miles out (very definitely wrong and heavily clipped in the highlights and very burnt out). If however, I then use the Auto button in the Levels toolbox on the same image, the Levels are corrected very nicely but hugely differently than when the Auto button (with only Levels, enabled) on the tool bar top right. Like....there is 30 points difference?? i.e When using the Auto button from the top toolbar, the highlights are massacred to 202 but if I then use the Auto button on the tool bar, the highlights are corrected (pretty nicely) to 233.

What is going on?
Is this another bug?

I find enabling Exposure on the Auto button on the top tool bar to be a complete waste of time because all it does is apply a global correction of plus 5 on Contrast and plus 7 on Saturation and I am not aware of any way to adjust these parameters even if applying the same fixed adjustments to every image was any use in the first place

0

• 

  NN122830UL1

  • May 25, 2011 05:35

  Here is an image displaying error in v6.2 that I am referring to. The first image has had the levels adjusted by the "Auto" button in the Levels toolbox, itself....and the result is near enough...I have pasted the histogram for both images to show numerically what is going wrong although I cant see how this issue can be brushed under the carpet by attributing it to operating system, video card, insufficient ram, direction of wind, etc
  
  http://www.johnprendergastphotography.co.uk/Correct.jpg
  
  Here is the same image where the Levels were adjusted by using the "Auto" button that is on the top right of the main toolbar at the top of the interface. Only "Levels" have been enabled on this button and this may be useful if it actually worked. As you can see, Auto Levels performed this way has massacred the highlights....and makes the feature, useless
  
  http://www.johnprendergastphotography.co.uk/Wrecked.jpg
  
  When is the next update and will it address this error in the program?

  0
• 

  John7

  • May 25, 2011 23:16

  Thanks, I find that you're right. I noticed with 6 that I couldn't depend on the master "Auto" button to give me a decent starting point for corrections any more. So many of the highlights were so blown out that the adjustment was unusable. I would think that the master auto level should do the same thing as on the individual auto levels box. They are certainly different. I hope this is something they will soon fix, I use to depend on the master auto most of the time to give me a good starting point. Also, it would be nice to have the ability to set the default "Saturation" before doing a global auto correction. Just a default 5 for any type of file does not make sense to me. On some shoots I would like a global +15 on auto rather than having to do this on another step.
  
  JOHN

  0
• 

  NN122830UL1

  • May 26, 2011 00:23

  There are a great deal of bugs and errors being reported on this forum about the program that are "right" but are, for some unfathomable reason???????, being brushed under the carpet by way of attributing (mistakenly) to user error, Operating System, system spec, dodgy Ram or which way the wind is blowing..........
  
  PhaseOne should be doing better than this for its customers and should not be dumping errors on its customer base to iron out by beta testing (which I certainly never enrolled on)

  0
• 

  Jim MSP

  • May 26, 2011 03:41

  [quote="NN122830UL1" wrote:
  Here is an image displaying error in v6.2 that I am referring to. The first image has had the levels adjusted by the "Auto" button in the Levels toolbox, itself....and the result is near enough...I have pasted the histogram for both images to show numerically what is going wrong although I cant see how this issue can be brushed under the carpet by attributing it to operating system, video card, insufficient ram, direction of wind, etc
  
  
  Here is the same image where the Levels were adjusted by using the "Auto" button that is on the top right of the main toolbar at the top of the interface. Only "Levels" have been enabled on this button and this may be useful if it actually worked. As you can see, Auto Levels performed this way has massacred the highlights....and makes the feature, useless
  
  
  
  When is the next update and will it address this error in the program?

  
  
  Thanks for pointing this out. It explains some of the weird results I have seen.
  
  Please open a support case with your excellent example; they really need to log this and fix it soon.
  
  I am like a lot of folks. I often use the global "Auto" as a starting point.

  0

Post is closed for comments.