P: Library zoomed view shows wrong color

Happening to me on my 2019 MacBook Pro 16", running Big Sur. This happens whether I use the stock ICC profile or my ICC profiles generated with X-Rite i1 Display Pro Plus. It happens on the MacBook display, as well as external display. It happens whether the external display is connected or not. It happens whether GPU acceleration is enabled or not. I couldn't find any workaround. Also, this never happened with previous versions of Lightroom.

I also want to point out that this bug exists in the Print panel as well, and it shows up when the option "Zoom to Fill" is selected.

Same issue here.
MacBook Pro (15-inch, 2018), Big Sur (11.1) and Lightroom 10.1.1.

When zooming into a picture in Library module Color profile seems to change into a much more flatten one.
That's not happening on Develop module.

Waiting for a bug fix on that...

I am experiencing this same issue exactly, after recently updating to Big Sur 11.1 and LR 10.1.1. I have never had this issue before and like others it is in Library mode only. The colour shift is a pretty significant shift towards green when zoomed in to an image - it does not happen in Develop mode. I use a 27" iMac Retina 5k 2017. I really hope Adobe can fix this bug soon!

Rare bug??? I

Yes, do you know what the words rare and bug mean? 

You don't know the installed base of the product or the number of pre-release users who never encountered this rare bug. 

It is NOT present on ALL Big Sur Macs with wide gamut displays; I have seen no such bug here at any time. Nor did anyone using the same kinds of hardware when conducting beta. Those are the facts. 

Again, I'm sorry the facts and this rare bug have affected you but since you've provided zero reporting of specifics about your system and hardware, you'll continue to see this bug until you decide to step up and aid in the fix instead of just complaining and wasting so much of your time and that of others. 

It is in no way rare!

Do tell us then the number of installed systems that exhibit this specific bug; the floor is yours again to assume. 😉

@andrew_rodney Rare bug??? I just did a clean reinstall of Big Sur on 2019 MacBook Pro 16 and the bug is there all right. It is present on ALL Big Sur Macs with wide gamut displays with the latest LR Classic. It is in no way rare!

Andrew, I think it would be best if you stepped away from this forum.

Request denied.

Rick has stated that he has successfully replicated this bug.

Because a bug exists and no one has said otherwise. This bug doesn't affect everyone by a long shot. Now why is that, and what can those who are affected do?

1. Report the issue and ALL system info. 

Useful. 

2. Bitch and complain. 

Not useful.

Stop getting emotionally involved.

Stop assuming. Please! 

Dear experts and friends of LR, 

why is it so difficult to listen to users and accept that they have a problem which for at least some of them significantly impacts workflow. Luckily I am using LR just for non-professional use. I have followed very closely every update and version since LR2 and suffered from another bug in the Library Preview (banding artifacts) since quite a while which was never accepted although reported many times. Surprisingly that bug was fixed and replaced with this new color rendering bug. The new color rendering bug had never been in LR Classic before (starting from LR2). This new bug is unfortunately more annoying since it is obvious in many more images, likely happening always, but for some images more prominent than others. It was reproduced by many of us using different cameras and display profiles. How can some of you claim these issues are tiny, or extremely rare even if they don't see the issue on their system.  Mistrust? Do you assume we provide hours of time complaining just for fun? How many example images do you want to get from us? If you don't want to listen, why do you do? I still hope and assume that Adobe wants to listen and that this is the reason to host this user forum. Otherwise, simply stop doing so. Then users stop complaining and save time. We are spending efforts (not to forget the monthly fee) hoping we can influence some decisions to fix bugs. We appreciate Adobe's commitment to further support LR Classic and accept that major parts of the team needs to focus an architectural rework to get LR up and running on new processors. What drives us nuts is to get ignored, or worse, being rewarded as stupid users who just want to complain for whatever reason. 

I can only speak for me, but I still like the LR Classic concept and want to continue using it. Personally I already got much more functionality than I need and would appreciate a consistently stable and state of the art performing LR.

I am leaving  this thread now. Not worth spending more time I fear.  Keeping fingers crossed that it will be fixed sooner than later.

Andrew, I think it would be best if you stepped away from this forum. As a tester, you are not really doing much to help with Adobe's image. You gave your two cents (that neither you nor the other testers encountered this bug, something which I assume is true of virtually every bug that ever ships with a product), and since then have added little except to antagonise already frustrated customers.

Rick has stated that he has successfully replicated this bug. Stop getting emotionally involved.

 You filed a bug just now??? The bug has been there for WEEKs, VERY obvious after a couple of clicks in any standard LR Classic workflow. Are you kidding us???

Engineering has been aware of this for weeks and weeks, that Rick stated he too has reported this isn't anything new really.

This is a very complicated, rare and difficult bug to knock down, like  Covid-19, at some point, it will be fully addressed and doing anything here but providing specifics as to the system hardware and software used on your specific system does nothing to aid Adobe in the fix. Want to help? Complain a bit less, inform Adobe a bit more of the specifics of what's causing this rare bug. 

The fact is that you are an N of ONE

None of the pre-release testers reported this bug, no one in Adobe Engineering did either. 

The fact is that you are an N of ONE too. 

You seem to falsely and with no data, believe there is this preview bug that affects all users, or all users on Macs etc. That is simply not true or factual. 

I have LR5 installed. It behaves on my system just as LR10 does with previews in Library. No bug here. Fact. 

Do you have any idea at all what the installed based of LR 10 is? Or the number of pre-release users who tested LR 10? No you do not. Yet you believe everyone suffers from this bug, that isn't true by a long shot. 

IF you want help or verification of a bug, instead of assuming so often, maybe get down to the bottom of your specific hardware and software to aid Adobe in fixing a rare bug you happen to have that many others don't. 

Or you can just complain as is so  often in the forums where users can do nothing else! 

“If you spend five minutes complaining, you have just wasted five minutes.” Anonymous