P: Ability to sync Lightroom Classic keywords with the Lightroom Ecosystem

Same here. This and the poor handling of Fuji .raf files means that I am pointing people towards Capture One. It is a bit trickier for me to change with 14 years of images in Lightroom.

@max_l_g5zfjo4iqqgaf 

For what it's worth, I'm already at a point of NOT recommending Lightroom to anyone ever, but this is pushing me to migrate away myself. The team just keeps making one bad software design decision after another and when they are pointed out, the response is borderline offensive. 

Amen 🙏
I could not phrase it better.

LR used to be the best DAM, and by far. But development decisions the last years are terrible and customer are treated as excrements. Bugs are too often referred as « feature requests » if not referred to as « by design ». The updates are either marginal or for the social side of LR.

I too stopped recommending LR, sadly. LR used to be the best in its class. It’s not and by far!

But there is syncing of keywords, it's just badly broken. Keywords sync to the files stored in Lightroom CC, but Lightroom CC stays unaware of them. That is just bad software design and poor user experience. 

Why can't this be fixed? The simplest way to address it would be for Lightroom CC to re-read keywords on file change just like it does on file import. It will still be infinitely better than the current mind-blowingly poor design decision. 

For what it's worth, I'm already at a point of NOT recommending Lightroom to anyone ever, but this is pushing me to migrate away myself. The team just keeps making one bad software design decision after another and when they are pointed out, the response is borderline offensive. 

This thread is being merged into an existing authoritative thread for better tracking and response. 

Keywords do not sync between Classic and the Cloud.

When I change metadata fields in Lightroom Classic, some metadata update in Lightroom Cloud and some do not. For example, changing the Title or Caption fields in Classic does propagate to Cloud but changing some other fields does not. Or rather the changes propagate to the photo that's in Lightroom Cloud but Lightroom Could does not "see". 

For clarity, let's say in Classic I change photo title, caption, and keywords from black to "Frustration". Then I update metadata in file and sync, and look at the photo in Lightroom Cloud - Title and Caption metadata updated but keywords field is till blank. But when I save the file from Lightroom Could, all 3 fields are actually updated to "Frustration". So, frustratingly, lightroom could actually gets out of sync with the actual file it stores in the could. 

This is very inconvenient because editing metadata is easier to do in Lightroom Classic, but then all that work is lost because there seems to be no way to get the Could to be aware of some of the changes. 

Apparently the LR product manager is "married" to this idea of only having minimal metadata sync capability between the two ecosystems and is oblivious to the customer base frustration, convoluted machinations, expense, and inconvenience people are going through because of this one synchronization failure point. 

Only hope seems to be if the LR Product Manager at Adobe leaves and a new person takes over who cares about what their customer base needs and want.    

Officially it's for technical reasons: in Classic, keywords are hierarchical, in cloud they are flat. But I let you judge if that's a real technical limitation or not. The other argument is: be happy with the limited cloud features classic has because it was not designed as such, if you want sync features, go with cloudy. Understand: the sync features of classic are kind a "goodie".

My personal take on this is the following: Adobe has understood the potential of cloud features linked to selling storage in addittion to a way broader market market (compared to enthusiast photographers): cell phone users and casual shooters. Maintaingin both versions of LR must also be expensive, so they have all to win to 'encourage' the migration to cloudy.

But you'll obviously never officially hear anything other than "Both version are equally important to Adobe and the dev teams are working on both versions." Up to us, users, to use our sceptical mind 😉

I have given up. I am moving from a desktop at home/laptop for the road, to a laptop for everything. It is going to be compromised for both tasks, and more expensive, but at least I will be able to keyword on the road.

it's a shame, I don't really understand what they expect to gain  with that decision. This is THE feature that I miss the most.