P: Compare after soft proofing shows only edited version

[Giovanni Stoto]

I think I found a bug in LrC when soft proofing.

Typically when you edit a picture and then hit the compare button, you are shown on the left the original picture and on the right the edited picture, like on the top part of the following screenshot.

But if you do soft proofing this comparison is broken, as you can see in the bottom part of the following screenshot, where I am being presented left and right with the same edited photo.

Steps to reproduce:

1- Click on soft proof
2- Click on create proof copy
3- Click on compare button  Before/After Button (Compare is a Library Feature)
4- Click on single photo to show only edited picture
5- Remove proof copy (only from LrC)
6- Click on compare > l  Before/After Button (Compare is a Library Feature)

Result:
Left edited phot and right edited photo

Expected:
Left is unedited/Right is edited

Reproduction was done on version 14.5.1 

Mod Comments in Bold

[ShootingPixelsAndy]

Yep, it's broken. Once you've created a soft proof copy LrC gets confused about the "edited state" of the original image. Even a reset or reverting to the import history step won't convinvce LrC to show the correct before state.

[Giovanni Stoto]

Thx... Another bug that will take ages to be fixed 

[Giovanni Stoto]

What's funny is that, like the ! bug, I have reported this under BUG but Adobe has moved this under DISCUSSION.
Luckily after Adobe realised the ! was really a bug and moved it back to BUGS

[ShootingPixelsAndy]

Wouldn't it be wonderful if the only people who could post in bugs were the mods? Would save a lot of frustration and improve the experience for Adobe's customers.

Maybe Adobe will add an AI that automatically decides where posts should go - oh wait, would that use up our AI credits?

[Giovanni Stoto]

I am an IT Services Owner, Service Manager and Delivery Manager with 28 years experience: any solution in this cases has pros and cons, there's no silver bullet.

End users must have a way to submit bugs, the problem is that someone at Adobe must verify them and confirm if actually a bug or not, in the former case open an INC internally.

[ShootingPixelsAndy]

Sure, but if any new posts from users in bugs are moved to discussion by the mods only to be moved back when confirmed as bugs why not start everything in discussion and cut down on the work for the mods and frustration for the users? I've got nearly 40 years in development, started with games on 8bit computers!

Edit to add context - By default any new posts in bugs are moved to discussion and stay there until they are confirmed as bugs.

[Giovanni Stoto]

Apologies my comment was not to put up a competence war 🙂 just to say I know the subject, as you do its eems 🙂

Adobe must consider we are paying customers, so I do expect to have a dedicated path for bugs, which must stay as bug untill confirmed otherwise. I have plenty of tickets that my partners open on us that are not issues (either due to temporary downs or to bugs): we still evaluate each one of them and reject those that are not issues. 

[JohanElzenga]

Sure, but if any new posts from users in bugs are moved to discussion by the mods only to be moved back when confirmed as bugs why not start everything in discussion and cut down on the work for the mods and frustration for the users? I've got nearly 40 years in development, started with games on 8bit computers!

Edit to add context - By default any new posts in bugs are moved to discussion and stay there until they are confirmed as bugs.

By @ShootingPixelsAndy

I asked that to Rikk some time ago, because so many people think that a 'bug' is just a fancy word for any software problem, and so they'll post in the "Bugs" forum about problems that are clearly not bugs (in a typical group of reported bugs, only about 3 out of 25 bugs reported turn out to be actual bugs). The answer is that it is apparently not possible to block people from posting a new thread, if you want to allow them to add their experience to an existing thread. The forum software has no provision for making this distinction.

[Rikk Flohr: Photography]

Regarding this specific thread: 

• No Lightroom Version number was supplied.
• The instructions provided did not lead to repetition of the reported behavior. 

Either of those reasons would have been sufficient to move the reported bug to discussions.

I highly recommend reading: How to write a bug report. and Shoud I post in Bugs or Discussions?

Both of these are pinned to the top of the Bug reporting page and contain valuable information for successful bug reporting. 

I suspect there are missing steps in your reproduction instructions as you seem to be moving between Library and Develop without mentioning how. (Example: Soft Proof is in Develop and Compare view is in Library)

If you want to attempt to create more complete reproducible instructions, I think the team would be happy to take another look.  Meanwhile, in Discussions, it will have 10X the number of eyes on it. 

[Giovanni Stoto]

In Adobe probably don't know ITIL, don't know the difference between issue and problem management and shouldn't even give end user the possibility to submit a bug.

An end user has an issue, the issue is reported to Adobe thru a flow different from help/suggestions, the issue is analysed and there could be two options: it's not a problem and a solution is given to end user, it's a problem and the root cause must be analysed. The problem 's root cause may be a bug, but not necessarily.

[ShootingPixelsAndy]

I managed to follow the steps and see the bug but I realised that "compare" meant the before after view in develop.

[Giovanni Stoto]

@Rikk Flohr: Photography Version Is irrelevant because I've had this problem also in the past, but yesterday it happened again so I thought it was time to submit.

No one has ever mentioned Library module: soft proofing is possible only in Develop so it's implicit all steps are done in Develop.

Others here could reproduce and before submitting I had already confirm this with others offline.

I will submit a screen recording showing the problem.

BTW: I've had this same argument for the ! Problem that eventually was confirmed to be a bug, yet after two months has not been solved yet.

[Giovanni Stoto]

@Rikk Flohr: Photography  >>> https://photos.app.goo.gl/XNtsSdvuuxMPArH5A

Hope this is enough.
BTW, as @shootit said: if you RESET the edited picture and click on compare again, as BEFORE you will see the soft proofing copy and as AFTER the original version.

In addition

[Rikk Flohr: Photography]

Thank you @ShootingPixelsAndy for your comment. It enabled me to understand the wrong information provided in the OP.

@Giovanni Stoto  I've corrected your bug report with the information required and altered your steps to be accurate in reproducing the bug.  I've marked those corrections in bold. 

I've logged this with the team.

Thank you for the report. 

[Giovanni Stoto]

@Rikk Flohr: Photography no problem 🙂 and yes apologies for using compare instead of before/after

[Bob Somrak]

There are a couple other operations that replace Before in Before/After.  

One of them is "Read Metadata from File". Its been this way forever so probably as designed but still annoying.

[soujo1]

I am experiencing the same problem.
In my case, I didn't even create a proof copy.
My steps are:

1. Turn on Soft Proofing
2. While in Soft Proofing view, I attempt to make an edit (e.g. change the exposure)
3. A warning dialogue box comes up, asking if I want to A. Undo; B. Make This A Proof; C. Create Proof Copy
4. I think "oops" and choose "Undo"
5. After that, whenever I do a Before/After comparison, the "Before" image is the edited version that I viewed in Soft Proofing, NOT the original unedited image (which is what I want)

Using Adobe Lightroom Classic 14.5

[Giovanni Stoto]

@Rikk Flohr: Photography has this been confirmed to be a bug and is someone working on this?

[Rikk Flohr: Photography]

@Giovanni Stoto please read the pinned post in this thread. It contains up-to-date information. 

[Giovanni Stoto]

 I had alread read that, but since today v15 has been released was wondering if this was fixed, although im doubt.

It seems that this bug instead (https://community.adobe.com/t5/lightroom-classic-bugs/p-v14-5-lightroom-has-encountered-problems-rea...) wqas fixed, so tehre may still be hope 🙂

[ShootingPixelsAndy]

@Giovanni Stoto  v15 is released? 

[Giovanni Stoto]

I got it today, like every version for whatever reason I get it a few days in advance 🤷🏻‍:male_sign: