Skip to main content
Inspiring
March 6, 2012

P: LR4 doesn't display point curve adjustments made in LR3

  • March 6, 2012
  • 228 replies
  • 3483 views

After updating from LR3, LR4 has reset my tone curves. I use custom tone curves on almost every picture, and all my contrast treatments this way seem to have gone. Initially the previews were still the old ones, so I only noticed after opening several pictures in the develop module, just to see my meticulous tone curve adjustments be removed.

Is anyone else seeing this?

This topic has been closed for replies.

228 replies

EdwardJohnAllen
Inspiring
March 12, 2012
Hi Tom
good to see you are taking this seriously, but can I ask if you would recommend that users who have not already upgrade catalogues wait until the core program has been altered to include the bug fix?

I just don't want to walk into a problem if there will be proper fix soon.

Please confirm

Thanks
Inspiring
March 12, 2012
Oh, I see. Just a day to late 🙂 Good luck with the fix!
Adobe Employee
March 12, 2012
Update: Those that have volunteered to help test a solution should have received an email from me earlier today with a proposed fix. I'll gather feedback on that solution and we'll then work to distribute it more widely.

Regards,
Tom Hogarty
Lightroom Product Manager
Inspiring
March 12, 2012
Honestly, I do not think this is serious, as I believe there's no permanent damage done as long as you keep your old catalog. But it is annoying and embarrassing for the guys at Adobe's. Anyway, please take your time and fix it properly. And keep us happy by updating us on the progress. Also, if you need someone to test, I volunteer.
Cheers
Henrik
Participating Frequently
March 12, 2012
@10002659 Ippers - disagree! I always write changes to xmp, but this has not had any effect on the import, unless you resave xmp in LR3 after conversion and then update from xmp in LR4.

I still think that it is something to do with the new catalog not importing default tone curve settings. If I go to my LR4 catalog and resave defaults, many of the rogue tone curves correct themselves, although some don't.

Going to do a bit more investigation today
Participating Frequently
March 11, 2012
Seriously, it's been almost a week. I bought LR4 before the weekend because I expected to be transferring files and editing my next shoot in LR4.
EdwardJohnAllen
Inspiring
March 11, 2012
Hi Tom (Hogarty)
I was also just about to do the upgrade from 3.6 Beta but am very concerned that I will give myself a big problem.

Can you confirm if Adobe are recommending that users WAIT to carry out the upgrade until this issue is resolved please?

Please also add my email edwardjohnallen@gmail.com to the list of people to be updated on this issue.

Thanks
Edward
Participating Frequently
March 10, 2012
The good thing is, that the import of the LR3 catalog into LR4 doesn't modify the LR3 catalog. You just have to check the pictures you selected in LR4 after the import and take a look in LR3 if any settings were modified by LR4. I have read Chris' post very early so I was able to prevent LR4 from modifying my metadata.

I can understand Adobe. They want to keep their product safe. But... then I expect some faster reaction to such critical bugs.

I bought a product and can't use it. If it would be a car, that car would have been taken back to the car dealer. No matter if the product is cheap or established compared to others. It's a matter of trust.
Inspiring
March 10, 2012
You did not use your LR3-xmp, when you upgraded the catalog by LR4.
That just converted the LR3-catalog recoreds into LR4-catalog records, with the exception of the tone curve settings. Which why there is now a default value in, no matter which PV.

My statement is correct. But I would not consider it safe.
My best advice is: cherish your last LR3-catalog version and go to LR3 if you need something from it.
Use LR4 only for new imports, if at all.

I share your frustration. Especially Adobe's approach to their friendly supportive beta-testing community: why did they have to shut them out of catalog-upgrade testing?! This is arrogance.
And now all customers pay for it.
Inspiring
March 10, 2012
Just wait for Adobe to provide a solution, as Tom said above.