Keyboard-Shortcut ⌘-G doesn't group anymore

[rschoeller]

The Keyboard-Shortcut ⌘-G was used to group the images in stacks. But in the new version it opens the preferences:

[dj_paige]

Please tell us your exact operating system version NUMBER (Number and not words to indicate the version)

Please tell us your exact version NUMBER of Lightroom (NUMBER and not words)

[rschoeller]

10.13.5 (macOS High Sierra)

7.4 (Lightroom)

[dj_paige]

I'm sure someone with that operating system version will try it on their computer and let us know if the problem is reproducible or not.

It is also possible that some operating system shortcut was assigned to that keystroke (that you the user set up) and so it overrides the Lightroom meaning of the keystroke. Please check for that.

[rschoeller]

No, there isn't any operating system shortcuts assigned. It worked in 7.3.

A friend of mine which is using a PC told me just, that he got the same problem. So it seems to be an across system fault.

[dj_paige]

Works fine for me under Windows 10, LR 7.4

[rschoeller]

Interesting. Maybe it's some kind of translation-problem: we are all working with german translations.

[viewfinder.pics]

Testet this Workaround with positive result:
https://www.lightroomqueen.com/custom-keyboard-shortcuts/

It overwrites the the Std. Keyboard Shortcuts

The workaround with editing the Translation Textfile ist very tricky and not for normal User 🙂 

Greets Peter

[johnrellis]

Testet this Workaround with positive result:

https://www.lightroomqueen.com/custom-keyboard-shortcuts/

It overwrites the the Std. Keyboard Shortcuts

If you're referring to setting the shortcut in the Mac's System Preferences, that is indeed easier. But unfortunately, there's no equivalent on Windows, so the options for Windows users are to edit TranslatedStrings, use the Keyboard Tamer plugin (which costs money), or get a third-party utility like Auto Hotkey (which itself isn't that easy to use).  For many, editing TranslatedStrings is the easiest.

It's unfortunate that Adobe keeps making these careless keyboard shortcut mistakes in nearly every release.

[viewfinder.pics]

Hi,

i found a small Tutorial for Windows User, How to edit the TranslatedStrings:
Changing Adobe Lightroom Keyboard Shortcuts In Windows (Video) – Craig Rogers

Editing the file in Windows is much easier 🙂

greets

Peter

[johnrellis]

It's yet another keyboard-shortcut bug: Lightroom: German keyboard shortcut for Group Into Stack broken | Photoshop Family Customer Communit... . See that post for a workaround. Based on years of such careless mistakes, it sure looks like Adobe has absolutely no quality processes around keyboard shortcuts.

[johnrellis]

Also, be sure to add your constructive opinion to that bug report, and click Me Too and Follow in the upper-right corner of its page. That will make it more likely Adobe will prioritize a fix, and you'll be notified when the bug's status changes.  Recently, it's taken Adobe six months or more to fix such mistakes in keyboard shortcuts.

[vanceance]

same here - new update in lightroom 8 for german users did the same.... can group with "strg+g" anymore..... not workable now atm ..... pls fix that quick with an update ...

[johnrellis]

This was fixed in LR 7.5 but broke again in LR 8.0! Please add your constructive opinion to the bug report: Lightroom: German keyboard shortcut for Group Into Stack broken | Photoshop Family Customer Communit... . Be sure to click Me Too and Follow in the upper-right corner, which will make it a little more likely Adobe will prioritize a fix and notify you when the bug's status changes.  See the bug report for a workaround.

[rschoeller]

Unbelievable!

So we have to edit the TranslatedStrings-File again.

[johnrellis]

Adobe appears to have no quality assurance process for the TranslatedStrings files.  They've repeatedly made editing mistakes over the past couple of years: Lightroom Classic: Allow for keyboard shortcut customization | Photoshop Family Customer Community

[Ian Lyons]

johnrellis  wrote

They've repeatedly made editing mistakes over the past couple of years

I would put the time span closer to 20 years.

Unfortunately, the TranslatedStrings files are implemented very late in pre release cycle, which means that errors tend to be found when it's too late to address. It's frustrating for everyone but that doesn't really address a problem that should not be occurring as frequently as it does.