Problem with Presets impact each others

[Eyalr]

Hello,

I have strange problem with Presets - I have one preset for importing photos. When I create new preset, the new one gets the definitions of the first one and the opposite. It looks like they impact each other. I define both of them from the same photo, maybe this is the problem ?

I am using Lightroom Classic version: 13.0.1.

With Operating system: Windows 11 - Home Premium Edition

Thank you, Eyal

[Eyalr]

I spent a lot of time yesterday with Adobe support –

1. Accordingly to the one who assist me, when i open the new preset with Update option, it was updated immediately from the other one, this is how LR work
2. If I create new one with less options it will be ok until I will open it again
3. There is no option to edit the preset content after it was created.

[richardplondon]

When you select a previously made import preset, the settings in the various panels load up accordingly.

At this point no option is shown to update the preset - logically enough IMO, that would merely keep it the same.

But the moment you've altered an import setting, the menu displays "[presetname] (edited)" instead.

An option is then shown to UPDATE [presetname] accordingly.

But whatever settings showed when you imported, appear in the starting point for next time. To get back to the preset as it was saved, you'd need to select that again.

I will often have applied suitable (bulk)  keywording during my prior import, so have made the firm habit of reinitialising everything (by selecting my same preset afresh) with each new import.

[Eyalr]

Thank you!
So your advice is to have preset with the most changes i want to have and to use it after I import the photos?
I have now 2 presets:
1. Import - include profile and Lens corrections options
2. Landscape_001 - Include other changes as Basic Details updates.

[richardplondon]

There's a small confusion here I think. An import preset controls such things as whether a Move, Copy or Add operation is to be carried out, and where (in the case of a Move or Copy) the file is to be put, and within what kind of folder filing scheme - such as date based, which is what I use. Also any file renaming, bulk keywording, and whether a particular Develop preset (image adjustments) or Metadata preset (copyright details etc) should be automatically called in as part of the import process. This is not the place where this Develop or Metadata preset would be altered - it is only that a certain preset is being applied by name.

If you don't invoke a Develop preset during import, then one can be applied after import with identical effect: except that in the latter case, a new History step would show accordingly for those images. 

Also if you don't invoke a Develop preset during import, one of two things will happen: the image file being imported already has some Adobe proprietary Develop metadata attached, in which case that will be used; or, the current processing defaults for that camera model and that file type (Raw, or non-Raw) will be called in. Those processing defaults may involve a particular named Develop preset, that imposes your own desired standard starting point for all images of that type.

When you refer to a Develop preset in your import settings (regardless whether you have used an import preset or not) that is a reference by name. The same is true when a Develop preset is invoked as your camera processing default. Updating that preset in the usual way within Develop, and deciding again which checkbox options should be enabled or disabled, updates it wherever it may get used in the future.

I find it useful to have a completely tested and standardised import preset. I vary from that with each import so far as any keywording which applies across the entire import batch, but this is optional - it could be equally well done after import. The same is true of selecting a Develop preset to be applied silently as part of import.

Doing those things overtly after import allows applying presets, equally keywords, differently to different groups within the overall imported batch. During import is: all, or none.

Also doing these actions after import leaves your import setup otherwise unvarying and predictable. No micromanagement needed each time, it's a simple push-button exercise. Still a good idea to verify the right IMPORT preset is chosen (so that the right actions happen to these images so far as folder location, renaming etc), but that is all.

[Eyalr]

Thank you very much!
I will have import preset include naming convention, metadata, folder to keep the files etc.
All other issues, especially editing issues i will define in the Landscape_001 preset or others.

[richardplondon]

Many kinds of preset in LrC, it's good idea IMO to always be clear when discussing in forums whether you mean a Develop preset or something else. You could make a number of import presets that each select a different Develop preset. But that would be complex and tedious to manage. You could choose a particular Develop preset manually in the import settings but need to then stay aware this is silently persisting for further imports until changed. So I recommend applying particular Develop presets (I assume that's what "Landscape_001" is) only after a 'neutral' standardised import is complete. Metadata presets make sense during the import though, IMO.

[Eyalr]

Thank you, now it's clear, Eyal