Welcome! Login here or Register for exclusive content.
And exactly how does it benefit a user who can't see the tags?Well, there are tags applied by the AI. It's just that Adobe can see them but you can't! The search is the less intelligent element.
And exactly how does it benefit a user who can't see the tags?
There is good chance the Tags aren't even human readable so may not be much use too you anyway.
It seems wrong, then, to even call this "tagging". It's really just some kind of intelligent search, isn't it?
This appears to be incorrect (as of today?).Keywords do not sync between LR Classic (and LRCC2015 before it) and the Adobe cloud. Never did, and I suspect never will.
I did. That last sentence refers to "Adobe Cloud end-points of LRCC and LRmobile", which is different from "LR Classic (and LRCC2015 before it)". Otherwise Jim's two statements would be contradictory, which they are not. Just that the first statement seems to be incorrect.Read the last sentence of the post you quoted.
John, thanks for your input. If anything I am getting more confused. I have raw files (.arw files), dng files, and tif files, ALL of which are showing keywords on LRWeb. But it turns out I also have raw files, dng files, and tif files for which keywords are NOT displayed. I don't understand the difference. And, you are (I think) saying there should be no keywords shown for any raw files, but I clearly see them on at least some of my raw file photos.I hope this helps clarify the mess..... When photos are initially synced from "Classic", keywords are read by Adobe's cloud if they have already been written into the file's internal xmp (not sidecar).
So take one raw file and one DNG/TIF/JPEG and add keywords, then save the metadata back to the files. Sync both files and you'll find that the raw file's keywords haven't synced, the DNG's have.
This is a one off thing. Subsequent keyword changes fail to sync to / from "Classic".
John
Let's clarify what we mean by "syncing". In this context I am talking about changes made in one app being applied to the same image held in a different app, and vice versa. So if an image is held in the sync ecosystem, and a change is made at one point (e.g. LRmobile), does that change then get applied to the same image as reflected in another point (e.g. LR Classic if it's sync-enabled)? Changes to Edits do, Titles do, Captions do, Keywords don't in this particular case, because keywords do not sync between the ecosystem and LR Classic. Keywords will, however, sync between e.g. LRmobile and the new LRCC, and at the moment they will appear also in LRWeb, but I don't think you can yet make keyword changes in LRWeb.At the minimum, have we disproved the oft-repeated claim that keywords don't sync from "Classic"? You are saying they will sync under certain conditions, correct? (Even though I don't understand yet what those conditions are ... I haven't had time to experiment with new images, so far I have only been looking back at my older, already uploaded, images.)
I have always treated my NEFs as effectively "read only," and used sidecars (I believe invented by Adobe) to capture metadata, edit changes etc. I have never seen the need to convert the NEFs to DNGs. I know Adobe is championing the DNG format, but that does mean that they deliberately ignore the needs of people who still use NEFs and CR2s?I hope this helps clarify the mess..... When photos are initially synced from "Classic", keywords are read by Adobe's cloud if they have already been written into the file's internal xmp (not sidecar).
So take one raw file and one DNG/TIF/JPEG and add keywords, then save the metadata back to the files. Sync both files and you'll find that the raw file's keywords haven't synced, the DNG's have.
This is a one off thing. Subsequent keyword changes fail to sync to / from "Classic".
John
I have always treated my NEFs as effectively "read only," and used sidecars (I believe invented by Adobe) to capture metadata, edit changes etc. I have never seen the need to convert the NEFs to DNGs. I know Adobe is championing the DNG format, but that does mean that they deliberately ignore the needs of people who still use NEFs and CR2s?
And a one-off sync only?
These details are very user-hostile and unintuitive. For me the list of reasons to stay with Classic just keeps getting bigger and bigger.
I know Adobe is championing the DNG format, but that does mean that they deliberately ignore the needs of people who still use NEFs and CR2s?
And a one-off sync only?
All of this applies only if you want to attempt a combined Classic and LRCC workflow, which frankly I'd advise most people against at this stage (or at least proceed with caution). With an LRCC-only workflow (which is probably how it was intended/designed to be used), even total IT novices will be able to cope...it really is not that complicated.@Johan and @johnbeardy, Thanks for correcting my misunderstanding.
But I will say this. Properly done, we should not have to be concerned about such detailed rules. As someone said in another thread, what about those non-IT background people. Shouldn't these products be "intuitive," so we can use them without consulting thick user manuals?
They never really intended for people to have "a foot in both camps". Used the way it was designed, it's simple.Properly done, we should not have to be concerned about such detailed rules.