Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

M2 Max + LRC + external monitor + Develop module = FLICKER

Community Beginner ,
Feb 05, 2023 Feb 05, 2023

Hi!
I took delivery the other day of a brand new Macbook Pro with M2 Max chip (38-core GPU) and experience so much flicker for LRC to be unusuable. This only occurs with my external monitor attached.

 

More details:
* This was a directly replacement of my M1 Max Macbook Pro (which had fewer GPU cores, less RAM);

* Fresh MacOS install (13.2);

* Same data/LR catalog (LRC 12.1);

* Apple Pro XDR display (latest firmware);

* Preferences > Performance > Camera Raw / Use Graphics Processor = Auto.

 

The flicker presents as if a new color profile is being applied on and off, every time I move the mouse in the Development module. It appears as if a new white balance is applied (the white balance doesn't actually change — it just has the same screen effect as if WB is changing). This makes the program unusuable for any editing. 

 

True Tone and Automatic brightness adjustments are both off, as is Night Shift.

 

If I turn this GPU usage to off within LRC, the flickering is gone — but the program slows SIGNIFICANTLY. If turn to this setting to "Custom", "GPU for Display is the most basic setting", and I have to shut it off for LRC to work properly.

 

Has anyone experienced this? Some web searches revealed M1 (and M2) users had flickering with BenQ monitors. I realize I'm one of the early ones with an M2 Max.

 

Any thoughts?

Booting into Safe Mode had no impact. Same external monitor, cables (Thunderbolt), data, etc., with my old M1 Max MBP and the new M2 Max MBP.

 

Thanks for any leads.

 

TOPICS
macOS
6.5K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Aug 30, 2023 Aug 30, 2023

The test reference image I was thinking of is the top image on this page: https://www.redrivercatalog.com/infocenter/printing-test-images-files.html

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Oct 19, 2023 Oct 19, 2023

This issue is still occuring on the latest update. LRC 13.01 with a MacBook Pro 14" M2 Max Chip using an external Apple Pro Display XDR. Is there any fix in the works?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 19, 2023 Oct 19, 2023

Yes, I still experience it.

As an aside, the latest update broke my ability to hit ESC to exit out of the mask window. I now have to scroll down and press Close with the mouse. Wish there was a way to get that capability back. It's a minor thing but one I encounter frequently. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 08, 2023 Nov 08, 2023

Having same issue on brand new M3 Max MacBook Pro. Keeping screen brightness "2 clicks below full" also seems to fix it.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 08, 2023 Nov 08, 2023

Ah, thank you for checking in. 

I was wondering what would happen; my M3 Max has not yet arrived.

I suspect it will be the same issue regardless, but what configuration of the M3 do you have? 14-core or 16-core?

My M2 Max where I reported the above issue is the 12-core — though I saw the behavior on other M2s I had in my possession (including M2 Pro). My M3 Max is the 16-core version.

At least we have the workaround I identified.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 08, 2023 Nov 08, 2023

16-core CPU, 40-core GPU.

 

Thanks for finding the workaround - I was starting to pull my hair out.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 20, 2023 Nov 20, 2023

I experince the same issue with an new Max Book Pro M3 Max.
Thanks for the work around!
Is there a chance that Adobe will fix this bug, since the first report is 6 month ago ? 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 12, 2023 Dec 12, 2023

This issue occurs for me on a Mac Studio with M2 Ultra. Connected directly to this is a Pro Display XDR and two Apple Studio Displays. The flickers occurs on the top 2 brightness levels, on any of the displays.

 

I do not experiene this issue on my M1 Max MacBook Pro using the internal display.

 

If I use an app like Vidid to trick the system and boost the Pro Display XDR brightness, then I can get around this issue when editing photos in a bright room. But still, this is a very annoying issue.

 

Also, I do not see this issue when editing on a Windows 11 PC with an RTX 4090 and real HDR display either.

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 28, 2024 May 28, 2024

Just wanted to add my experience of how annoying this is. I've been using an M3 Max (non-binned) for the last 6 months with the Pro Display XDR and have had to go into the P3 reference mode to avoid the problem - essentially rendering all the HDR goodness of screen useless. I'd given up until I read this thread and saw the 2 clicks down from max brightness trick, so thanks for that!

 

Its amazing that Adobe has still not fixed the issue. I thought it was just a problem with the M3 MBPs (possibly caused by the 600 nits SDR vs the 500 nits SDR of the Pro Display XDR) as my older M1 Pro never had any issues. Sounds like I just got lucky with that though. I was actually pretty happy with the 600/500 nits theory and it also fits with the need to reduce the brightness slightly on the XDR if Lightroom is trying to push 600 nits but the display doesn't want to... but if people are having issues on M2 machines then sounds like that's not it! 

 

Will use the 2 clicks method for now but its really frustrating to spend £5k on a display and have to not use all of its performance because of a long term bug in LRCC that Adobe seemingly can't be bothered to fix...

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 28, 2024 May 28, 2024

If you had taken the time to read the thread and did some Google searches, then you'd find that the issue is not Adobe's to fix. The issue is for Apple to fix, although  hwo when they fix is another matter. In the meantime, you may find this article by the Developers of Better Display informative https://github.com/waydabber/BetterDisplay/wiki/Eye-care:-prevent-PWM-and-or-temporal-dithering

 

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 28, 2024 May 28, 2024

I actually did take the time to read the thread 🙂 If you'd taken the time to read the replies from ericb14197638 and johndebay on 29 August 2023, you'd find that the issue isn't anything to do with PWM or Temporal Dithering. I have the exact same issue as those users which is clearly isolated to the viewer in LR, where the image changes brightness every few seconds (notably not the UI or rest of the screen). I've not seen this behaviour in any other app, at any point in my 15 years of using OSX with external displays. It therefore seems likely to me that its an Adobe issue.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 25, 2024 Nov 25, 2024

Quick update:

After experiencing this with my M1 Max, M2 Max and M3 Max, I notice I no longer experience the Develop module display flickering with my M4 Max.

 

I can't speak to whether it is solved with every model/combination. Here is mine:

* 14" MBP with M4 Max chip (16c/40c/128GB)

* MacOS 15.1.1

* LR Classic 14.0.1

* Apple Pro Display XDR (hasn't changed)

 

While I rarely do it, I can now go full brightness (or 1 step below) and use the Develop module without flicker.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 25, 2024 Nov 25, 2024
LATEST

When I updated to the new Sequoia version of macOS, it fixed the issue. I can now be on any of my Macs (M2 Ultra Mac Studio with Pro Display XDR, or M4 Mac Macbook Pro) and use the Develop module at full brightness. Previously the Develop module would flicker at full brightness so I always went Full Brightness minus 2 ticks down. Annoying, but apparently resolved.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines