P: Presets including raw profiles are sometimes available for non-raws, sometimes not

And another person who wasted time due to this confusion:
https://forums.adobe.com/message/10459499

Another person horribly confused by this behavior: 
https://forums.adobe.com/thread/2502681

Another person confused by this behavior: 
https://forums.adobe.com/message/10441151#10441151

My reply to your original post:

This confusing behavior happens because the problem presets include an enhanced profile (e.g. Adobe Color, Adobe Landscape, etc.).  According to an Adobe employee, this is by design. If you find this confusing, please  add your constructive opinion to this problem report in the official Adobe feedback forum: Lightroom Classic: Presets including raw profiles are sometimes available for non-raws, sometimes not | Photoshop Family...

A workaround is to modify the preset to uncheck Treatment & Profile so that the enhanced profile isn't included.  But unfortunately, yetanother preset bug makes that impossible when the preset includes any of the Color settings:

https://feedback.photoshop.com/photoshop_family/topics/automaticly-checking-treatment-prof ile-box-wh...

The workaround in that case is to remove the Treatment & Profile from the presets using the free Fix Presets plugin.

Hi,

Originally posted here: https://forums.adobe.com/message/10397349

I'm having trouble with some presets in my LR. I created a preset and it all works great, however, in the develop module on some images it seems that this preset is not available to use (it just doesn't show up in the list). I think it may be due to the type of image I'm trying to edit - I created the preset for an uncompressed RAW image I was working on, and it shows up just fine for any other uncompressed RAW images, but compressed RAW (even from the same camera) it doesn't show up, nor for any jpegs that I may have in my catalog. Is there any reason why this would be the case and is there a workaround so that I can use this preset on everything else in my library?

 

Shooting with a mix of a Sony a7, a7rii, rx100 and my phone.

 

Lightroom Classic version: 7.3.1 [ 1167660 ]

License: Creative Cloud

Language setting: en

Operating system: Windows 10 - Home Premium Edition

Version: 10.0.16299

Application architecture: x64

System architecture: x64

Logical processor count: 8

Processor speed: 2.3 GHz

Built-in memory: 8078.8 MB

Real memory available to Lightroom: 8078.8 MB

Real memory used by Lightroom: 2267.7 MB (28.0%)

Virtual memory used by Lightroom: 2406.7 MB

GDI objects count: 864

USER objects count: 2190

Process handles count: 2952

Memory cache size: 531.9MB

Internal Camera Raw revision: 933

Maximum thread count used by Camera Raw: 5

Camera Raw SIMD optimization: SSE2,AVX

Camera Raw virtual memory: 1677MB / 4039MB (41%)

Camera Raw real memory: 1697MB / 8078MB (21%)

System DPI setting: 96 DPI

Desktop composition enabled: Yes

Displays: 1) 1920x1080

Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

 

 

Graphics Processor Info:

DirectX: AMD Radeon HD 8800M Series (8.17.10.1404)

A workaround is to modify the preset to uncheck Treatment & Profile so that the enhanced profile isn't included.  But unfortunately, yet another preset bug makes that impossible when the preset includes any of the Color settings:

https://feedback.photoshop.com/photoshop_family/topics/automaticly-checking-treatment-profile-box-wh...

The workaround in that case is to remove the Treatment & Profile from the presets using the free Fix Presets plugin.

Yet another person who can't understand why some of his presets aren't appearing when editing JPEGs: https://forums.adobe.com/thread/2493603

I understand the logic of filtering out presets with some raw profiles, but that design is surely going to cause needless confusion and frustration.

A similar user interface causes one of the most frequent questions on the user-to-user forum: "Where are the lens profiles?".   Nothing in the user interface tells the user that the presets or lens profiles are being filtered when the current photo is a non-raw.  (And the type of the photo is hidden in Develop -- users often think they're editing a raw when in fact they're editing a JPEG.)

Two better alternative designs:

- Don't filter any presets containing raw profiles.  LR has gone all these years with presets containing raw profiles, and I don't recall seeing any complaints or confusion on the forums about that.  There's no problem to be fixed -- LR should just continue to ignore the contained raw profile when applying the preset to a non-raw.

- Give a clear visual indication in the user interface that presets are being filtered.  E.g. at the top of each group containing filtered presets, include this message in grey italics:

Some presets containing raw profiles are not shown because the current photo isn't raw

Or show the presets in the list but greyed out, and if the user tries to click on one, pop up the message:

This preset contains a raw profile that can't be applied to the current photo, which isn't a raw photo.

I have a few technical questions/suggestions about the LUT implementation with profiles. A few small modifications would make the use of LUTs far easier and intuitive. Mainly settings dealing with color space transforms and possibly the option of an Adobe Linear profile. Is there a person to contact regarding this? I've posted about it on the adobe blog and on the boards here (i think i was logged into a different account).