anders_sorensen_6378269's profile

21 Messages

 • 

782 Points

Thu, Nov 9, 2017 4:17 PM

Lightroom Classic: Zooming very large images shows grey box

I am using lightroom Classic CC 7.0.1 and Camera Raw 10.0. Is there a limit to how large a file can be and still be able to create a 1:1 preview?  I have a 16 bit TIFF that is 26246 x 2899 pixels.  When I try to view it at 1:1 or any other size except "Fit" in the Library module, it refuses to draw (Fill works so long as I don't try 1:1 first).  I just see a grey box. I can view it in any size in the Develop module or Photoshop, but not the Library module.  Does the Library module have a size limit, and if so, what is it?  I also checked the Task Manager and it showed the CPU and disk had little or no activity, and memory was using 15GB which is not unusual on my system. I have 3.67 Terabytes of unused disk space. I have an i7 6700K processor running at 4.00GHz and 32GB of DDR4 Sdram memory and Windows 10 version 1703.

Responses

Champion

 • 

2.4K Messages

 • 

39.1K Points

4 y ago

I'm seeing the same behavior using LR Classic on Windows 7. See this post: https://forums.adobe.com/message/9956218#9956218

Champion

 • 

6K Messages

 • 

103.6K Points

4 y ago

I observe the same behavior with a 20K x 13K PSD (260 megapixels) on LR CC 7.0.1 / Windows 10 running in a virtual machine, but only if I repeatedly and quickly click between Fit, Fill, 1:1, and 1:8.

On MacOS 10.12.6, I don't see the grey box, but I do get a huge virtual-memory leak after a minute or so of such clicking in Library Loupe:



Do you see a similar increase in virtual memory in Windows Task Manager? It may be that an allocation of virtual memory is failing on Windows, causing the grey box.

Champion

 • 

2.4K Messages

 • 

39.1K Points

4 y ago

John, I don't think it has anything to do with memory. A 10000x10000 (100 megapixels) file and 16000x2000 (32 Megapixels) file render at 1:1 Zoom view with  no issues, but a 16500x2000 (33 megapixels) file shows nothing in the Loupe with 9.1 GB memory available. Weird!

21 Messages

 • 

782 Points

4 y ago

I have trouble the first time I try it.  I  have tried closing Lightroom and then reopening it and still had the problem right away.

Champion

 • 

6K Messages

 • 

103.6K Points

4 y ago

" I don't think it has anything to do with memory."

It may have something to do with virtual memory.  As I described on Mac, I can pretty quickly get LR to allocate 62 GB of virtual memory before MacOS warns me it's run out.   LR isn't actually reading or writing this memory, since on a machine with 16 GB of physical memory, that would take a very long time, with lots of paging to and from disk.

My hypothesis: LR is incorrectly requesting that the operating system reserve very large blocks of virtual memory, but LR isn't actually using that virtual memory (not writing into it or reading from it). Maybe LR is getting an error from Windows when it requests more virtual memory and shows the grey box as a result.

It's been years since I read about Windows virtual memory, but I (very) vaguely recall that Task Manager may not show such reserved virtual memory until it is actually touched by the program.

Here's what the memory situation looks like on Mac:

Champion

 • 

2.4K Messages

 • 

39.1K Points

4 y ago

Virtual memory is showing at ~0.5% usage with 12GB system memory and the Windows 7 Page File set to 12.5GB.

DirectX support was added in LR Classic and causing many different screen rendering issues. Perhaps this is another one caused by DirectX incompatibility. I used the below procedure (#2) to force LR Classic to use OpenGL and not DirectX, but the blank preview screen is still present with the 16500x2000 image file at 1:1 Zoom view with Use Graphics Processor checked or uncheked.

https://helpx.adobe.com/lightroom/kb/crash-gpu-directx-enabled.html

Do you see the same 1:1 rendering issue using a 16500x2000 image file?

21 Messages

 • 

782 Points

4 y ago

My image is much smaller than the stated limit, but will not draw in the Library module, but it will in the Develop module.  My machine does not show any use of the virtual memory.  One interesting possible explanation may be that it has something to do with the graphics card.  Adobe documentation states that only the Develop module uses the graphics card for GPU acceleration.  So, there is a difference between how the library module renders images and how the Develop module does it, and how the GPU is used.

Champion

 • 

2.4K Messages

 • 

39.1K Points

4 y ago

That's true, but if 'Use Graphics Processor' in LR Preferences is unchecked the Library and Develop modules should use the same rendering and display path. Unfortunately doing that doesn't "fix" this 1:1 Preview rendering issue. Adobe added DirectX support in LR Classic, which may be the root cause of this issue. I found a similar issue at the below post, which is now marked 'In Progress' so Adobe is aware of the issue and working on a solution.

https://feedback.photoshop.com/photoshop_family/topics/lr-classic-noise-reduction-effect-not-display...

9 Messages

 • 

186 Points

3 y ago

This reply was created from a merged topic originally titled LR Classic: Large files not displaying 1:1 in Library module..

Lightroom CC Classic 7.1 [1148620], Win 10 Pro, Nvidia GTX 1050 [23.21.13.9077]. With GPU enabled, some very large images will not display 1:1 in the main window. They will display 1:1 in window 2 Loupe. They will display in Develop module. Turning off GPU acceleration resolves the problem. I have tried switching color monitor profiles to sRGB without effect.

1 Message

 • 

62 Points

3 y ago

For what it's worth, I've just tried disabling GPU acceleration and it didn't solve my problem. Running Classic CC release 7.5 with Camera RAW 10.5.

Champion

 • 

2.4K Messages

 • 

39.1K Points

2 y ago

Since this issue hasn't been addressed (i.e. fixed) by Adobe I started looking at alternatives.

It appears the LR Preview is limited to ~16,384 pixels (2 to the 14th power) long Edge dimension with 16,385 failing. I have numerous LR Panorama DNG files that are longer than this dimension and I certainly don't need that much resolution for most of my usage. If you're shooting panoramas with a 50+ Mp camera it's very unlikely you will need the full-resolution panorama merge DNG file.  I happened to fall on an old post discussing how to reduce the size of these large DNG files. https://forums.adobe.com/message/10254121#10254121

Use the below LR Export module settings to covert large panorama DNG files into resized lossy DNG files that are 1:1 view enabled. Using even a very wide 1:5 aspect ratio panorama the dimensions will be 3250 x 61250 (52 Mp), which is capable of creating a 300dpi 10.8" x 54" print. I converted a large 17844 x 3806 panorama using the below settings to 16250 x 3466. Next I exported the original DNG file to TIFF 16 bit ProPhoto RGB format with Resize to 16250 Long Edge and Screen Low Sharpening. At 1:1 or even 2:1 view there is no visible difference in the image quality between the loss-less TIFF export file and the resized lossy DNG file. Even the fine gradient sky areas are identical with no banding observed.

Below is a comparison of file sizes. The Resized Lossy DNG file is slightly smaller than a same size 80 Quality JPEG Export file. I'm not sure what type of compression is used for the lossy DNG file, but they also look identical.

Having said all this it still begs the question why Adobe hasn't fixed this issue since it was working in earlier versions (pre LR Classic).





Champion

 • 

2.4K Messages

 • 

39.1K Points

2 y ago

Thinking about this some more I wondered if the reduced-size Lossy DNG could be used to sync editing settings back to the original full-size LR panorama DNG.

To test this I used the original 17523 x 3906 panorama DNG file to create a lossy DNG file with Long Edge 7856. This is less than 1/2 the original resolution to see if resizing affects the Develop setting sync. I applied EVERY Global and Local setting available in LR (except Red Eye Correction) to the 7856 x 1706 Lossy DNG and then synced it to the original DNG file with no settings applied. The results are identical when viewed at any zoom size.

This allows using the much smaller file size lossy DNG as a settings archive. It also acts as a Smart Preview if you set 'Resize to Fit' at 10000 px or less when creating the lossy DNG. This will improve editing performance without having to enable the global Preferences setting 'Use Smart Previews instead of Originals for image editing.' Make sure to stack the original raw files with the lossy DNG copy, which I always do anyhow. If at a later date you need a full-size copy of the panorama rebuild it using the stacked raw files and then Sync All of the settings from the lossy DNG to the resurrected full-size DNG file. Done!

I hope someone finds this useful. Thank you.



380 Messages

 • 

6.7K Points

2 y ago

This reply was created from a merged topic originally titled Large dng pano not rendering at 1:1 zoom in Lr 9.1 Classic Library module.

I have a very large pano made in Lr from 19 vertically shot raw images from a Nikon D90 camera. In the Library module of Lr 9.1 Classic with Loupe View, this is what I see:



Clicking to zoom in at 1:1 view I get a very low res image while Lr is loading:



Once loaded, the image area goes grey - 1:1 image view is not rendered:



Zooming back out to Fit View briefly flashes the low res image, then the image is displayed as normal, like the first screen shot above. Clicking to zoom in again at 1:1, first gives a grey outlined box:



before again showing a grey image area like the third screen shot shown above.

In the Develop module, zooming to 1:1 view works as expected.


Employee

 • 

1.7K Messages

 • 

32.4K Points

2 y ago

Try temporarily turn off the GPU acceleration from Lightroom>Edit>Preferences>Performance to see if it helps. There might be a GPU RAM/driver limit.

In general Lightroom has a hard maximum image size limit of 65000 px on the long edge or a maximum total of 512 mega pixels, whichever comes first.

380 Messages

 • 

6.7K Points

2 y ago

Surely it can’t take more than 2 years to fix this? Come on Lightroom development team, lift your game. I've been developing software in one form or another for more than 40 years and you don't ask the user to fault find or troubleshoot for you. You take the issue onboard, do your own testing, track down the problem and fix it. The developer debugs their own software, not the paying user. There seems to be some sort of in-house aversion to fixing problems in Lightroom, much to the annoyance of the Lr's customers.