"The Spot Removal Tool and Local
Corrections Brush are not designed for hundreds to thousands of
corrections.
If your image contains many (hundreds) of localized
adjustments, consider using a pixel-based editing application such as Affinity Photo or Photoshop for that level of correction..."
Use optimal settings in Lightroom
Pause ‘Sync With Lightroom CC’ while making edits in Lightroom Classic
Keep standard-size previews as small as possible
Keep the catalog and preview cache in the same folder
Leave autowrite XMP turned off
Optimize the catalog
Increase the Camera Raw cache size Spot Removal tool, local corrections, and History panel - don't use too much :o
Order of Develop operations
Avoid corrections that you don't need
Zoom options
Delete the Lightroom previews cache
Reduce the number of presets
The best order of Develop operations to increase performance is as follows:
Spot healing.
Geometry corrections, such as Lens Correction profiles and Manual corrections, including keystone corrections using the Vertical slider.
Global non-detail corrections, such as Exposure and White Balance. These corrections can also be done first if desired.
Local corrections, such as Gradient Filter and Adjustment Brush strokes.
Detail corrections, such as Noise Reduction and Sharpening.
Note: Performing spot healing first improves the accuracy of the spot healing, and ensures the boundaries of the healed areas match the spot location.
1. Use fastest drive for catalog, cache and current photos. Make new catalog for any new job, then proceed with these steps.
2. Render smart previews then CHANGE the name of photos folder [this
is different from just checking that box mentioned in article], LR will
render smaller files [from 24MPX, it makes about 2600x1700 px files,
which are large enough for checking focus and noise etc].
3. Use import preset with camera specific ISO etc, your choice.
4. Import ONLY presets you will use, making LR caching 10000 or so
presets is not good. [some people are preset hoarders], This speeds up
LR a lot.
5. Make 1:1 previews of SMART previews [when they are detached from
the folder], to have import preset, smart preview and 1:1 on start.
6. Flag pics that you will edit [cull], rather than doing black flag
on non-chosen pics [morale thing, you reward yourself, you are more
likely to edit with more 'oomph' //optional
7. After whole cull and edit, change the name back to have original
files in LR, check sharpening and noise reduction, and export.
8. After job is exported to JPGs, export whole catalog with files
onto a slower archive folder. Name it, so that you know which job was
that.
9. New pictures? New catalog, and from 1 to 9 again, Starting on
fastest drive with clean new empty catalog, import photos as instructed.
__________
That's my workflow, and I don't see how it could be any faster
[culling maybe, but with smart previews it's ultra fast]. Hope this
helps anyone, I can go into details if someone wants to learn more about
my workflow. It works for superfast PCs and slow laptops, so far
haven't seen it go any faster.
I know from my experience
on the KelbyOne Help Desk, as well as from various forums and
conversations with other Lightroom users, that improving performance has
been high on everyone’s wish list. Adobe has apparently taken this
issue seriously and devoted most of its resources for this version to
identifying various points in the workflow where speed can be improved.
One of the first places you may notice an improvement is in launching
the program, which should be more noticeable with larger catalogs. I’ve
definitely noticed an improvement here.
Florence Owens Thompson
- 1. září 1903 – 16. září 1983
Migrant Mother
Florence Owens Thompson was the subject of Dorothea Lange's famous photo Migrant Mother (1936
Library of Congress
While the image was being prepared for exhibit in 1941, the negative of the photo was retouched to remove Florence's thumb from the lower-right corner of the image...
source: wiki
We’ve worked with a large number of
3rd party preset makers to help them create profiles, and a number of
them have made sets available already. If you’re interested in exploring
ways of expanding the range of Creative profile options, be sure to
check out one of the companies below...
As the title would suggest, Google has released a new open source JPEG encoder called Guetzli that uses a new open source algorithm to create JPEG files that are “35% smaller than currently available methods” (though if you dig a bit you’ll find they actually say it’s more typically 20-30%). That’s according to Google’s own literature from their Research Blog, and that’s a significant claim if for no other reason than there exits JPEGmini ...
SHOOT IN RAW? EDIT IN 16 BIT MODE? SEE IT ALL HERE! | Check out my short video breakdown that will help you understand the differences between 8bit and 16bit images and editing in Photoshop ...
2. Render smart previews then CHANGE the name of photos folder [this is different from just checking that box mentioned in article], LR will render smaller files [from 24MPX, it makes about 2600x1700 px files, which are large enough for checking focus and noise etc].
3. Use import preset with camera specific ISO etc, your choice.
4. Import ONLY presets you will use, making LR caching 10000 or so presets is not good. [some people are preset hoarders], This speeds up LR a lot.
5. Make 1:1 previews of SMART previews [when they are detached from the folder], to have import preset, smart preview and 1:1 on start.
6. Flag pics that you will edit [cull], rather than doing black flag on non-chosen pics [morale thing, you reward yourself, you are more likely to edit with more 'oomph' //optional
7. After whole cull and edit, change the name back to have original files in LR, check sharpening and noise reduction, and export.
8. After job is exported to JPGs, export whole catalog with files onto a slower archive folder. Name it, so that you know which job was that.
9. New pictures? New catalog, and from 1 to 9 again, Starting on fastest drive with clean new empty catalog, import photos as instructed.
__________
That's my workflow, and I don't see how it could be any faster [culling maybe, but with smart previews it's ultra fast]. Hope this helps anyone, I can go into details if someone wants to learn more about my workflow. It works for superfast PCs and slow laptops, so far haven't seen it go any faster.