To further explain; “introspection” just provides a description of the parameter fields of each module (for the latest version only). How this is used is up to whoever wants to use it.
So I was imagining one would want to have a complete XMP, but with the info for some (or all) modules’ parameters in “human readable” form. But instead one could also have a separate XMP/XML/csv “adjustment” file that could be read (via a script? whatever) and “overlaid” over the current values (just overwriting the fields it contains with the values specified; multiple instances would need to be dealt with carefully). Or treat any additionally specified field values in an XMP as adjustments to the blob that would also be provided (a “blob” would always be “complete” “by definition”). Or whatever other approach might be more generic and widely useful. Even when using individual fields, one has to be careful that their values or interpretation might change between versions. Or they might even be completely removed, so staying up to date with version changes would still be important.
If adjustments are to be provided in separate files, of course finding and handling those (matching them with the images/styles that need to be adjusted) is a separate topic that needs to be carefully designed. If everything in the same xmp, this is simpler and changes would only be needed in the saving and loading routines.
I once also got the idea, a little helper program could read the editabl/edited values and write a new blob., maybe the crawler could even initiate it, once he finds, the editable values are different from the blob
If I could code and would have the time, I would have started it already.
Would it make sense to update my FR #4250 accordingly or make a new one?
Apologies for resurrecting an already resurrected thread, but am I correct that the issue (“distance to subject” being locked when creating a preset) is still with us? I’m a bit confused in that there seem to be a workaround but maybe not? I cannot get it to work
Edit: Also, when you copy and paste the history stack from one image to another?
I appreciate the work going into DT and don’t want to criticize or demand, I only want a definite yes or no.
I believe the correct way is to create a preset which merely turns the module “on” and then apply that preset to your images, then the module will auto detect the settings.
I would also like to have the ability for a lens correction preset to save some parameters (e.g. disable vignette correction), and auto detect the remaining parameters.
This is because I feel like the vignette correction provided by lensfun is a bit too much for my particular lens.
From what I gather in this thread, there are 2 types of presets for lens correction:
Preset that only turns lens correction module on
Values like focal length, correction type (distortion, TCA, vignette) are automatically set to defaults
Preset saves every parameter in lens correction
This may apply the wrong lens type and focal length etc
May I ask, for the first type of preset, are the parameters assigned with an ‘auto’ tag or are they undefined?
And what is the technical challenge for a user to edit/generate the .dtstyle file to create a preset that includes some fixed values and some auto values?
