P: Allow for keyboard shortcut customization

@C.Cella 

That makes sense about the history steps. I am sure PFixer works the same way, and I've been using that for years with no trouble, aside from clearing it from the ram every few days. I'll look into deleting history steps as a bonus. I have the M1 Max with 32gb ram, 32 core gpu, and 2 tb drive now, so I'm definitely not worried about it since I never had any problems with my old 2013 i5 IMac and MacBook. Maybe it would be a something to look out for with a junky computer. 

It's too bad keyboard editing hasn't sped things up for you. I've found less mouse/trackpad fatigue, and way less scrolling in the develop module. I also have my favorite presets set to cmd+1, cmd+2, etc. so I can edit a picture by just doing cmd+3, FFSRRRWGX... etc. then I'll press , to copy the settings, and . To paste them. / lets me sync settings. Yeah all that can be done with the mouse, but it objectively takes more time to drag the mouse, and my wrist gets tired of the mouse. 

The only downside I've seen to keyboard editing is that you have to memorize the keyboard shortcuts, but that's not too bad. 

@evanwish 

PowerKeys creates/adds an absurd amount of history steps to each photo.

E.g

To change a settings form 0 to 100 PowerKeys creates 10 history steps, 10 individual events, while LrC only creates one step using sliders or edit boxes.

So you end up with probably hundreds of history steps per photo just to change few settings back and forth.

This is going to create lots of problems especially if your photos have local edits:  bloated catalog, slowdowns, enormous temp file, etc...

I already contacted the author of PowerKeys and explained this issue with history steps.

I am not familiar with PFixer, I have seen a bit of LoupeDeck.

For fast editing reaching the keyboard is not faster than reaching the slider or the edit box.

It's equivalent.

To me reaching the keyboard for editing, or to use shortcuts is slow: I don't do it, I have a faster way to work.

.

@C.Cella 

How would you compare the challenges you are seeing to PFixer? I've been using PFixer for years. My catalogs are big, I start a new catalog twice a year, and generally have about 80 shoots in each catalog. PFixer would fill up my ram after a few days of editing and I would just quit and restart both PFixer and Lightroom and it would reset the ram just fine. I haven't been using Power Keys more than a few days, but it seems the same so far. 

@evanwish 

You are clearly unaware of the problems that Plug-in is creating.

If you like to have bloated catalog and even have poor performance then go ahead and keep using it.

.

@cwurzbach 

I have tried you Plug-in and sent you an eMail with my feedback.

@evanwish I'm really glad to hear you are enjoying Power Keys. Our plan is to release the next version before the end of the year.

@C.Cella In my experience, I've found using a keyboard is the quickest way to edit large quantities of images. Feel free to give it a try. Personally, I couldn't imagine editing in Lightroom Classic any other way now that I have this functionality.

@richardplondon 

I understand those methods of editing with the keyboard shortcuts, currently available in Lightroom, but once you try something like PFixer, it's impossible to go back. The speed difference is incomparable. 

@cwurzbach

THANK YOU! You are the hero that Lightroom failed to find. I just downloaded your software and it works beautifully. I am very excited for your upcoming updates. I've done a bit of playing around so far and found I can run GetPowerKeys and PFixer simultaneously. I just successfully tested using GetPowerKeys for the single key press commands (ie: f for brightness up) and PFixer for the other features not supported yet. Works flawlessly! Probably till the next update where PFixer will finally kick the bucket. Thank you so much for your reply and your work on this exciting replacement. 

also, I recommend others try this or something like it. It's game changer. 

Thank you for the correction, I should have ensured my lingo was accurate first. Thank you also for the link! A breath of fresh air, I'm excited to check it out now. 

@cwurzbach 

I don't see how your Plug-in would be faster than reaching an edit box, click it, and change the setting form there using up/down or wheels/knobs... which also spares us the creation of infinite history steps.

.