Skip to main content
Adobe Photoshop Family

2 Messages

 • 

80 Points

Fri, Nov 23, 2018 10:23 AM

Lightroom Classic CC 8.0 Develop Presets Issue

I wanted to raise an issue I came across in Lightroom Classic CC 8.0 with the Develop Presets chooser.

Essentially the Presets panel wasn't working with either no presets showing (as displayed below), or a kind of "stuck box" pattern appearing, not listing presets but merging in the boxes for Snapshots, History and Collections below. 

Presets did sort of work, but you were guessing where they were and you couldn't open sub-folders. In effect, it was of no use.

presetsJPG

When I posted in the Lightroom Classic CC forum (https://forums.adobe.com/thread/2546365) it was suggested that I try restoring app preferences to default. 

I did this, and it worked for a short time. But then the problem would re-occur.

My solution was to remove all my presets and then re-install them in small batches, checking LR each time to see if the problem had re-occurred. Note that I tried with both pre-April 2018 versions (i.e. pre XMP format), and post ones.

Eventually, I tracked the problem down to two pre-sets (https://www.dropbox.com/sh/dppyciypbp3qcj4/AAAc75JrbvOEb7r-6GyYEWgVa?dl=0) which if I excluded, and reset LR app preferences, seemed to fix the problem.

Note that I didn't have a problem with this until October, and initially with version 7.5, although the problem exists in version 8.0 which I have been using since launch.

Hope this helps.


Adam


Responses

Champion

 • 

5.2K Messages

 • 

93.3K Points

2 years ago

Those two presets imported without problem into my LR 8.0 / Mac OS 10.13.6. I looked at their internals and didn't see anything obviously wrong. So the bug might be more subtle, e.g. an interaction with the other presets you were importing or a problem particular to your configuration.  Hmm.

2 Messages

 • 

80 Points

2 years ago

It sounds like it's peculiar to me then. I'm using a Windows 10 machine, and importing either the old or new format presets causes me the same issue. But there might be other things at work.