Known Participant

P: Compare View on 2nd Monitor shows no image on Zoom.

Forum|Forum|2 years ago
October 10, 2023
130 replies
26079 views

After LR Classic 13.0 and update 13.0.1 Lightroom is behaving weird on my second monitor.
Before I could use the compare mode on the second monitor when in the develop module on the first without any issues.
Could zoom in and out on the comparisons.
After the update this behaves odd.

Sometimes it will zoom in and out as before but most of the time it doesn't and one of the selected pics for comparison won't even show (just black) or sometimes even zooms in at a different percentage compared to the other. This only occurs when in the Develop module.

Switching from Compare to Loupe on the second monitor sometimes won't work either - display goes black.

When I switch to the Library module on the first screen there's no issue.

I've got a very robust Windows system with 32 GB of RAM and a NVIDIA GeForce RTX 3060 Ti 8GB of RAM which before (v 12.5) just did the job without any trouble.

Seems like Adobe rushed to do this update but forgot to test it thouroughly.

Windows

This topic has been closed for replies.

Show previous replies

flemmingo27941925

Participant

i cant zoom in on my second monitor to 100 procent. it just show a small fraction of the picture and its aint solved by the latest update.

D

duriv73

Participating Frequently

And I also noticed that the quality of the image in the second window, ALWAYS IN DEVELOPMENT mode (in adaptive zoom) is bad (oversaturation, no contrast)

R

r hb88940642

Participant

I installed the update 13.02. sadly the bug is still there on my second screen in developer mode zooming in. hoping for another update taht will definitely fix it. It is an annoying bug !!

D

duriv73

Participating Frequently

A bug appeared in version 13 of LrC: 100% zoom no longer works on the second screen, ONLY IN DEVELOPMENT MODE.

More precisely, zooming to 100% is done completely off-center (bottom left), which often leads to a black window. If we try to recover the photo (by PAN), only part (bottom left) of the image (truncated) is accessible.

I temporarily reinstalled the latest V12 (which works perfectly), which proves that it is indeed a bug on V13 (including the latest version).

-Windows 10

- Intel® Core™ i7 4770 CPU @ 3.40GHz

- 8 GB RAM

-NVIDIA GeForce GTX 1080

D

dsm1212

Participating Frequently

Still happens on 13.0.2, but I wanted to add I have a bunch of older scanned images that work fine in develop second screen. Only the images from my camera are doing it. The scanned images are much lower resolution and they are not raw.

NYNC

Known Participant

Having almost exactly the same problem with LR Classic 13.01as described by davep60 on AMD Ryzen desktop system with two monitors running on GeForce RTX 3070 Ti with NVIDIA 546.01 Studio Driver (NVIDIA's latest). Click on Loupe view on second monitor in Develop mode and screen shows only grey background with a small black square in lower left hand corner. Develop module on monitor 1 zooms OK. Turn off GPU acceleration and LR behaves properly. Turn on GPU acceleration, and issue recurs. Reproducible. Clearly related to GPU acceleration with NVIDIA card. No crash reports as LR continues to run.

NYNC

Known Participant

As of today, 10/17/23, LR Classic 13.0.1 for Windows 11 X64 is still crashing.

My computer uses two monitors. In Develop mode with Develop Module on monitor 1 and Loupe view on monitor 2 and CPU acceleration enabled, double clicking on monitor 2 brings up either a black screen or just a corner of the image instead of showing a magnified view. I turned off GPU acceleration and restarted LR 13.0.1. With that, Develop module worked OK. So, I updated to the latest NVIDIA GeoForce RTX 3070 Ti graphics card drivers, restarted computer, and restarted LR 13.0.1. Got same faulty display on monitor 2 with GPU acceleration enabled. When I then disabled GPU acceleration and restarted LR 13.0.1, it failed to start. I suspect it failed to start because it failed to close properly. Three "temporary" files, including LRCatalogName.lrcat.lock, LRCatalogName.lrcat-shm, and LRCatalogName.lrcat-wal remained behind in the directory containing the LR13 catalog. Windows 11 itself wouldn't properly shut down, probably because it couldn't close those files on LR shutdown. It got stuck forever on the "Shutting Down" screen and required a hard shutdown by holding down the power button. When I rebooted, deleted those 3 files along with any other LR 13 catalog files or preview directories before starting it, LR 13.0.1 started up, again requiring that I update from the LR 12 catalog to a LR 13 catalog format. I fail to see how an Adobe Server issue would affect what happens with a local version of LR Classic. This seems to me like a problem with GPU acceleration in LR 13.0 that persists in 13.0.1. I can't afford to spend any more time losing new edits each time I have to abandon a LR 13 Catalog and restart LR13 from scratch using my old, no longer current LR 12.5 catalog. So, I rolled back to LR 12.5. It can use GPU acceleration with the newly updated display drivers. Will wait for LR 13.0.2 or perhaps 13.1 or 13.2. Regarding Rikk Flohr's comment below about clean install of LR 13, does rolling back from LR 13.0.1 to LR 12.5 do a complete uninstall of LR 13.0.1 such that when I'm ready to try LR 13.2, updating to 13.2 from LR 12.5 will be a clean install? Alternatively, do I have to update to LR 13.2, uninstall 13.2 and then reinstall 13.2 to get a clean uninstall/reinstall? Thanks.

NYNC

Known Participant

At suggestion of another member, I'm reposting this in Windows forum instead of Mac where it wound up first.

My computer uses two monitors. In Develop mode with Develop Module on monitor 1 and Loupe view on monitor 2 and GPU acceleration enabled, double clicking on monitor 2 brings up either a black screen or just a corner of the image instead of showing a magnified view. I turned off GPU acceleration and restarted LR 13.0.1. With that, Develop module worked OK. So, I updated to the latest NVIDIA GeoForce RTX 3070 Ti graphics card drivers, restarted computer, and restarted LR 13.0.1. Got same faulty display on monitor 2 with GPU acceleration enabled. When I then disabled GPU acceleration and restarted LR 13.0.1, it failed to start. I suspect it failed to start because it failed to close properly. Three "temporary" files, including MyLR13CatalogName.lrcat.lock, MyLR13CatalogName.lrcat-shm, and MyLR13CatalogName.lrcat-wal remained behind in the directory containing the LR13 catalog. Windows 11 itself wouldn't properly shut down, probably because it couldn't close those files on LR shutdown. It got stuck forever on the "Shutting Down" screen and required a hard shutdown by holding down the power button. When I rebooted, deleted those 3 files along with any other LR 13 catalog files or preview directories before starting it, LR 13.0.1 started up, again requiring that I update from the LR 12 catalog to LR 13 catalog format. I fail to see how an Adobe Server issue (mentioned in Mac post) would affect what happens with a local version of LR Classic. Although this same sequence of failure to start with those 3 files left behind occurred repeatedly before I updated Graphics drivers, it now seems to be based in a problem with GPU acceleration in LR 13.0.1. My first update was to 13.0.1. Never installed 13.0. I can't afford to spend any more time losing new edits each time I have to abandon a LR 13 Catalog and restart LR13 from scratch using my old, no longer current, LR 12.5 catalog. So, I rolled back to LR 12.5. It can use GPU acceleration with the newly updated display drivers. Will wait for LR 13.0.2 or perhaps 13.1 or 13.2. Regarding Rikk Flohr's comment in Mac forum about clean install of LR 13, does rolling back from LR 13.0.1 to LR 12.5 do a complete uninstall of LR 13.0.1 such that when I'm ready to try a mature version like LR 13.1 or 13.2, updating from LR 12.5 will be a clean install? Alternatively, do I have to update to LR 13.2, say, uninstall 13.2 and then reinstall 13.2 to get a clean uninstall/reinstall? Thanks.

johnrellis

Legend

"After my second round with support, ... I've been told "Our engineering team advised that this issue will be fixed with the new Lightroom 13.1".

That would be good news if true, but note that Adobe chat and telephone support is not trustworthy -- they often say things that aren't true.

LR releases a non-patch release on average every 8 weeks, so we might expect to see 13.1 in the next week or two. Given they just released the second patch release (13.0.2), it wouldn't be surprising if 13.1 was delayed a little bit.

D

defaultg0xz0h1s8nty

Participant

After my second round with support, spending over 3 hours total with Adobe remote controlling my machine, my case was escalated and I've been told "Our engineering team advised that this issue will be fixed with the new Lightroom 13.1".

I asked when 13.1 would be made available and was told they have no date.