Yes, I know. Maybe I’m missing something here, since I haven’t done much testing with the dynamic profiles feature in RT. I was under the (possibly wrong) impression that the dynamic profiles feature in RT applied (by overwriting what section values where already applied) the whole sections contained in partial (or full, for that matter) profile files, meaning that any given section found in a .pp3 file, when applied through the chain or rules for a given image, would overwrite all keys in that section. RTPS always merges the keys when it processes a section, combining values from several files for the same section.
For example, the [Exposure] section may contain several entries:
[Exposure]
Auto=false
Clip=0.02
Compensation=0
Brightness=0
Contrast=0
Saturation=0
Black=0
HighlightCompr=100
HighlightComprThreshold=0
ShadowCompr=50
HistogramMatching=true
CurveFromHistogramMatching=true
ClampOOG=true
CurveMode=FilmLike
CurveMode2=Standard
Curve=4;0;0;0.050000000000000003;0.017144577454482151;0.12;0.056293599784506772;0.21799999999999997;0.17068922303460063;0.35519999999999996;0.41106299850999484;0.54727999999999999;0.7126570386677068;0.81619199999999992;0.9512966621491713;1;1;
Curve2=0;
But it is conceivable (and sometimes useful) that a user wants to just seletively enable or disable the auto-matched curves, or the exposure compensation, etc. In RTPS, for example, I have a partial profile that looks like this:
[Exposure]
HistogramMatching=false
This way, for certain kinds of photos, I want to automatically disable just the auto-matched curves, but I don’t care about the other keys present in the [Exposure] section. In RTPS, it’s possible to select this profile after all other partial profiles have been applied, and make sure only the auto-matched curve is disabled. All other entries in the [Exposure] section in the final generated .pp3 file are carried over from other “lower ranked” profiles.
This is where I may be wrong about how the dynamic feature handles partial profiles. Maybe the built-in profile selector in RT does the same as RTPS, merging section keys one-by-one, from several profiles, instead of overwriting the whole section keys as found in each partial profile file selected through the chain of rules.