P: Allow for keyboard shortcut customization

Commenting to add to the many requests for custom keyboard shortcuts in Lightroom. 

would be very convinient... specially to solve the very frequent problems with shortcuts

@cwurzbach 

See the latest reply by @johnrellis 

You should be able to fix the issue with history in your Plug-in with those. 

.

The relevant calls are:

LrDevelopController.startTracking( param )

LrDevelopController.stopTracking( isLocalParam )

LrDevelopController.setTrackingDelay( seconds )

LrDevelopController.setMultipleAdjustmentThreshold( seconds )

@evanwish 

I believe that LoupeDeck is not adding countless of history step when using knobs or buttons. 

If the right API commands are used correctly a chage, a history step should be added only after a certain delay (like X ms after inactivity of keyUP event)

@johnrellis probably definitely knows how to make so that pressing a key in rapid succession or holding it, doesn't create countless of individual history steps/events.

@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.