Long time user of DXO. Most recently PL5, skipped 6. Just upgraded and installed PL7 (v7.7.2). My problem is the default preset seems to be stuck on “Natural” which is anything but natural, as it is oversaturated with a highlight cut, midtone boost, and with clearview plus enabled, none of which I want. I want my default preset to be “Standard” as I have always used as a base for editing, and much prefer.
In Edit - Preferences -General - Correction settings I have specified DXO-Standard for RAW images. Then close the dialog and exit PL7. Restart PL7, and the default preset has reverted to “Natural”, despite “Standard” being shown in the Settings dialog box.
I can change the preset for the image I’m currently processing, but it should not behave in this way. Please can someone advise, this is a real pain.
PS I have tried setting other presets as the default, eg Black and White, Optical Corrections only, etc, and no matter which I choose it always re-opens with “Natural” as default. Help!
At the time you first open a folder in PhotoLab, the current default preset for RAW and RGB files is applied to the files in that folder. Closing and restarting PhotoLab doesn’t change a preset that’s already been applied to files. Closing PhotoLab and either renaming the folder or deleting the database before restarting PL will cause the new default preset to be applied.
Thanks. I don’t recall previous iterations of PL working in this way. Does that mean that now I’ve reset the default preset to Standard in Settings, when I next open any other (i.e. differently-named) folder, the default preset applied will be Standard? And from then I’ll be working with Standard as my default in future?
In the meantime I’ve selected all the images in the folder I’m working on, and set the preset to Standard and that’s working for this set of images.
Also I’d like to point out that “Natural” is nothing like natural and really shouldn’t be the default preset for a new installation. The default should surely be something neutral but with optical corrections. Others may disagree of course.
For any newly encountered image (one that’s not in PL’s database and/or for which there is not an existing sidecar/.dop file), PL will apply the default preset - as prescribed in Preference settings … Otherwise, current database/sidecar settings will be retained.
I have recently upgraded from v.6 to v.8 (Elite in both cases). I see that there was a change in v.7 that now has Natural and Standard versions. I am not used to finding the Selective Tone faders chosen for me. Obviously I want the lens corrections, but otherwise I want raw files to be treated as they always were in v.6, and go from there.
Can anyone advise on the settings I need in the Preset Editor and/or elsewhere to achieve this, please?
Hi David - - Are you saying that you’re using the Natural preset - but that you do not want it to be activating the Selective Tone sliders ?
If that’s the case then you could make your own version of the Natural preset - and then set it as the default preset (to be assigned by PL to all newly encountered images).
I am using the default settings, as Ihave always done; but I question why these now result in movements of the Selective Tone faders, which means that I have to memorise these settings in order to return to “first base”. Up to v.7 all corrections for different equipment were done behind the scenes and not reflected in the faders, which always started out at zero…
You would need to ask DxO that question … Note: This is a USER forum.
There’s an easy solution to this; simply create your own default preset, with all your preferred settings, and have it assigned to all newly encountered images.
stuck
(Canon, PL7+FP7+VP3 on Win 10 + GTX 1050ti)
10
The answer is, because DxO decided that these changes ‘Improved’ things. [Note the use of an uppercase ‘I’ to indicate the word is a proper noun, it’s just a name, it has no connection with the word ‘improved’, with a lower case ‘i’, which is an adjective describing a change for the better ]
When I upgraded from PL5 to PL7 I quickly discovered that the ‘Natural’ preset was far from natural and that the ‘Standard’ preset was not the same as the previous ‘Standard’. I therefore created my own preset and made that the default for RAW files.
Creating your own preset is simple. Set all the settings to what you want and then choose the ‘make preset from current settings’ option. Then in the Preferences dialog, choose your preset as the one for RAW images.
Could the use of wide gamut be the problem? You are coming from PL5.
George
stuck
(Canon, PL7+FP7+VP3 on Win 10 + GTX 1050ti)
14
You are confusing the original poster (@nputtick) who was upgrading from PL5 to PL7 with @david-p, who resurrected this topic 7 months after the OP, who has upgraded from PL6 to PL8.
Thanks for trying George. I only replied to this old-ish thread because I thought it was considered discourteous to start a new one on the same subject!
I havent had time today to solve the problem. Perhaps tomorrow…
It is possible that the move from PL6 to PL8 resulted in your default selection of ‘1 - DxO Standard’ in PL6 being “converted” to ‘1 - DxO Style -Natural’ in PL8 which would not give your desired result.
I cannot test what happens during the upgrade because I have PL6, PL7 and PL8 already installed
Whether the images using the “Standard” presets look the same on the monitor and in the eyes of the user, both during editing and then when exported is a matter of conjecture. The exports are certainly not the same size and a bit comparison shows difference between the releases.
The “so called” “Natural” setting is different in the editing commands used and definitely different when exported.
As various other posters have commented, using the DxO presets is useful as a general starting point but developing and using your own variants will lessen the risk of unexpected changes between releases!
Exported images for review ‘Standard’ first and then ‘Natural’
@Wolfgang Thank you I had worked out that they had chosen ‘1 - DxO Style - Natural’ and deprecated DxO Standard to ‘2 - DxO Standard’. I had guessed (wrongly) that they were using the numbering scheme rather than the position in the list!?
So we have the, words fail me, at DxO to blame for not leaving ‘1 - DxO Standard’ where it was and/or not honouring what the user had chosen as the defaults in the previous release, both of which would have maintained continuity!
There is something seriously wrong with DxO development that it cannot control its engineers from interfering with the product or the “UI Police” from not insisting on maintaining a workable continuity between releases.
The reason I gave up on Luminar (Skylum) many years ago was because they seemed to give each release to a new group of developers who developed a whole new UI rendering existing workflow etc. completely useless , NTSI - Never Twice Same Interface.
DxO are nowhere near as bad as that but neither are they as diligent as they should be!
With the paucity of release data for each release, particularly point releases, I am not sure that the first time DxO Support realise what has been “adjusted” is when they get complaints (Support Requests) from the users!?
The detour for this issue is not to use anything under direct DxO control and create user presets, as has already been stated, even if they are just a copy of the DxO preset.
However, that still doesn’t mean that DxO won’t make “subtle” changes to the component edits in the user created Defaults!
So we all need a test set of images to undertake our own regression tests on a new release.
]
