LR Classic very slow to boot (then performs normally)

Explorer ,
Jun 03, 2019

Copy link to clipboard

Copied

Hi everyone, firstly thanks in advance for any help.

I have Lightroom Classic, on the latest version. Running on a late 2013 Imac 27" which has 16GB of RAM.

I am a photographer and use my Mac for pretty much only LR/PS and the odd web browsing.

I store my photos on an external USB drive which my current one is only 1.2TB used out of 4TB.

My Mac is only using 400GB of its internal 1TB fusion drive.

Recently my LR can take 5minutes+ to fully start up and allow my photos to appear in library/development. Once it has finally loaded everything it is quick and snappy to use and navigate around. This only occurs on the first startup after booting up, if I "Quit Lightroom Classic' and then open it again its quick to load.

FYI the rest of my Mac is quick on startup, I can be browsing Safari listening to Spotify within seconds.

A browse of the net has made me try a few things to no avail.

- Delete time machine snapshots in terminal

- Boot up in safe mode

- Restart and reset NVRAM

I have also unboxed a brand new external drive, copied my photos onto it but it is still the same (I wondered whether the older drive was on its way out)

Any help greatly appreciated,

Thanks,

Dan

Hi Dan,

That is not a typical experience with Lightroom and it does sound frustrating, as Lightroom is booting up at a slow speed. Could you please try optimizing the performance of Lightroom and let us know if it helps? Optimize Lightroom performance

Have you tried turning off the GPU option from Lightroom's preferences?
Go to Lightroom > Preferences > Performance tab > Uncheck "Use Graphics Processor" > Restart Lightroom.


Also, could you please let us know the exact version of Lightroom you're using by going to Help > System Info?

Regards,
Sahil

Views

3.3K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Adobe Employee ,
Jun 03, 2019

Copy link to clipboard

Copied

Hi Dan,

That is not a typical experience with Lightroom and it does sound frustrating, as Lightroom is booting up at a slow speed. Could you please try optimizing the performance of Lightroom and let us know if it helps? Optimize Lightroom performance

Have you tried turning off the GPU option from Lightroom's preferences?
Go to Lightroom > Preferences > Performance tab > Uncheck "Use Graphics Processor" > Restart Lightroom.


Also, could you please let us know the exact version of Lightroom you're using by going to Help > System Info?

Regards,
Sahil

Likes

1 Like

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 03, 2019

Copy link to clipboard

Copied

Many thanks for your reply.

'Use graphics processor' is already unchecked.

Below is the info from my system info, I updated the software yesterday in the hope this may solve it but hasn't, the problem persisted on the previous version too.

Lightroom Classic version: 8.3.1 [ 201905241238-dcd7e2de ]

License: Creative Cloud

Language setting: en-GB

Operating system: Mac OS 10

Version: 10.14.0 [18A391]

Application architecture: x64

Logical processor count: 4

Processor speed: 3.2 GHz

Built-in memory: 16,384.0 MB

Real memory available to Lightroom: 16,384.0 MB

Real memory used by Lightroom: 1,848.7 MB (11.2%)

Virtual memory used by Lightroom: 5,191.2 MB

Memory cache size: 290.2MB

Internal Camera Raw version: 11.3 [ 197 ]

Maximum thread count used by Camera Raw: 3

Camera Raw SIMD optimization: SSE2,AVX,AVX2

Camera Raw virtual memory: 767MB / 8191MB (9%)

Camera Raw real memory: 768MB / 16384MB (4%)

Displays: 1) 2560x1440

Graphics Processor Info:

Metal: NVIDIA GeForce GT 755M

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Employee ,
Jun 03, 2019

Copy link to clipboard

Copied

Thanks for providing the information, could you please try creating a new catalog and import a few images into it? Then let us close Lightroom and let us know if it opens up faster?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 03, 2019

Copy link to clipboard

Copied

I have never used catalogues, always just imported into a folder and worked out of that

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 03, 2019

Copy link to clipboard

Copied

`This is what I look at for 5 minutes until the numbers populate in place of the dashes

61605601_349145369135981_8749100565251751936_n.jpg

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jun 03, 2019

Copy link to clipboard

Copied

dannyc34543779  wrote

I have never used catalogues, always just imported into a folder and worked out of that

The folder that you are working from is a catalogue in itself. Lightroom uses catalogues and this is what you import to, and then you work from that. 

Perhaps by creating a new catalogue, as suggested, this may solve your problem.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 03, 2019

Copy link to clipboard

Copied

Thanks for that Ricky, so which of these levels is the actually Catalogue? Right back up to 'My Lightroom Photos USB?' which is the external USB name?

Screenshot 2019-06-03 at 19.07.13.png

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jun 03, 2019

Copy link to clipboard

Copied

Everything. When you open Lightroom you're opening a catalogue. You can have as many catalogues as you like.

In the very top of the folder structure, you even have "Catalog". All your photos are in this catalogue!

dannyc34543779  wrote

Thanks for that Ricky, so which of these levels is the actually Catalogue? Right back up to 'My Lightroom Photos USB?' which is the external USB name?

Screenshot 2019-06-03 at 19.07.13.png

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jun 03, 2019

Copy link to clipboard

Copied

As has requested please try LR using a new catalog with a few image files imported into it. This will help determine what is causing the issue. Follow the instructions at the below link. BTW there is no need to use more than one (1) catalog so you can delete this new catalog file after testing it. Give it a unique name such as Test Catalog and locate it on your system drive. Reboot your system and see if LR opens faster using the new catalog.

How to create and manage catalogs in Photoshop Lightroom Classic

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 03, 2019

Copy link to clipboard

Copied

Cheers Todd/Ricky

So I clicked File>newcatalogue>called it TEST CATALOGUE, copied 25 photos in, restarted my mac and the photos appeared immediately.

Therefore, this looks like it could my problem.

My other catalogue was just called 'Lightroom Catalogue' and when i opened it back up it once again took ages to load.

As you can see from a previous screengrab I have folders with thousands of photos per year i.e 2015, 2016, 2017, 2018 etc. Is it possible to create a catalogue for previous years and copy them in and if so would this help me now?

Thanks again

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jun 03, 2019

Copy link to clipboard

Copied

OK two things.

You should back up your LR Catalog to a different drive (your external USB HD) than where it is located AND to a 2nd external drive used specifically for back up of your media and document files files. You should do this after every major editing session such as after adding pictures to LR from a shoot.

To do that open your original catalog and go to Edit> Catalog Settings> General and select Back up catalog> Every time Lightroom exits. This will remind you each time you close LR to decide if a backup is required. Next close LR and in the below dialogue Choose the Backup Folder location to a folder on your external USB drive and check BOTH options as shown below. When complete restart your system and see if this fixed the issue. Tell us if the issue persists and we can try merging your catalog into a new catalog. But hold off on that right now.

Likes

2 Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 03, 2019

Copy link to clipboard

Copied

Ok, I'll take a look at doing that.

One question first though. I never saw the need to backup catalogue as I use time machine which makes regular backups.

Is this not the case?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jun 03, 2019

Copy link to clipboard

Copied

dannyc34543779  wrote

One question first though. I never saw the need to backup catalogue as I use time machine which makes regular backups.

Is this not the case?

Yes, as long as the Time Machine Backup is to a separate external drive dedicated for that purpose.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Most Valuable Participant ,
Jun 03, 2019

Copy link to clipboard

Copied

`This is what I look at for 5 minutes until the numbers populate in place of the dashes

Part of the slow launch time is likely due to a LR performance bug when you have many folders and smart collections that are expanded in the Folders and Collections panels in the left column of Library.

As a palliative, collapse the Folders panel and the Collections panel by clicking on the grey triangles to the left of them:

Then restart LR.  Does it start up faster now?

If so, then keep as many of the parent folders and collection sets collapsed as you can while you're working.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 04, 2019

Copy link to clipboard

Copied

Thankyou for all your help. This looks like a catalogue issue so have started a new thread to hopefully sort the problem.

Splitting one catalogue into multiples catalogues

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jun 04, 2019

Copy link to clipboard

Copied

That should not be necessary. As I suggested we can try merging your current catalog into a new catalog. That often corrects many issues without having create and use multiple catalogs.

Create a new empty catalog and give it a unique name different than your current working catalog like Lightroom Classic Catalog and follow the instructions at the below link. Make sure you have created a backup copy of your current catalog for restoration if something goes wrong.

How to import photos from Photoshop Elements, other Lightroom Classic catalogs, or apps such as iPho...

Choose Add New Photos To Catalog Without Moving. Once complete close and restart LR and see if the slow startup issue is resolved using the new catalog. If so you can remove the old catalog folder, but make sure to verify all is well using new catalog.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 04, 2019

Copy link to clipboard

Copied

Thankyou Todd Shaner​, will give this a go and report back.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Most Valuable Participant ,
Jun 04, 2019

Copy link to clipboard

Copied

But what happens when you collapse Folders and Collections and restart LR?  Does it start up faster?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 04, 2019

Copy link to clipboard

Copied

No change John unfortunately

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 04, 2019

Copy link to clipboard

Copied

Hi Todd Shaner​ so I went back through this post and revisited the link sent in the first reply regarding optimizing.

I made sure all performance suggestions in there were correct to my situation with regards to hard drive speed/RAM/location of files etc.

The only thing I missed was 'optimize catalogue' under the file menu.....

This took 10minutes to carry out and seems to have worked after a reboot!

Massive thanks for your consistent help and I'll be straight back if the previous fault comes back after a few reboots.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Most Valuable Participant ,
Jun 04, 2019

Copy link to clipboard

Copied

This only occurs on the first startup after booting up, if I "Quit Lightroom Classic' and then open it again its quick to load.

No change John unfortunately

This suggests your issue isn't related to the other symptom you've observed, the slow population of the folder counts. Others who have reported on that symptom observe that collapsing the Folder panel eliminates the startup CPU usage: Lightroom Classic 7.2: Very slow to build the folder structure | Photoshop Family Customer Community

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Most Valuable Participant ,
Jun 04, 2019

Copy link to clipboard

Copied

The only thing I missed was 'optimize catalogue' under the file menu..... This took 10minutes to carry out and seems to have worked after a reboot!

internal 1TB fusion drive.

This only occurs on the first startup after booting up, if I "Quit Lightroom Classic' and then open it again its quick to load.

Fascinating. The main thing Optimize does is compact the catalog's .lrcat file, removing unused blocks that slowly accumulate after large numbers of updates to the catalog. Normally, this isn't much of an issue even for frequently used catalogs, and Optimize produces only modest compaction, but perhaps for some reason yours is the exception. 

To help others in the future, perhaps you could report this: Find a recent backup of your .lrcat catalog file and report its size, and report the current size. (Do Catalog Settings > General > Show to open Finder on the catalog folder and the .lrcat file.)

-----------------------

My geek hypothesis: Mac OS caches the contents of files in memory.   So when you first startup LR after a reboot, it reads the catalog file, and Mac OS caches the file in memory, even after LR exits and then restarts.  I think that initial read of the catalog file was really, really slow; but once it was cached in the OS, subsequent starts could read the file blazingly fast.  

A fragmented file with lots of unused blocks could be slower to read, and perhaps it was so large and fragmented that it was triggering bad performance from your Fusion drive.  A Fusion drive is a hybrid with a small SSD and a large spinning disk, and Mac OS tries to keep most recently used files on the faster SSD.  But perhaps the catalog file was so large and fragmented that Mac OS just thrashed around. (Disk caching algorithms can perform perform poorly with very large files.)

Or maybe the catalog file was on a region of the spinning disk that has failing blocks that the drive must reread multiple times to get the correct contents, and optimizing the catalog moved it to a different part of the disk with no failing blocks.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Explorer ,
Jun 04, 2019

Copy link to clipboard

Copied

Thanks John, you obviously know much more about this than I ever will.

I am just happy for the help I was offered here and that at the moment it seems to operating normally.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jun 04, 2019

Copy link to clipboard

Copied

dannyc34543779  wrote

The only thing I missed was 'optimize catalogue' under the file menu.....

This took 10minutes to carry out and seems to have worked after a reboot!

Glad to hear that resolved the slow LR startup. In my reply #11 I suggested you check both 'Test Integrity' and 'Optimize Catalog' options in the Backup dialogue. I suggest keeping them checked for ALL catalog backups to help prevent this from happening again. Makes sure to do a LR catalog backup on exit after ANY editing session that would take considerable time to redo. That way if something happens to the catalog file you simply restore the latest backup to recover. A Time Machine backup does NOT perform the LR 'Test Integrity' and 'Optimize Catalog' functions so it's important to do this using the LR Backup utility. Time Machine will then backup the optimized and integrity tested backup Zip file copy.

Likes

3 Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Mar 18, 2020

Copy link to clipboard

Copied

Time machine normally does not backup the catalog file when it is open. If like me you keep Lightroom Classic open 100% of the time, you won't get any backups of the catalog file. They're also harder to restore than the backups that Lightroom itself makes where you just click the zipped backup, finder expands it and you can open the backed up catalog. Note that catalog files is where Lightroom stores all your settings. It does not store any images in the catalog. It is just a database pointing to your images and has all the devlop settings and keywords in it. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Oct 14, 2019

Copy link to clipboard

Copied

I am experiencing exactly the same problem in a Windows machine. I changed some parameters without any effect. As you mentioned, after the slow start up LR classic runs very fast. So I think that when starting up the program makes some new connection to the Adobe sites to downolad or who knows what and this process is slow or times out because of some connection setting. But I do not find any answer to the problem on the net.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Jan 06, 2020

Copy link to clipboard

Copied

I've actually have the same problem: both LR Classic and Photoshop 2020 take too long to load, but once they load, they perform fine. I've timed them: both take 2 plus minutes to load before they become operational. I've tried turning off my

NVIDIA GeForce GT 750M 2 GB graphics engine, but there was no noticeable speeding up of the loading. I use a 2015 MBP with 16 GB memory and 1 TB solid state drive. The problem arose with Catalina and more recent updates of Adobe PS and LR. It's an irritant but not a deal breaker for me. I hope you can fix it.

One more thing PS 2018 loads without a hitch. So, it's something between 2018 version and 2020 that created the problem.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Jan 08, 2020

Copy link to clipboard

Copied

I just add an info: during the long boot CPU consumed by LR is less than 3% and GPU is 0 (nothing else running except standard services). So the LR process seems really to wait for some event that does not occur.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Mar 16, 2020

Copy link to clipboard

Copied

I also have this issue and I don't see any work from Adobe to address this problem.

I already spent several hours on the web support and the problem was confirmed and was to be escalated.

Who knows what that means and when it would be addressed.

One way that I found to accelerate LR startup is to open task manager and play around going from one process to another with the mouse.

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Mar 18, 2020

Copy link to clipboard

Copied

I'm having the same issue as well...VERY frustrating. Takes 10min to start up and then everything seems normal after that. My main catalog is stored on a local SSD with Files on external USB, but I have a similar issue with another catalog where everything is on the local SSD.

OS: Windows 10

LR version:

RAM: 24GB

LR Catalog Drive: SSD

LR File Drive: La Cie External 2TB Rugged Drive

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Apr 16, 2020

Copy link to clipboard

Copied

I also have LR now starting extremely slow once I upgraded to my new ThreadRipper 2950x, with 128 GB RAM, and a eVGA RTX 2080 Super. Using super fast M.2 1TB drives for my OS and Adobe files and cache.  Crazy.  My old AMD 8350 with 32 GB and eVGA 960 was faster with my SSD drives.  I wonder what is going on as well. It used to take 16 seconds to boot up LR version 8.*, but now version 9.2.1, it takes more than 60 seconds.  Then only works so so. Moving from photo to photo, even with 1:1 previews being built on import, it still takes 2 seconds to see the photo in full clearity. 

. -- Windows Pro 10 AMD ThreadRipper 2950x water cooled, Corsair 128GB RAM, Two Fast M.2 1TB drives for OS and Adobe, RAID for storage 8TB, eVGA RTX2080 super FTW Canon 5D MKII, Epson 4990 Scanner, SureColor P400 Printer

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
New Here ,
Jun 03, 2020

Copy link to clipboard

Copied

I am running Lightroom 5.7.1 on a new computer. I built the computer from scratch because I was forced to go to Windows 10 and my older computer was not a good choice to update.   I never had any problems opening Lightroom on the old computer. On the new one, Lightroom would open in 6 seconds right after booting Windows 10.  The next day, Lightroom would open in 18 seconds.  At the end of that day, it would require 28 seconds, and the problem got progressively worse each day, if the computer wasn't rebooted.  Since it was a new computer, I checked out every forum I could find on Lightroom, Windows 10, Drivers, Drives, Bios, Cloud Backup, Antivirus, and nothing helped. The Task Manager didn't show any memory, processor, or drive problems, or other overloads while this was happening.

 

I started checking things that could be running in the background which could cause daily degradation. At least for my computer, I found the problem and it fixes it 100%.  It is very easy and won't take but a few minutes of your time to find out if it helps you.

 

On your Windows desktop, right click and select Personalize. On the Settings window that opens, click on the Background tab on the left side of the window. On the Background drop-down selector in the middle of the screen, change it from Slideshow to Picture and select the still picture of your choice.  (If your background was already set to Picture, then my fix won't work.)  Close the window, close any open programs, and restart Windows 10.  If my fix works for you, that's all you need to do. I have tried many promising fixes in the past only to be disappointed, so I hope this fix is worth your time!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Jun 04, 2020

Copy link to clipboard

Copied

Versione di Lightroom Classic: 9.2.1 [ 202004070813-7699d98a ]

Licenza: Creative Cloud

Impostazioni lingua: it

Sistema operativo: Windows 10 - Home Premium Edition

Versione: 10.0.18363

Architettura dell'applicazione: x64

Architettura del sistema: x64

Conteggio processore logico: 12

Velocità processore: 3,1 GHz

Versione SqLite: 3.30.1

Memoria integrata: 16318,2 MB

Memoria reale disponibile in Lightroom: 16318,2 MB

Memoria fisica usata Lightroom: 1387,5 MB (8,5%)

Memoria virtuale usata Lightroom: 1612,0 MB

Conteggio oggetti GDI: 777

Conteggio oggetti UTENTE: 2655

Conteggio maniglie elaborate: 2367

Dimensione cache memoria: 972,1MB

Versione Camera Raw interna: 12.2.1 [ 415 ]

Numero di thread massimo utilizzato da Camera Raw: 5

Ottimizzazione SIMD Camera Raw: SSE2,AVX,AVX2

Memoria virtuale di Camera Raw: 240MB / 8159MB (2%)

Memoria reale di Camera Raw: 239MB / 16318MB (1%)

Impostazione DPI del sistema: 144 DPI (modalità DPI elevata)

Composizione desktop attivata: Sì

Monitor: 1) 1920x1080, 2) 3840x2160

Tipi di input: Multitouch: No, Tocco integrato: No, Penna integrata: No, Tocco esterno: No, Penna esterna: No, Tastiera: No



Informazioni processore grafico:

DirectX: NVIDIA GeForce GTX 1060 6GB (26.21.14.3200)





Cartella applicazione: C:\Program Files\Adobe\Adobe Lightroom Classic

Percorso libreria: C:\LightRoom Catalog SSD\LT_MM_2014 SSD-2-2.lrcat

Cartella impostazioni: C:\Users\Michele\AppData\Roaming\Adobe\Lightroom



Plug-in installati:

1) AdobeStock

2) Facebook

3) Flickr

4) LogiOptions

5) Plug-in acquisizione diretta Nikon



Indicatori Config.lua: None



Adattatore n. 1: Fornitore : 10de

Dispositivo : 1c03

Sottosistema : 85b61043

Revisione : a1

Memoria video : 6052

Adattatore n. 2: Fornitore : 1414

Dispositivo : 8c

Sottosistema : 0

Revisione : 0

Memoria video : 0

AudioDeviceIOBlockSize: 1024

AudioDeviceName: MX27UC (NVIDIA High Definition Audio)

AudioDeviceNumberOfChannels: 2

AudioDeviceSampleRate: 48000

Build: 12.1x4

Direct2DEnabled: false

GL_ACCUM_ALPHA_BITS: 16

GL_ACCUM_BLUE_BITS: 16

GL_ACCUM_GREEN_BITS: 16

GL_ACCUM_RED_BITS: 16

GL_ALPHA_BITS: 0

GL_BLUE_BITS: 8

GL_DEPTH_BITS: 24

GL_GREEN_BITS: 8

GL_MAX_3D_TEXTURE_SIZE: 16384

GL_MAX_TEXTURE_SIZE: 32768

GL_MAX_TEXTURE_UNITS: 4

GL_MAX_VIEWPORT_DIMS: 32768,32768

GL_RED_BITS: 8

GL_RENDERER: GeForce GTX 1060 6GB/PCIe/SSE2

GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA

GL_STENCIL_BITS: 8

GL_VENDOR: NVIDIA Corporation

GL_VERSION: 4.6.0 NVIDIA 432.00

GPUDeviceEnabled: false

OGLEnabled: true

GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_AMD_vertex_shader_viewport_index GL_AMD_vertex_shader_layer GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_locations GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shader_viewport_layer_array GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_sparse_texture2 GL_ARB_sparse_texture_clamp GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_filter_minmax GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_post_depth_coverage GL_EXT_provoking_vertex GL_EXT_raster_multisample GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_formatted GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_sparse_texture2 GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_filter_minmax GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_R8 GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_EXT_memory_object GL_EXT_memory_object_win32 GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_equation_advanced_coherent GL_NVX_blend_equation_advanced_multi_draw_buffers GL_NV_blend_minmax_factor GL_NV_blend_square GL_NV_clip_space_w_scaling GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_conservative_raster_pre_snap_triangles GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_feature_query GL_NV_fence GL_NV_fill_rectangle GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_coverage_to_color GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_fragment_shader_interlock GL_NV_framebuffer_mixed_samples GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_geometry_shader_passthrough GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_memory_attachment GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_path_rendering_shared_edge GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_sample_locations GL_NV_sample_mask_override_coverage GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_float64 GL_NV_shader_atomic_fp16_vector GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_stereo_view_rendering GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NV_viewport_array2 GL_NV_viewport_swizzle GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_OVR_multiview GL_OVR_multiview2 GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Adobe Community Professional ,
Jun 04, 2020

Copy link to clipboard

Copied

Plug-in installati:
1) AdobeStock
2) Facebook
3) Flickr
4) LogiOptions
5) Plug-in acquisizione diretta Nikon

The LogiOptions plugin is known to cause long startup times.

Go to File > Plugin manager and disable it.

Then restart Lightroom.

 

LR-plugin-manager.png

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Community Beginner ,
Jun 04, 2020

Copy link to clipboard

Copied

GREAT!!!
I have disabled all the non Adobe plugins (that I do not need) and the
start up is now much faster.
Thanks, Michele

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...