Search the Community

I would like to know what the Develop Assistant > Exposure Bias(option)/Compensation(message) does in APh (1.10.0.244), I am as unclear as the poster below. As the other poster states EC is baked into the pixel data by physically changing the amount of light. The attached image was shot with a +2 EC to make any differences extreme. EB-ApplyExposureBiasAsDefault - Appears to apply the exposure compensation a second time while setting the slider to zero. With +2EC this saturates most pixels. EB-ApplyExposureBiasAsInitialState - Appears to apply the exposure compensation a second time while setting the slider to the EC value in the raw file. With +2EC this saturates most pixels. EB-TakeNoAction - Self explanatory and my current option. Assuming Exposure Bias(option) is the same as Exposure Compensation(message) it would help to use a single term.

The Map Default Region option defaults to Europe even though my default System-wide region is set to US/North America. Is this a bug? Seems like it should respect my System's setting, not Serif's native Europe setting. #MAGA

Goog morning, I've searched through the forum but didn't found a satisfying answer. What exactly is the difference between "Bias as default" and "Take no action" ? As can be seen in the EXIF data, the image was taken with an underexposure of -1.7 stops. I did the test with "Apply tone curve" as default. Using "Apply exposure bias as initial state" the bias is shown correct in the Exposure section. Using "Apply exposure bias as default" on my screen the image looks +/- the same but the bias in the Exposure section is set to 0 ! Using "Take no action" shows a total different image ! IMHO, opposite to the setting used, a lot of actions must have been executed !

I'm a great fan of James' video tutorials (thanks, James!) but the video on exposure bias and the develop assistant settings has me flummoxed - either I am totally missing what these settings are for, or they are not working as they should. James explains that AP does not apply EB (based on the setting in exif) by default - which is where I started to get lost. After all, the exposure compensation setting causes a "physical" change in the camera settings to achieve the desired result - so how can AP not apply these, I wondered - after all, that would mean AP ignoring what I told the camera to do. To test, I took two RAW images based on -1/3 and plus 2 EVs, with aperture and ISO fixed so the variable was shutter speed. The develop assistant setting was "do nothing" and on loading into AP, the images looked about what I was expecting - and compared near enough to Lightroom. "So far, so good" as someone one said... I then tried the "initial state" and "default" options and in both cases the exposure bias was applied yet again, so doubled up - so effectively -2/3 and +4 based on what the camera "wanted" to do and -1/3 and +2 on what I had told it to do. In summary, the results were: No action - images as expected/wanted - slider setting 0 Initial state - image effects "applied again" up so darker or lighter than expected/wanted - slider setting being the EB/EV value Default - image effects "applied again" so darker or lighter than expected/wanted - slider setting 0 I'm getting the results I want using "do nothing" so I'm leaving develop assistant on that - but why would I want to apply the EB/EV already applied to an image again so it doubles up? If, as in James' video, I know that my camera consistently over/under exposes then I guess that might warrant a standard user setting to apply to all images from that camera, but even that must be inconsistent depending in the scene, I would have thought, and wouldn't be based on the exif data as this adjustment would aim to effectively override camera settings. What am I missing? Cheers

Hi there, so good, that you added the assistant to the develop persona. Now the auto adjustments could be switched off, which for my camera is vital (Canon EOS 450D). Two things regarding that as feedback: - could you let the assistant remember the users settings? As it is now, you have to switch off the auto adjustments with every different raw file you open. - the auto adjustments might not be necessarily a bad thing with every picture. It would help tremendously if the adjusted values would be visible in the settings, so that you could fine tune the settings. As it is, every setting start with the same value whether it is auto adjusted or not. Then still: The raw quality is still inferior by far in comparison to the jpeg file, it is really, really noisy and thus lacks detail that is visible when I open the jpeg file. Might be just my camera... All the best and keep up the great work!! Oliver