Skip to main content
Known Participant
February 15, 2020
Question

Lightroom 9.2 Update

  • February 15, 2020
  • 4 replies
  • 384 views

I need to say this update is a disappointment. Prior to this release, for years, I have been using develop presets by camera by iso. They worked great.  With the release of L'room 9.2 puff they are now usless and no longer work.

Adobe has now given us the opportunity,  to learn how to write code in xmp files in order to get back our develop presets by iso.

Who thought of doing this?

Could Adobe not have made the new way an option and let the old way continue?

Could they have offered a wizard to create develop presets in 9.2 so we can get back our delevop presets by ISO?

Could they made a sample available that we could edit for our own particulary camera?

Of course they could have done all of the above, but they didn't even offer decent instructions.

Dear Adobe , I want to spend my time doing photogrpahy not learning how to write code in XMP files.

 

Please take a step back, soon,  and try to figure out how to fix this mess created by 9.2 and then please communicate it to  your customers.

 

This topic has been closed for replies.

4 replies

johnrellis
Legend
February 16, 2020

"John the link you supplied doesn't work. I managed to figure it out and reposted to feedback"

 

Good. The stupid new forum software sometimes appends a blank to copy/pasted URLs (which I've also reported to Adobe).

Tony_See
Inspiring
February 16, 2020

Tony_See
Inspiring
February 16, 2020

This pretty frustrating for you NormU . . .

Can you go back a version using the Adobe creative Cloud desktop app?

johnrellis
Legend
February 16, 2020

Adobe wants all product feedback in the official Adobe feedback forum:

https://feedback.photoshop.com/photoshop_family/categories/photoshop_family_photoshop_lightroom 

 

Product developers read everything posted there but rarely participate in this forum (which is primarily user-to-user).

NormUAuthor
Known Participant
February 16, 2020

John the link you supplied doesn't work

I managed to figure it out and reposted to feedback