Skip to main content
Inspiring
October 19, 2017
Open for Voting

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

Keywords do not sync correctly: When added on the mobile app (iOS), they do not appear in LR classic and not in LR Web (I deleted the new LR CC immediately, this version does not make sense to me).
Same problem into the other direction: Keywords from LR classic do not appear on the mobile app. 
Attention: At this stage the whole keywording within the iOS app should not be used!

返信数 372

Participating Frequently
January 13, 2019
It is still possible to buy Lightroom 6 perpetual licence here in the UK but I have heard rumours that may well be the last version. Sylvain, have you seen an official Adobe announcement that the non-CC version of Lightroom will be discontinued or are you just assuming that will happen?
Inspiring
January 13, 2019
Johan Elzenga. You will not be able to buy Lightroom classic anymore. You need a plan to have it, a plan that include the cloud capabilities . A bit of consistency would be greats
andromedis
Participant
January 13, 2019
If Adobe develops something new it should make sense to its users, right? That is my expectation and it is not being fulfilled at all. What sense does it make to have two independet solutions, if one could support the other? Everybody is talking about workflow and what does Adobe deliver? Workflowinteruptions! 
Sorry for being a bit emotional here, but it is true not "only" in this instance but also cannot sync libraries from LR CC cloudversion with Adobe Portfolio both ways, neither export file names into Adobe PF. So each single one a beautifully made app but they do not function together. 
JohanElzenga
Community Expert
Community Expert
January 13, 2019
What they say is that Lightroom Classic is the desktop oriented app and Lightroom CC is the cloud oriented app. They could have (and maybe they should have) removed all sync features from Lightroom Classic, to make it perfectly clear where this app stands. I’m glad that they didn’t do that, but the result is that people keep having expectations for new or improved sync features that will not arrive.
-- Johan W. Elzenga
Inspiring
January 13, 2019
What I do not get is the attitude of Adobe, there is industrial secrets involved here. They can say something like “we want to bring all the (keys) possibilities of LR classic to CC little by little to this modern platform so nobody will need classic anymore. Therefore our focus is on making this a reality as soon as possible. The sync between classic and CC is more based on best effort.”
It would be clear for everybody.
The subscribion sheme imply a trusted partnership between us, clients and adobe.
Jerry Syder
Inspiring
January 13, 2019
I'm not so sure if this is true because they are continuously adding new features to Classic. 
Antoine HLMN
Known Participant
January 13, 2019
Exactly !

And even: at first, they said it was a technical reason. No one believed it and now it is "by design" and "Classic will not get any new sync feature" and "switch to LR CC if you want more sync capabilities".

Your statement

what they mean is "we don't want to spend any significant money on improving Classic as it will divert resources from CC development and we are trying to get people off of Classic and on to CC so why would be do something that would encourage people to stay on Classic?

is exacly right. I would also add: "Adobe wants the users to switch to cloud also because it's more difficult to migrat to another solution afterwards!"
Califdan2
Inspiring
January 12, 2019
so, let's go down the list....

1)  Keywords in CC are flat, not hierarchical as they are in Classic. 
     Okay, Keywords in a JPG file are flat as well and LR seems to be able to bridge that gap OK.  On export, LR keywords are flattened.  On import JPG keywords already present in Classic are just used on the image wherever they are in the hierarchy and any new KW's in the JPG are added to the KW list at the the root level of the hierarchy.  So, they already have the algorithm to do this

2)  Adobe would like to minimize the use of KW's in CC (IMHO) and have people rely on their AI (Sensei) engine.  So, other than not wanting to expend resources on Keywords, is not a technical reason preventing the sync of KW's.  

3) Users may not want all their Keywords from Classic to migrate to the cloud.  This is a true statement.  But, right now, in many situations when you add an image to a synced collection at already copies Classic KW's to the cloud.  And, just adding a 4th check box to on keyword's  in Classic called "Sync this Keyword in Adobe Cloud" to decide whether or not to copy and sync each keyword with the cloud.  

4)  Keyword sync is too complex for the skill level of the programmers at Adobe.  Well, this is all we are left with as a "technical" reason not to sync keywords but is absolute nonsense.  If they can figure out how to sync all the complexities of image edits, doing the same thing with Keywords is trivial.  


So, no matter what they say about "technical reasons" - what they mean is "we don't want to spend any significant money on improving Classic as it will divert resources from CC development and we are trying to get people off of Classic and on to CC so why would be do something that would encourage people to stay on Classic?

It's as simple as that.
Community Expert
January 12, 2019
The full raw syncing thing is similar to the keyword thing. I have a request here that you should add your vote to: https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-should-be-able-to-sync-full... but don't expect this to change as I think this ship sailed a long time ago. Still can't hurt to make sure they know it is something users want to see.
Inspiring
January 12, 2019
Stil do not get also why you cannot upload full raw on classic (at least linked to your catalog). I will never subscribe to CC for that, but I would subscribe to the 1To plan tomorrow if this is allowed. To sync smart previews between phone and computer the 20Go is enough.
I really do not understand this keyword limitation. Does not really make sens and the technical explanation is BS.