Lightroom Classic CC 7.3: default settings only partially applied on import

  • 3
  • Problem
  • Updated 3 weeks ago
  • (Edited)
There appears to be a bug in Lightroom Classic CC 7.3 with regards to camera default settings: they're only partially applied on Import.

For example, in my default settings, I apply a camera profile (Camera Neutral) - this works.

I also use a fixed, custom white balance - this doesn't work. Lightroom always uses the "As Shot" white balance from the camera instead on import.

"Remove Chromatic Aberration" is on in my default settings (why does that default to off, anyway?), but it's off after importing.

Only when I use "Reset" on a newly imported photo, ALL of my custom default settings are applied.

I reverted to version 7.2, and my default settings are applied right on import, as expected.

I'm using Windows 7 64bit.

Thanks for looking into it
Alexander.
Photo of Alexander S. Kunz

Alexander S. Kunz

  • 23 Posts
  • 6 Reply Likes

Posted 3 months ago

  • 3
Photo of brian scantlebury

brian scantlebury

  • 19 Posts
  • 3 Reply Likes
Sorry, I'm not going to be much help. I have been experiencing same probs, amongst the raft of other issues.
I spoke to Adobe 1 month ago about these, they went away to find the solution and never came back. So I went again (3 contact on this issue) and they gave up, just plain could not work out why or what to do.
Strangely enough a week-10 days ago, the lens profile setting just started working - out of the blue!!!!
Hopefully your might do that too.
I dont use custom white balance on import, but I did use chrom.Abbr. That doesn't work now, have to do it manually every time.
Photo of Alexander S. Kunz

Alexander S. Kunz

  • 23 Posts
  • 6 Reply Likes
Thanks for the confirmation Brian. For the moment I'll stick to version 7.2.
Photo of Akshay Mathur

Akshay Mathur, Employee

  • 28 Posts
  • 7 Reply Likes
Hello Alexander,

Thanks for sharing with us your problems.
Can you please explain in detail, how do you set your defaults while import ?
 Have you created a develop preset which you apply during import ?
It will be of great help if you can share with us your workflow steps, so that we can reproduce the issue and fix it.

Thanks,
Akshay
Photo of Alexander S. Kunz

Alexander S. Kunz

  • 20 Posts
  • 6 Reply Likes
I have set my defaults in the Develop module, using the Develop menu, "Set default settings..." menu entry.
Photo of Todd Shaner

Todd Shaner, Champion

  • 991 Posts
  • 324 Reply Likes
Keep in mind that custom Develop default settings are specific to camera model, file type raw and non-raw (JPEG, TIFF), and even ISO setting if checked in menu Preferences> Presets> Make defaults specific to camera ISO setting.
Photo of Alexander S. Kunz

Alexander S. Kunz

  • 23 Posts
  • 6 Reply Likes
Again, Todd: it works as expected, and like it ALWAYS did, in v7.2, it doesn't work in v7.3 anymore - where are your questions supposed to lead, other than wasting time?
Photo of Alexander S. Kunz

Alexander S. Kunz

  • 23 Posts
  • 6 Reply Likes
Also, allow me to repeat what I already wrote above: Only when I use "Reset" on a newly imported photo, ALL of my custom default settings are applied.

They're not applied on import anymore. Coincidentally, the whole profile/preset system was changed in version 7.3...
Photo of Todd Shaner

Todd Shaner, Champion

  • 991 Posts
  • 324 Reply Likes
It sounds like you're not interested in "trouble-shooting" this issue with LR 7.3. That's fine and in fact I've rolled-back to LR 7.2 for similar reasons (corrupt catalog backups, Develop preset issues, etc.).

To roll-back to LR 7.2 open the Creative Cloud app and click the down arrow next to Lightroom Classic CC, select 'Other Versions' and then select 7.2. See if this resolves the Default Develop settings issue.

Sorry, I just noticed you've already rolled back to 7.2. Hopefully this will be fixed in the next update 7.3.1.
(Edited)
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4133 Posts
  • 1473 Reply Likes
Todd, note that the corrupt backups was in 7.2 (everything since 7.0) so you'll want to back up manually for the minute.
Photo of Todd Shaner

Todd Shaner, Champion

  • 991 Posts
  • 324 Reply Likes
There also appears to be a long standing (pre 7.0) issue with the 'Integrity' check when backing up a catalog file on exit from LR. Any catalog corruption detected during the backup process is NOT reported. If you hold down the CTRL or CMD key when launching LR and select the Integrity test it will report any detected catalog corruption. Unfortunately the current catalog "repair" process doesn't "fix" it even when the catalog appears to be working properly. Adobe is working on a solution to both issues, which should be corrected in the next update.
Photo of Arvid Uhlig

Arvid Uhlig

  • 11 Posts
  • 1 Reply Like
Hey Folks, 
simmilar problem here!

please be patient with me, i'm no native speaker, so my english might be a little rough.

If i set a default develop setting (camera & iso specific) the settings i do (especially sharpening / noise reduction) are applied perfectly on import.

But if i apply an additional preset on import (for example for color correction) the settings from the default develop settings are not applied correctly (for example sharpening is set to lightroom standards)

any suggestions about that?

thanx 
Photo of Arvid Uhlig

Arvid Uhlig

  • 11 Posts
  • 1 Reply Like
By the way,

i updated to 7.4 right now, and it didn't fix the problem (see above!)
Any suggestions here?
Photo of brian scantlebury

brian scantlebury

  • 19 Posts
  • 3 Reply Likes
I'm now in 7.3.1. Still Nothing seems to be  the same as it was . The host of issues continue. For the time I can only put up with it. Adobe don't seem to be able to work it out. I have tried again. but the communication system and promises to get back always fall apart.
I'm still experiencing the same camera/lens profiles issues, intermittently, slow uptake when typing keywords/captions etc, slowing of functionality etc. And these things also happen on my laptop. Clearly, to me anyway, it is a lightroom problem. So if you've resolved your probs by reverting to 7.2 thats great, I'm fearful that if I try to go back I'll end up with more issues. Good luck.
Photo of Renato Richina

Renato Richina

  • 11 Posts
  • 1 Reply Like
Yes definitely, 7.4 fixed mostly all 7.3.x issues for me
Photo of brian scantlebury

brian scantlebury

  • 19 Posts
  • 3 Reply Likes
Thank you. Will do. Didn't realise a update had been released. Usually automatic, but not this time it seems. Hopefully that will be great. Cheers.
Photo of Arvid Uhlig

Arvid Uhlig

  • 11 Posts
  • 1 Reply Like
7.4 didn't fix it for me.
Photo of brian scantlebury

brian scantlebury

  • 19 Posts
  • 3 Reply Likes
Agreed, not fixed by 7.4. This is frustrating and seems so wide spread, dont understand why something isn't done about it by Adobe.
Photo of Arvid Uhlig

Arvid Uhlig

  • 11 Posts
  • 1 Reply Like
Yes, it would be very nice to see some dedication from adobe to fix this problem. 

It's a very essential function, and as far as i understand it's one of the big strengths of lightroom to automate a lot of recurring tasks, like for example applying settings / profiles on import. 
But that doesn't work reliable at the moment. So please fix that fast, because it costs a lot of time to do all that stuff manually.

We are not stupid, and we did understand the mecanics behind the "default develop settings" and the "profiles"
All that worked fine for us until 7.3. 
We know that "default develop settings" are camera and ISO dependent, of course! That's the reason we use it!
And i need to use a (color correction) profile on import, because it gives me a starting point to my very own look, or the look of the current project.

Please fix this.
thanx
Photo of Alexander S. Kunz

Alexander S. Kunz

  • 48 Posts
  • 5 Reply Likes
For what it's worth, this problem HAS indeed been fixed for me in Lightroom 7.4 - I set the Develop defaults again, and they are all applied now when I import new photos, or hit "Reset".

Brian, Arvid - have you tried the "Develop" menu, "Set Default Settings...", then selecting "Restore Adobe Defaults", and THEN set your own defaults again? I didn't have to do that, but since the problem persists for you, maybe something is "stuck" somewhere, and reverting to Adobe's Defaults will help? Just an idea.
Photo of brian scantlebury

brian scantlebury

  • 19 Posts
  • 3 Reply Likes
Yes, I did that in 7.3 thanks. No improvement. The whole system has slowed a lot. Really quite frustrating, but thanks for your persistence and help.
Photo of Arvid Uhlig

Arvid Uhlig

  • 11 Posts
  • 1 Reply Like
Did that in 7.3 also, but no luck...
When i have time i‘ll also try in 7.4
But i‘m really annoyed to be the beta tester here!
This whole process really takes a lot of time, and i feel like I‘m wasting a lot of time with things that should actually just work.
And if it doesn’t work in the end i‘m even more frustrated!
Photo of brian scantlebury

brian scantlebury

  • 19 Posts
  • 3 Reply Likes
Know exactly how you feel. Most unfortunate. Makes me wonder if shouldn't look at Luminar!