Skip to main content
Kaugummi!Kauer
Participating Frequently
October 19, 2018
Answered

GPU acceleration only affects the library module, but not the development module

  • October 19, 2018
  • 2 replies
  • 835 views

Hello friends,

It seems to me that GPU acceleration only affects the library module, but not the development module.

This is demonstrated by the fact that when GPU acceleration is turned on, the images in the Library module are finely rasterized, in the Develop module they are roughly rasterized. This makes image processing very difficult.

If I switch off the graphics processor acceleration in LR, the images in both modules are roughly rasterized. If I switch on the graphics processor acceleration again, then it is as described above.

I am of the opinion that this is only the case since an update in LR. I have been working with LR V5 for years, I never noticed this behavior. Now with the installation of LR Classic CC it is like that from the beginning.

My graphics card is a NVIDIA GeForce GT710. This is not in the list of recommended graphics cards. But it worked very well under LR5 (finely rasterized images in both modules). I need a passively cooled graphics card.

Do you have any idea why that might be? I have installed the latest drivers from the NVIDIA site.

My configuration: Win10Pro 64bit; NVIDIA GeForce GT710, driver V416.34; Lightroom Classic CC, V8.0; Camera Raw 11.0

Best regards

  Marcus

This topic has been closed for replies.
Correct answer dj_paige

marcusk29492084  wrote

Hello friends,

It seems to me that GPU acceleration only affects the library module, but not the development module.

This is demonstrated by the fact that when GPU acceleration is turned on, the images in the Library module are finely rasterized, in the Develop module they are roughly rasterized. This makes image processing very difficult.

If I switch off the graphics processor acceleration in LR, the images in both modules are roughly rasterized. If I switch on the graphics processor acceleration again, then it is as described above.

I am of the opinion that this is only the case since an update in LR. I have been working with LR V5 for years, I never noticed this behavior. Now with the installation of LR Classic CC it is like that from the beginning.

The problem with this logic is that no other Lightroom user is experiencing this, and so the most likely cause is something else. Or perhaps it is the GPU driver (and not Lightroom) that is the problem.

Can you show us screen captures so we can see the problem? We would need to see a screen capture of what the photo looks like in the Library module and we would need to see a screen capture of what the photo looks like in the Develop Module.

2 replies

Legend
October 19, 2018

This may be a problem with the ver 416.x drivers from nVidia?

There have been reports of LR slowdowns when these drivers are in use combined with LR8 but works better with driver ver 411.x

Kaugummi!Kauer
Participating Frequently
October 19, 2018

Yeah, that's what I was thinking. Therefore I also tested older drivers.

But then the representation of the pictures in both modules would have to be equally bad.

Now the image in the library module is displayed in good quality, so the graphics card is able to display the image with maximum quality.

Only in the Develop module the quality is poor.

There are 2 versions of the 411.x drivers. I will test both and give feedback about the result.

dj_paige
dj_paigeCorrect answer
Legend
October 19, 2018

marcusk29492084  wrote

Hello friends,

It seems to me that GPU acceleration only affects the library module, but not the development module.

This is demonstrated by the fact that when GPU acceleration is turned on, the images in the Library module are finely rasterized, in the Develop module they are roughly rasterized. This makes image processing very difficult.

If I switch off the graphics processor acceleration in LR, the images in both modules are roughly rasterized. If I switch on the graphics processor acceleration again, then it is as described above.

I am of the opinion that this is only the case since an update in LR. I have been working with LR V5 for years, I never noticed this behavior. Now with the installation of LR Classic CC it is like that from the beginning.

The problem with this logic is that no other Lightroom user is experiencing this, and so the most likely cause is something else. Or perhaps it is the GPU driver (and not Lightroom) that is the problem.

Can you show us screen captures so we can see the problem? We would need to see a screen capture of what the photo looks like in the Library module and we would need to see a screen capture of what the photo looks like in the Develop Module.

Kaugummi!Kauer
Participating Frequently
October 19, 2018

I also thougt that it depends on the graphics driver. So I've tried different things to fix that:

de-installing my graphics card and using the online graphics chip (Intel HD Graphicvs 4600): image in both modules rough rasterized

installing the GT710 without drivers from NVIDIA (drivers provided by OS): image in both modules rough rasterized

installing drivers V382.33 from NVIDIA Homepage: library fine rasterized, develop rough rasterized

installing latest drivers V416.34 from NVIDIA Homepage: library fine rasterized, develop rough rasterized

The screen captures are part of a license plate; left in library module, right in develop module. Both maximum zoom.

I use Original & Smart-Preview. Standard Preview Size set to Auto (2560px), Preview Quality High.

Thanks for your help

dj_paige
Legend
October 19, 2018

marcusk29492084  wrote

The screen captures are part of a license plate; left in library module, right in develop module. Both maximum zoom.

Probably, we need to see the views of this image at 1:1 zoom and not at maximum zoom, which really isn't something you want to use to judge quality, I would use maximum zoom only if I was trying to modify the image locally in the area near a boundary.

Also, do not use Smart Previews here.

So, let's see that before we conclude there is a quality difference here. Library and Develop don't have to match in the fine details in some instances.