Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: huguito on October 27, 2014, 08:45:31 pm
-
I have a mess on the catalogs.
Can I delete them and start a new one fresh?
I can't find a command to delete
-
there isn't one. the catalog (.lrcat) is just a single filesystem 'file' so use whatever method your computer uses to drag the ones you want to discard to the trashcan
-
I see
So where is this folder located so I can drag it to the trash can?
-
Open the catalog, then edit>catalog settings. The dialog contains the full path to the file.
Alan
-
Thanksguys.
Find the path, erased them and started with a new catalog from scratch.
Once the catalog was created and the system start to create the previews, I chosen standard previews, seems to take a long time.
Already over 24hs for a total of about 90,000 images, most of them Raw files.
Is that a longer time than it should take? Looks like it will need just another few hours looking at the progress bar.
Is that telling me that my computer is running out of muscle and need to be upgraded to run Lightroom eficiently?
Hugo
-
Now you've got to look at 90k images and re-edit them. Sheesh! All the information about previous edits is gone.
-
Not really
I was creating the initial catalog when all the mess of multiple catalogs happened.
No edits where done in Lightroom before, all the existing edits where done in ACR and Photoshop. I understand the edits to raw file will stay unchanged as sidecar files
-
No edits where done in Lightroom before, all the existing edits where done in ACR and Photoshop. I understand the edits to raw file will stay unchanged as sidecar files
As long as you've done ZERO to your image settings, key wording, etc, that's true...but if you HAVE done anything in those catalogs, you might want to open them and save the metadata to the files–this will update the .xmp files so the next import will pick them up.
-
As long as you've done ZERO to your image settings, key wording, etc, that's true...but if you HAVE done anything in those catalogs, you might want to open them and save the metadata to the files–this will update the .xmp files so the next import will pick them up.
I have a somewhat tangential question here. Last Spring we got back from a trip and I did the usual import of images into LR. For some reason (maybe user error???) LR put everything into a new catalog. I didn't pay any attention to this and did some editing on maybe 20 or so images when I saw that none of my other images were in this catalog. It was then that I discovered that this was all part of a new catalog with only this trip's images. I know how to do an import and did so but it looks like none of the .xmp files are associated with the import as I can't see any edited images. Can someone explain how to get these .xmp edits to transfer over as I really don't want to have extra catalogs if I don't need to.
Thanks in advance.
-
Forget xmp files - they're OldThink. Open your main catalogue, and use File >Import from Another Catalog, point to the trip catalogue, and import it.
-
I have a somewhat tangential question here. Last Spring we got back from a trip and I did the usual import of images into LR. For some reason (maybe user error???) LR put everything into a new catalog. I didn't pay any attention to this and did some editing on maybe 20 or so images when I saw that none of my other images were in this catalog. It was then that I discovered that this was all part of a new catalog with only this trip's images. I know how to do an import and did so but it looks like none of the .xmp files are associated with the import as I can't see any edited images. Can someone explain how to get these .xmp edits to transfer over as I really don't want to have extra catalogs if I don't need to.
Thanks in advance.
Did you try importing from that extra catalog into your default catalog? .XMP files will not exist unless the Automatically write changes into .XMP is checked in the Catalog Settings dialog. It is off by default.
Bill
-
Forget xmp files - they're OldThink. Open your main catalogue, and use File >Import from Another Catalog, point to the trip catalogue, and import it.
That's what I did, all the images imported but none of the development instructions did.
-
That's what I did, all the images imported but none of the development instructions did.
Are you certain you pointed to the right catalogue, and that the pictures in that catalogue weren't also in the main catalogue but with more recent edits? What you might do is give these pictures a flag or label in the trip catalogue, making their edit time more recent, then try the File > Import from Another Catalogue.
-
Are you certain you pointed to the right catalogue, and that the pictures in that catalogue weren't also in the main catalogue but with more recent edits? What you might do is give these pictures a flag or label in the trip catalogue, making their edit time more recent, then try the File > Import from Another Catalogue.
Perhaps that is what happened. I think when I did the original import I didn't set the dialogue box correctly so that development settings were imported. As with everything 'user error' is the chief culprit 99% of the time! Things are fine now and the development settings are now in the main catalog. Thanks!
-
What will be the command I need to ener once edits are done to an image so the edits get attached to a file in the way sidecar files work in ACR?
So the images travel with the edits in case I move them, copy or export them?
-
What will be the command I need to ener once edits are done to an image so the edits get attached to a file in the way sidecar files work in ACR?
So the images travel with the edits in case I move them, copy or export them?
The command you want is Metadata > Save Metadata, or Ctrl S on Windows, Cmd S on Mac.
But remember that sidecars don't contain all your Lightroom work, and the right way to safeguard your work is by backing up your Lightroom catalogue. And when you move images, move them in Lightroom.
-
Thanks John
What does Lightroom do when I use "synchronize" ?
I was under the impression that was the command that got all the edits attached.
-
It checks the folder for files that haven't been recorded in the catalogue and gives you the chance to import them, and removes photos that the catalogue has recorded but which are no longer in the folder. It doesn't do any harm, but be cautious when using it.
-
The command you want is Metadata > Save Metadata, or Ctrl S on Windows, Cmd S on Mac.
But remember that sidecars don't contain all your Lightroom work, and the right way to safeguard your work is by backing up your Lightroom catalogue. And when you move images, move them in Lightroom.
It's always helpful to come across a thread like this as a refresher on how much I've forgotten on how Lightroom catalogue system works. It's just that threads like this indicate how there are so many different approaches and scenarios that get each user into LR Cat trouble I never would've anticipated or could ever have developed precautionary best practices for.
OK, John, what Lightroom work are you referring that doesn't get recorded in an xmp side car file after doing a Save (Cmd/Ctrl S) in Develop module?
-
OK, John, what Lightroom work are you referring that doesn't get recorded in an xmp side car file after doing a Save (Cmd/Ctrl S) in Develop module?
.xmp stores all image settings (including Snapshots) and keywording but doesn't store history nor collection info which is only stored in the database.
-
OK, John, what Lightroom work are you referring that doesn't get recorded in an xmp side car file after doing a Save (Cmd/Ctrl S) in Develop module?
XMP fails to save - virtual copies, pick flags, history steps, stacking, and any assignment to collections which includes usage in books or LR Mobile etc, published collection data. Sidecars are a way to communicate with other applications, but it's the catalogue that needs backing up as it contains 100% of your work.
-
Thanks for the replies, Jeff and John.
Your answers reassured I don't have to be concerned with xmp side car embedding in LR.
-
XMP fails to save - virtual copies, pick flags, history steps, stacking, and any assignment to collections which includes usage in books or LR Mobile etc, published collection data. Sidecars are a way to communicate with other applications, but it's the catalogue that needs backing up as it contains 100% of your work.
There are pros and cons for having LR write metadata into .XMP files. It takes up disk space and slows things down. However, if the catalog is corrupted and there is no backup, that metadata would prevent complete loss of one's editing work. Personally, I do have LR save the metadata to .XMP because I still use Bridge a great deal with Photoshop.
Bill
-
There are pros and cons for having LR write metadata into .XMP files. It takes up disk space and slows things down. However, if the catalog is corrupted and there is no backup, that metadata would prevent complete loss of one's editing work. Personally, I do have LR save the metadata to .XMP because I still use Bridge a great deal with Photoshop.
Bill
Just did an experiment by dragging and dropping a copy of a Raw file with saved LR 4.4 xmp edits from LR's Library Grid thumbnail layout into a Bridge CS5 image folder (not written to LR's Catalogue) and the Raw file retains the xmp icon and its LR preview in Bridge's Filmstrip thumbnail and Main preview. I realize if I open this LR edited image in ACR 6.7 I'll lose the PV2012 settings with changes of some degree to the preview.
Just wanted to see if stuff gets corrupted, freezes, crashes or I get any dialog box warnings from either Bridge or LR. So far nothing.
The only way this would work in reverse with a drag/drop from Bridge CS5 Picture folder directory into LR sidebar Library folder directory (which I've limited to a few folders to keep LR's CAT from expanding its directory to include all of my entire Mac OS Picture folder) is to invoke "Synchronize Folder..." in LR. Otherwise LR won't show it since it uses its catalogue to see folders and folder content.
Please correct me if I'm wrong and if it's NOT best practices to do this kind of moving stuff with LR.