P: Respect Hierarchical Folders of Presets

The above thread it seems has been marked as resolved by an official comment that Hierarchical Folder presets  were implemented in Lightroom 4, even if they were, they are not currently in CC, which is why the thread is asking for them, but confusion abounds as commentators seem to think that Lightroom just do not care, is it possible to get some sort of official review/comment of this thread. ? thank you

GREAT NEW WAY TO GIVE THIS FEEDBACK...  Adobe put up a survey asking users to tell them their top 3 issues with Lightroom performance. This is a good place to let them know about how much time we waste because Lightroom does not provide for hierarchical Develop Module Preset folders. Here's the link to the survey:  https://www.surveymonkey.com/r/LrDesktop_performance

So glad I have found this but really surprised there are so few votes.
Please, Adobe can something be done about making our time on your product more efficient. It would be greatly appreciated by many people.

I have a lot of presets and when it comes to organisation Lightroom is not my friend. Surely the organisation of presets should be a priority for the application/program. Yes folders of presets are good but when you buy collections and they are in 15/20 different types it would be nice to have your main folder (preset creator) then within that folder for example folders grunge, vintage, etc etc.

Lars got it right on the money. Adding a filter/search to this would be, IMHO, perfect.

1. Develop Module - Preset panel (Mandatory)
2. Library Module - Quick Develop panel (Yes - please)
3. Auto Import>Auto Import Settings... (Yes - please)
4. Tether Capture Tool Bar (Yes - please)
5. Import dialog - Apply During Import panel (Yes - please)

How many levels of hierarchy are desired? 4
How many are necessary? 2
How many will be detrimental to the average user? > 5

And in local ajustments (filter effects) - minimum 2 levels!

Thank you, beautifully said! We must keep the momentum going on this. We're closer now than at any time in the past as we at least have someone's attention at Adobe. Thank you Rikk Flohr for taking us seriously.

Please keep your comments on topic not person....

Thank you for an official answer 🙂

As for your questions:

"Have you viewed all five of the places where this will impact UI and are comfortable with the impact on workflow in those areas - whether you use a particular area or not?"

Of course performance impact is never a good thing - I do believe however it is definitely well worth it if the impact is only on preset preview and application. If there is a significant delay every time when switching to the Develop module, that would be a matter for concern (but also a sign of seriously bad programming ^^).

"Specifically to all who have posted on this thread - which area (1-5) are you asking about?"

I mainly just care about the 1 - Develop module. The functionality would of course also be very nice on 2, 3 and 5, though I personally don't use these often enough to matter (and if I do, I can currently use a single folder for favorite import presets). As for 4 - ask me again when Adobe and Pentax get their act together and I can actually shoot tethered 😉

"How many levels of hierarchy are desired?"

Obviously, two at a minimum so we can have preset groups with subgroups. Three would be a lot nicer, of course, but I could live with two if that's significantly easier to implement. Four or more already seems a bit like overkill to me personally.

"How many are necessary?"

See above - even two levels would already help a lot compared to the current situation.

"How many will be detrimental to the average user?"

That's a non-issue IMHO because even if you were to offer fifty levels of hierarchy, nobody would be forced to use them. But for sanity's sake, I'd draw the limit at five.

Of course, a Filter / Search box as suggested by John would also be a very welcome addition. But if I had to choose between those two, I'd prefer a hierarchy because it's easier to browse a well organized preset library than wracking my brain for the name of a preset I forgot.

As for this:

"Preset organization needs to be consistent across the application"

Just out of curiosity let me ask why is this? Is this a necessity because all those areas using presets use the same code or is this a dictum from your UI/UX team?