Highlighted

Fullscreen mode: slow switching between images

Participant ,
Oct 17, 2020

Copy link to clipboard

Copied

Hi,

I want to mark failed photos within 230 DNGs in full screen mode photo by photo (pressing x or cursor right).

But switching to the next photo takes 1 second each time – 0.9 seconds 😉 too long...

Switching in not fullscreen mode without such a delay.

The files are on my HDD (size of the DNGs: 4,4 GB), Lightroom/Cache on SSD.

 

Is this just the "usual (and well/bad known) performance" of Lightroom? 

My workaround (with a lot of work...): exporting all images as JPGs (only with 1800px width) and marking the photos with ACDSee, then "transferring" the result into LR.

 

Thanks a lot and greetings from Germany

mycc

 

–– 

Lightroom Classic-Version: 9.4 [ 202008061458-dbb2971e ]
Spracheinstellung: de
Betriebssystem: Windows 10
Version: 10.0.19041
Anwendungsarchitektur: x64
Systemarchitektur: x64
Anzahl logischer Prozessoren: 16
Prozessorgeschwindigkeit: 3,0 GHz
SQLite-Version: 3.30.1
Integrierter Speicher: 32713,4 MB
Für Lightroom verfügbarer phys. Speicher: 32713,4 MB
Von Lightroom verwendeter phys. Speicher: 2435,7 MB (7,4%)
Von Lightroom verwendeter virtueller Speicher: 2788,8 MB
Anzahl GDI-Objekte: 890
Anzahl BENUTZER-Objekte: 2305
Anzahl Prozess-Handles: 1945
Cache-Speichergröße: 815,6MB
Interne Camera Raw-Version: 12.4 [ 555 ]
Maximale Anzahl Threads, die Camera Raw verwendet: 5
Camera Raw SIMD-Optimierung: SSE2,AVX,AVX2
Virtueller Speicher in Camera Raw: 1195MB / 16356MB (7%)
Physischer Speicher in Camera Raw: 1197MB / 32713MB (3%)
Desktop-Komposition aktiviert: Ja
Monitore/Anzeigegeräte: 1) 2560x1440, 2) 2560x1440
Informationen zum Grafikprozessor:
DirectX: NVIDIA Quadro K2200 (26.21.14.4128)

Config.lua-Flags: None

Adapter Nr. 1: Anbieter : 10de
Gerät : 13ba
Subsystem : 109710de
Version : a2
Grafikspeicher : 4053
Adapter Nr. 2: Anbieter : 1414
Gerät : 8c
Subsystem : 0
Version : 0
Grafikspeicher : 0
AudioDeviceIOBlockSize: 1024
Build: LR5x42
Direct2DEnabled: false
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 441.28
GPUDeviceEnabled: false
OGLEnabled: true

–– 

 

 
 
 
 
 
 
 
 
 
 

2020-10-17_shot_006.png

 

2020-10-17_shot_007.png

 

TOPICS
Performance, Windows

Views

34

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

Fullscreen mode: slow switching between images

Participant ,
Oct 17, 2020

Copy link to clipboard

Copied

Hi,

I want to mark failed photos within 230 DNGs in full screen mode photo by photo (pressing x or cursor right).

But switching to the next photo takes 1 second each time – 0.9 seconds 😉 too long...

Switching in not fullscreen mode without such a delay.

The files are on my HDD (size of the DNGs: 4,4 GB), Lightroom/Cache on SSD.

 

Is this just the "usual (and well/bad known) performance" of Lightroom? 

My workaround (with a lot of work...): exporting all images as JPGs (only with 1800px width) and marking the photos with ACDSee, then "transferring" the result into LR.

 

Thanks a lot and greetings from Germany

mycc

 

–– 

Lightroom Classic-Version: 9.4 [ 202008061458-dbb2971e ]
Spracheinstellung: de
Betriebssystem: Windows 10
Version: 10.0.19041
Anwendungsarchitektur: x64
Systemarchitektur: x64
Anzahl logischer Prozessoren: 16
Prozessorgeschwindigkeit: 3,0 GHz
SQLite-Version: 3.30.1
Integrierter Speicher: 32713,4 MB
Für Lightroom verfügbarer phys. Speicher: 32713,4 MB
Von Lightroom verwendeter phys. Speicher: 2435,7 MB (7,4%)
Von Lightroom verwendeter virtueller Speicher: 2788,8 MB
Anzahl GDI-Objekte: 890
Anzahl BENUTZER-Objekte: 2305
Anzahl Prozess-Handles: 1945
Cache-Speichergröße: 815,6MB
Interne Camera Raw-Version: 12.4 [ 555 ]
Maximale Anzahl Threads, die Camera Raw verwendet: 5
Camera Raw SIMD-Optimierung: SSE2,AVX,AVX2
Virtueller Speicher in Camera Raw: 1195MB / 16356MB (7%)
Physischer Speicher in Camera Raw: 1197MB / 32713MB (3%)
Desktop-Komposition aktiviert: Ja
Monitore/Anzeigegeräte: 1) 2560x1440, 2) 2560x1440
Informationen zum Grafikprozessor:
DirectX: NVIDIA Quadro K2200 (26.21.14.4128)

Config.lua-Flags: None

Adapter Nr. 1: Anbieter : 10de
Gerät : 13ba
Subsystem : 109710de
Version : a2
Grafikspeicher : 4053
Adapter Nr. 2: Anbieter : 1414
Gerät : 8c
Subsystem : 0
Version : 0
Grafikspeicher : 0
AudioDeviceIOBlockSize: 1024
Build: LR5x42
Direct2DEnabled: false
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 441.28
GPUDeviceEnabled: false
OGLEnabled: true

–– 

 

 
 
 
 
 
 
 
 
 
 

2020-10-17_shot_006.png

 

2020-10-17_shot_007.png

 

TOPICS
Performance, Windows

Views

35

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
Oct 17, 2020 0
LEGEND ,
Oct 17, 2020

Copy link to clipboard

Copied

Are you talking about the Library Module or the Develop Module?

 

If you are talking about the Library Module, are you generating 1:1 previews?

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...
Oct 17, 2020 0
Adobe Community Professional ,
Oct 17, 2020

Copy link to clipboard

Copied

Why not try NOT using the Full Screen Mode and just hide all the panels, left/right/top/bottom (Filemstrip), and see how that goes?

 

 

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...
Oct 17, 2020 0
LEGEND ,
Oct 17, 2020

Copy link to clipboard

Copied

DirectX: NVIDIA Quadro K2200 (26.21.14.4128)

and

Direct2DEnabled: false
GL_VENDOR: NVIDIA Corporation
GL_VERSION: 4.6.0 NVIDIA 441.28
GPUDeviceEnabled: false

So, v441.28, somewhat out of date, per NVIDIA web site, v452.39 is available.

Also, does not look like DirectX 12 is running (Sys Info not clear on that, usually very clear), per NVIDAIA release notes, v452.39 should.

 

 

 

 

Just another Adobe customer; My Sys; APP: LRC 10.0, PS 22.0; CMP: WIN WS 16GB OS 10 v1909 (18363), mid 2015 MBPr 15” 16GB MACOS 10.15.7; 4K EXT DSPY; CAM: Canon 5D Mk III, Fuji X-T3

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...
Oct 17, 2020 0
LEGEND ,
Oct 17, 2020

Copy link to clipboard

Copied

Your Camera RAW CACHE, set for default of 5 GB is way undersized, increase that to at least 50GB, 70 would be better.

 

This effects Develop module only.

 

Just another Adobe customer; My Sys; APP: LRC 10.0, PS 22.0; CMP: WIN WS 16GB OS 10 v1909 (18363), mid 2015 MBPr 15” 16GB MACOS 10.15.7; 4K EXT DSPY; CAM: Canon 5D Mk III, Fuji X-T3

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...
Oct 17, 2020 0
GoldingD LATEST
LEGEND ,
Oct 17, 2020

Copy link to clipboard

Copied

Lightroom/Cache on SSD.

 

So, your C drive is a SSD? Screenshot shows Camera RAW CACHE is in C drive, your boot drive.

 

Ok, but can be improved if you have another SSD that is not your boot drive. It is best for performance on a Windows PC if the Camera RAW CACHE is not put on the same drive as the Windows OS Paging file. This due to read/wright competition.

 

 

Just another Adobe customer; My Sys; APP: LRC 10.0, PS 22.0; CMP: WIN WS 16GB OS 10 v1909 (18363), mid 2015 MBPr 15” 16GB MACOS 10.15.7; 4K EXT DSPY; CAM: Canon 5D Mk III, Fuji X-T3

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...
Oct 17, 2020 0