I don't know why exactly, but it doesn't surprise me either.

I have had similar issues developing plugins that apply develop settings, because some things depend on other things that need some "settling time".

e.g. One must wait for profile-based lens correction enabling to settle, before selecting a profile.

One must wait for custom white balance to settle, before changing temperature / tint.

And one must wait for a new process version to settle, before changing things unique to that process version.

I know this probably doesn't help you much. But to Adobe: the ability to have interdependent settings (administered by a preset) handled by Lightroom in a fashion that honors the dependencies would be great, for users with preset issues, and developers making editing plugins that issue changes by way of (temporary ad-hoc) presets.

R

davidnaylor83 wrote:

 

I created a preset for switching to process version 2012, with some added sharpening and a defringe setting of 0 (to override the "default" of 1 that has appeared on many of my photos).

 

When I apply it, the exposure (and any other tone adjustments in the basic panel) get reset to 0.

I think the bug is that the only "intelligent" conversion from PV2010 to PV2012 happens when clicking on the "!" button or manually switching to PV2012 in the calibration panel. Applying a preset just does a "hard switch" to PV2012 without any conversion. And because all settings in the basic panel except WB, vibrance and saturation are internally completely new settings in PV2012 (even if they have the same name as before), they just appear as being reset, but essentially they just become visible now and are on their default/previous *) values.

I don't know whether or not this behaviour is really intended.

*) A little demonstration:

1. Reset an image to Adobe defaults (PV2012 is used)
2. Set exposure to -3 (this is the PV2012 exposure variant!)
3. Set to PV2010
4. Set exposure to +3 (this is the PV2010 exposure variant!)
5. Apply your preset

Result: Exposure "resets" to -3, or more correctly, the PV2010 exposure vanishes and PV2012 exposure becomes visible again.

This behaviour can make presets behave a little bit unpredictable if they contain the process version 2012, but none of the settings that are new in that process version, and are applied to an image with process version 2010. The outcome of assinging the preset depends on the PV2012 values that were set somtimes before in the past.

My personal opionion on PV2010/PV2012 is that the handling of presets is not fully developed (perhaps it was rushed?). It leads to too much confusion.

davidnaylor83 wrote:

 

When I apply it, the exposure (and any other tone adjustments in the basic panel) get reset to 0.

Pretty sure the "update logic" of translating of PV 2003/2010 to PV 2012 is only available in either the ! update or the dropdown in Camera Calibration. Since all develop settings are absolute, if you DON'T select anything other than the Process Version, only the PV is changed and the image is set to default. I don't think there's a way around this in presets...