Skip to main content
F
FeedbackCommunityMember
Inspiring
March 6, 2018
Open for Voting

P: Sync all Ecosystem Metadata with Classic desktop version

  • March 6, 2018
  • 22 replies
  • 798 views

I do not understand why Adobe would have fields on the mobile or CC version that do not sync to desktop Classic version. Can someone please explain? I understand not pushing everything from Classic desktop to mobile/cloud version as it is too much. But FROM mobile/cloud to desktop is a must if this is truly supposed to be a portable product. Is Adobe branching into two completely different products? I can think of no other reason to program them to not sync properly from the beginning. Entered lots of location data on CC and from what I can see, it does not sync and Adobe has no plans to ever sync that metadata even though those fields already exist in Classic version. Would someone please explain WHY?

    22 replies

    Show previous replies
    F
    FeedbackCommunityMemberAuthor
    Inspiring
    March 7, 2018
    But what about the location fields? City, State, Country are identical names. Why wouldn't they sync those? It would be helpful if Adobe published a very clear listing of what does and does NOT sync. The marketing literature talks around the reality of what does NOT sync. Help and Forums do not address this thoroughly, only one issue at a time, which doesn't help me to develop a realistic workflow that incorporates using the CC versions.
    RikkFlohr: Inactive
    RikkFlohr: Inactive
    Inspiring
    March 6, 2018
    The CC versions (Lightroom CC, IOS, Android, Apple TV and Web) were designed to work seamlessly with one another.  They all contain full access to each other's data and the cloud and were built that way from the beginning. Lightroom Classic was designed as a desktop-based environment originally and had cloud access bolted on very late in its design.  Differences in the way things like Keywords are handled (Flat in CC and Hierarchical in Classic CC) is one example of reasons why it is very difficult to port metadata from one to the other. 
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices