Lightroom catalog permission problem!

Hi everyone,
please help me solve this problem. I reinstall OS X last night to new Yosemite. I did clean install. I made TM backup of my old OS X on external LaCie hdd. I copied my catalog from the backup into my pictures folder on an internal hdd. When I tried to open it this message pops up "Lightroom cannot use the catalog named “Lightroom 5 Catalog” because it is not writable and cannot be opened.". Just to be clear the "get info" permissions are set for "Me" R/W. I don't have any different file inside the folder "pictures" only my catalog.ircat. I can't open original file from the LaCie backup, also permission problem. Thanks for help.

it's all ok. The file for some reason have some info written about the owner. I did change that but it does not matter and still don't work. If I want rename the file then I have to put the password and that is why LR can't work with it. I found the solution already (after 5 hours searching the internet) This helped me http://backdrift.org/fixing-mac-osx-file-permissions-and-acls-from-the-command-line I used sudo chmod -N /here is path to the file/ and enter. This solved all my trouble and I can open the catalog without problems.

Similar Messages

Lightroom 4.3 Problem - Another Application Is Using Catalog

I recently moved all my photos and my Lightroom 4.3 Catalog onto a Drobo Mini so that I can use it easily with my MacBook Pro Laptop and my Mac Pro Desktop. Everything has been working fine for a few weeks but now I'm having a problem. When I try to open Lightroom it says it can't open my Catalog because it is being used by another application. I can't find any other application that is using the Catalog and I have shut down both computers and restarted, but still getting the same message??? Any advice on how to free up my Catalog would be greatly appreciated.
Bernie Weinzimmer
[email protected]

Cornelia-I,
I will answer your questions as best I can. About a month ago, I purchased a new MacBook Pro laptop and a Drobo Mini. I copied all my images (about 40,000) on to the Drobo Mini and also created a Drobo Mini Lightroom Catalog on the Drobo Mini and imported all the images into that catalog. Everything worked fine and I could move the Drobo Mini from the MacPro Desktop to the MacBook Pro Laptop without any problems. I use the Thunderbolt cable to connect to the laptop and a USB cable to connect to the Desktop. In the past I made sure only one cable was connected to the Drobo Mini depending upon which computer I was connecting to. A couple of days ago I believe I didn't disconnect the USB cable and didn't shut down the Drobo and just connected it to the laptop. That is when the problems began. Initially I couldn't open Lightoom from either computer connected to the Drobo. It appeared I had somehow corrupted the Drobo and I tried to use my Disk Utility on the MacBook Pro Laptop to repair it but it wasn't able to do so. I contacted Drobo support and they advised me to purchase Disk Warrior which I did and it fixed the issue with the Drobo files. Then I was able to look at the Drobo Mini and as Web Weaver suggested, there was a LR lock file on the Drobo. I moved it to the trash and I replaced the original catalog with the most recent backup, and then I was able to open Lightroom on the Desktop and everything appeared okay. Then I went over to the laptop, and the messages above about permissions showed up and I couldn't open the catalog. Rather than go back to the desktop and see if it is okay, I'm thinking first I'd like to solve the problem on the laptop if possible. I don't know how to fix the folder permissions???
Bernie Weinzimmer
[email protected]

Huge Problem When Create New Lightroom Catalog

When I created new Lightroom catalogs, I did not notice that it asks where to save it. So, it saved the catalogs in "Documents". Now it seems I have two copies of the following:
- The Lrcat files appear in Documents and on my external drive in a file labeled LRFILES
- The original raw files downloaded from the camera appears in Documents and my external drive in a file labeled ORIGINALS
I trashed the Lrcat files and the originals in Documents. I was surprised to see that the Lrcat files and original raw files ALSO disappeared (from external storage). Why, how did that happen?
I recovered the Lrcat files and original raw files and loaded them back onto the external storage. They appeared in Documents! Why, how did that happen?
I tried to relink my Lightroom pictures with the Lrcat file on the external drive. I can do it one at a time. It does not locate all the other ones even though they are all in same file, like what usually happens.
Goal is to relink all pictures with the originals on the external drive so I can get rid of the duplicate files under "Documents". How can that be done?

I don't understand why you are creating so many different catalogs. In most instances, Lightroom is much easier to manage when using a single catalog. When you use the import dialog you need to take care to specify the destination folder where you are going to download. It's all controlled in the right-hand panel of the import dialog. Ideally, you should be working with a single catalog, and choosing a destination folder on your external hard drive if that is where you want to store your images.

List of recent Lightroom Catalogs not showing in the dialog at launch

I have a friend using Lightroom 3 on a Windows 7 PC. She uses multiple catalogs. (one for each client) as do I.
Now when she launches LR the list of recent catalogs is empty. Could this be cleared some where? Why do they not show up and will they start showing up again after she opens different catalogs?
Thanks for any feedback.

If LR uses the Windows recent-files facility, and I’m not saying it does, then clearing recent documents in another area of Windows might have cleared LR’s too. A question back to her would be whether other recent-documents lists have disappeared or only the LR-catalog recent list. The recent-files would be user-profile specific, too, I think, so logging in with a different user would make things look different.
If the LR recent-library-list is something internal to LR and unrelated to the OS, then it could be part of the preferences, and if she reset preferences for any reason, then that might have cleared the catalog list.
If this is on a Mac, then I’m not sure, but I’d expect the OS has a recently-opened-files facility, too, and that such things are tied to the user.
Unless there is some permission problem or corruption that has caused them to disappear, they probably should start showing up, again. It’d be easy enough for her to check, just open LR and open a catalog, then close LR and open LR, again and see if the just-opened catalog shows in the list. If so then there’s probably nothing more to do, except not do whatever cleared the list in the first place, where we can’t really know what she did since we weren’t there.

LR 4.4 (and 5.0?) catalog: a problem and some questions

Introductory Remark
After several years of reluctance this March I changed to LR due to its retouching capabilities. Unfortunately – beyond enjoying some really nice features of LR – I keep struggling with several problems, many of which have been covered in this forum. In this thread I describe a problem with a particular LR 4.4 catalog and put some general questions.
A few days ago I upgraded to 5.0. Unfortunately it turned out to produce even slower ’speed’ than 4.4 (discussed – among other places – here: http://forums.adobe.com/message/5454410#5454410), so I rather fell back to the latter, instead of testing the behavior of the 5.0 catalog. Anyway, as far as I understand this upgrade does not include significant new catalog functions, so my problem and questions below may be valid for 5.0, too. Nevertheless, the incompatibility of the new and previous catalogs suggests rewriting of the catalog-related parts of the code. I do not know the resulting potential improvements and/or new bugs in 5.0.
For your information, my PC (running under Windows 7) has a 64-bit Intel Core i7-3770K processor, 16GB RAM, 240 GB SSD, as well as fast and large-capacity HDDs. My monitor has a resolution of 1920x1200.
1. Problem with the catalog
To tell you the truth, I do not understand the potential necessity for using the “File / Optimize Catalog” function. In my view LR should keep the catalog optimized without manual intervention.
Nevertheless, when being faced with the ill-famed slowness of LR, I run this module. In addition, I always switch on the “Catalog Settings / General / Back up catalog” function. The actually set frequency of backing up depends on the circumstances – e.g. the number of RAW (in my case: NEF) files, the size of the catalog file (*.lrcat), and the space available on my SSD. In case of need I delete the oldest backup file to make space for the new one.
Recently I processed 1500 photos, occupying 21 GB. The "Catalog Settings / Metadata / Automatically write changes into XMP" function was switched on. Unfortunately I had to fiddle with the images quite a lot, so after processing roughly half of them the catalog file reached the size of 24 GB. Until this stage there had been no sign of any failure – catalog optimizations had run smoothly and backups had been created regularly, as scheduled.
Once, however, towards the end of generating the next backup, LR sent an error message saying that it had not been able to create the backup file, due to lack of enough space on the SSD. I myself found still 40 GB of empty space, so I re-launched the backup process. The result was the same, but this time I saw a mysterious new (journal?) file with a size of 40 GB… When my third attempt also failed, I had to decide what to do.
Since I needed at least the XMP files with the results of my retouching operations, I simply wanted to save these side-cars into the directory of my original input NEF files on a HDD. Before making this step, I intended to check whether all modifications and adjustments had been stored in the XMP files.
Unfortunately I was not aware of the realistic size of side-cars, associated with a certain volume of usage of the Spot Removal, Grad Filter, and Adjustment Brush functions. But as the time of the last modification of the XMP files (belonging to the recently retouched pictures) seemed perfect, I believed that all my actions had been saved. Although the "Automatically write changes into XMP" seemed to be working, in order to be on the safe side I selected all photos and ran the “Metadata / Save Metadata to File” function of the Library module. After this I copied the XMP files, deleted the corrupted catalog, created a new catalog, and imported the same NEF files together with the side-cars.
When checking the photos, I was shocked: Only the first few hundred XMP files retained all my modifications. Roughly 3 weeks of work was completely lost… From that time on I regularly check the XMP files.
Question 1: Have you collected any similar experience?
2. The catalog-related part of my workflow
Unless I miss an important piece of knowledge, LR catalogs store many data that I do not need in the long run. Having the history of recent retouching activities is useful for me only for a short while, so archiving every little step for a long time with a huge amount of accumulated data would be impossible (and useless) on my SSD. In terms of processing what count for me are the resulting XMP files, so in the long run I keep only them and get rid of the catalog.
Out of the 240 GB of my SSD 110 GB is available for LR. Whenever I have new photos to retouch, I make the following steps:
create a ‘temporary’ catalog on my SSD
import the new pictures from my HDD into this temporary catalog
select all imported pictures in the temporary catalog
use the “File / Export as Catalog” function in order to copy the original NEF files onto the SSD and make them used by the ‘real’ (not temporary) new catalog
use the “File / Open Catalog” function to re-launch LR with the new catalog
switch on the "Automatically write changes into XMP" function of the new catalog
delete the ‘temporary’ catalog to save space on the SSD
retouch the pictures (while keeping and eye on due creation and development of the XMP files)
generate the required output (TIF OR JPG) files
copy the XMP and the output files into the original directory of the input NEF files on the HDD
copy the whole catalog for interim archiving onto the HDD
delete the catalog from the SSD
upon making sure that the XMP files are all fine, delete the archived catalog from the HDD, too
Question 2: If we put aside the issue of keeping the catalog for other purposes then saving each and every retouching steps (which I address below), is there any simpler workflow to produce only the XMP files and save space on the SSD? For example, is it possible to create a new catalog on the SSD with copying the input NEF files into its directory and re-launching LR ‘automatically’, in one step?
Question 3: If this I not the case, is there any third-party application that would ease the execution of the relevant parts of this workflow before and/or after the actual retouching of the pictures?
Question 4: Is it possible to set general parameters for new catalogs? In my experience most settings of the new catalogs (at least the ones that are important for me) are copied from the recently used catalog, except the use of the "Catalog Settings / Metadata / Automatically write changes into XMP" function. This means that I always have to go there to switch it on… Not even a question is raised by LR whether I want to change anything in comparison with the settings of the recently used catalog…
3. Catalog functions missing from my workflow
Unfortunately the above described abandoning of catalogs has at least two serious drawbacks:
I miss the classification features (rating, keywords, collections, etc.) Anyway, these functions would be really meaningful for me only if covering all my existing photos that would require going back to 41k images to classify them. In addition, keeping all the pictures in one catalog would result in an extremely large catalog file, almost surely guaranteeing regular failures. Beyond, due to the speed problem tolerable conditions could be established only by keeping the original NEF files on the SSD, which is out of the question. Generating several ‘partial’ catalogs could somewhat circumvent this trap, but it would require presorting the photos (e.g. by capture time or subject) and by doing this I would lose the essence of having a single catalog, covering all my photos.
Question 5: Is it the right assumption that storing only some parts (e.g. the classification-related data) of catalog files is impossible? My understanding is that either I keep the whole catalog file (with the outdated historical data of all my ‘ancient’ actions) or abandon it.
Question 6: If such ‘cherry-picking’ is facilitated after all: Can you suggest any pragmatic description of the potential (competing) ways of categorizing images efficiently, comparing them along the pros and contras?
I also lose the virtual copies. Anyway, I am confused regarding the actual storage of the retouching-related data of virtual copies. In some websites one can find relatively old posts, stating that the XMP file contains all information about modifying/adjusting both the original photo and its virtual copy/copies. However, when fiddling with a virtual copy I cannot see any change in the size of the associated XMP file. In addition, when I copy the original NEF file and its XMP file, rename them, and import these derivative files, only the retouched original image comes up – I cannot see any virtual copy. This suggests that the XMP file does not contain information on the virtual copy/copies…
For this reason whenever multiple versions seem to be reasonable, I create renamed version(s) of the same NEF+XMP files, import them, and make some changes in their settings. I know, this is far not a sophisticated solution…
Question 7: Where and how the settings of virtual copies are stored?
Question 8: Is it possible to generate separate XMP files for both the originally retouched image and its virtual copy/copies and to make them recognized by LR when importing them into a new catalog?

A part of my problems may be caused by selecting LR for a challenging private project, where image retouching activities result in bigger than average volume of adjustment data. Consequently, the catalog file becomes huge and vulnerable.
While I understand that something has gone wrong for you, causing Lightroom to be slow and unstable, I think you are combining many unrelated ideas into a single concept, and winding up with a mistaken idea. Just because you project is challenging does not mean Lightroom is unsuitable. A bigger than average volume of adjustment data will make the catalog larger (I don't know about "huge"), but I doubt bigger by itself will make the catalog "vulnerable".
The causes of instability and crashes may have NOTHING to do with catalog size. Of course, the cause MAY have everything to do with catalog size. I just don't think you are coming to the right conclusion, as in my experience size of catalog and stability issues are unrelated.
2. I may be wrong, but in my experience the size of the RAW file may significantly blow up the amount of retouching-related data.
Your experience is your experience, and my experience is different. I want to state clearly that you can have pretty big RAW files that have different content and not require significant amounts of retouching. It's not the size of the RAW that determines the amount of touchup, it is the content and the eye of the user. Furthermore, item 2 was related to image size, and now you have changed the meaning of number 2 from image size to the amount of retouching required. So, what is your point? Lots of retouching blows up the amount of retouching data that needs to be stored? Yeah, I agree.
When creating the catalog for the 1500 NEF files (21 GB), the starting size of the catalog file was around 1 GB. This must have included all classification-related information (the meaningful part of which was practically nothing, since I had not used rating, classification, or collections). By the time of the crash half of the files had been processed, so the actual retouching-related data (that should have been converted properly into the XMP files) might be only around 500 MB. Consequently, probably 22.5 GB out of the 24 GB of the catalog file contained historical information
I don't know exactly what you do to touch up your photos, I can't imagine how you come up with the size should be around 500MB. But again, to you this problem is entirely caused by the size of the catalog, and I don't think it is. Now, having said that, some of your problem with slowness may indeed be related to the amount of touch-up that you are doing. Lightroom is known to slow down if you do lots of spot removal and lots of brushing, and then you may be better off doing this type of touch-up in Photoshop. Again, just to be 100% clear, the problem is not "size of catalog", the problem is you are doing so many adjustments on a single photo. You could have a catalog that is just as large, (i.e. that has lots more photos with few adjustments) and I would expect it to run a lot faster than what you are experiencing.
So to sum up, you seem to be implying that slowness and catalog instability are the same issue, and I don't buy it. You seem to be implying that slowness and instability are both caused by the size of the catalog, and I don't buy that either.
Re-reading your original post, you are putting the backups on the SSD, the same disk as the working catalog? This is a very poor practice, you need to put your backups on a different physical disk. That alone might help your space issues on the SSD.

Can I move the Lightroom Catalog from one location to another?

Lightroom by default, places the Lightroom Catalog in the Pictures folder on my PC. My image library though, is located on an external hard drive. I've read that it is better to have the Catalog at the same location to avoid disconnected images, which sounds reasonable. Is it feasable to move the Catalog over to the same drive as my image library, or will that cause a problem? In other words would I need to start over again and create a new Catalog on the external drive? I know this sounds like a dumb question, but I've learnt to my cost that the obvious solution isn't necessary the correct one.

For better performance it is preferable to have the catalog located on an internal hard drive. By default the catalog and the preview files have to be located in the same folder since there is continual read/write taking place while working in Lightroom. Lightroom does not make any changes to the original files so its fine for them to be located on another hard drive internal or external. Lightroom loves lots of hard disk space to operate so if your catalog is on an internal drive make sure it not starved for disk space.
However its ok for your catalog/previews files to reside on an external HDD with your original photo files.
Your photo files can reside on a HDD conected to a network but your catalog and preview files cannot be located on a network.
e.g I have my catalog / previews on the main HDD with my operating system with over 50% free disk space. My Photo files are on a secondary internal HDD with over 75% free disk space. I back up to external HDD.

"Lightroom has encountered problems reading this photo."

***** UPDATE July 17, 2013 @ 9:16 am Central Time (UTC -06:00)*****
After Creating a fresh catalog I have been able to clarify the issue a bit. This error appears to only show up in Folders exported as Catalogs. Particularly when I try and open that exported catalog.
I suspect there is a problem with the way Lightroom 5 is exporting these catalogs. I didn't have this issue with LR4.4, but it shows up any time I export a folder as a catalog within LR5, regardless of whether or not it is exported from an upgraded catalog or a fressly created catalog.
It looks like fixing the problem is going to be time consuming, but not impossible. So far I have confirmed that these files - reported as throwing this error by Lightroom 5 ("Lightroom has encountered problems reading this photo .... You will not be able to make adjustment to this photo.") - can be imported into a new/existing catalog by multiple methods without carrying over the errors displayed in the exported catalog.
This is frustrating and adds additional steps to my workflow, but isn't undoable. Of course it would be nice if LR5 worked as correctly and exported folders as catalogs without throwing errors when those new catalogs were opened...
Is anyone else seeing this problem when they open catalogs created by "exporting a folder as a catalog"?
***** Original Post *****
I'm really confused. I am consistently getting this message on certain exports, but not others...
When it happens:
1) "Export this Folder as a Catalog" from a specific folder within my Working Catalog
Select the location
Select "Export negative files"
When I open the NEW Catalog - ALL the photos reflect this error message: "Lightroom has encountered problems reading this photo .... You will not be able to make adjustment to this photo."
When I go to the Develop tab it displays "There was an error working with the photo" over the photo, but I can edit it... When I close the catalog and re-open it, the changes don't reflect UNTIL I go back to the Develop tab, then the thumbnail will reflect the change. But the system still insists that it has a problem with the file...
2) The same thing happens when I export the file from my Working Catalog as an image of the same format - be it tif, dng, or psd, or RAW files. Not sure what I was refering to here (can't duplicate today - July 17).
When it doesn't happen:
When I export the file to the auto import folder for my Portfolio catalog (original format). This seems to work...
Why am I so confused? Because all of these catalogs are located on the same drive (which is different than the drive my Working Catalog is on). When they are auto imported to my Portfolio catalog they seem to work, but everything else throws an error sinse I upgraded to LR5!
My System:
Windows 7 Pro SP1 (fully up to date) 64-bit
Intel Core i7 CPU 950 @ 3.07GHz
Installed RAM: 12.0 GB
My Lightroom 5 Working Catalog doesn't seem to be having any problems...
This problem is frustrating enough that I may go back to LR4. I can't have my archived files compromised...

Suggestion to all who encounter problems like this: if you've installed 3rd party memory cards (ram), go back to your original ram, or at least the brand of ram that your computuer came with.
Long story, short:
I had the same error message in LR5. It only happened with several images in a given import. If I deleted all of the images from the import and reimported the images, a different set of images would have the error message. The images that originally had the message would no longer have the problem. I deleted and reimported several times while observing the same behavior.
Not only did lightroom give me issues, but Bridge had problems reading the files, and the previews of the problem images would not show up in Finder (Mac speak). This ruled out, to me at least, that it was a software issue. I went out and purchased a new card reader and had the same problems. I tried a different card with different images and got the same problems.
After I contacted Adobe, they had me upload two files with the error, and they said the files were corrupted due to faulty hardware. I took my mac book pro (13in early 2011 w/ 10.7.5) to the apple store and they ran a diagnostic test amoung other test and we came up with nothing. Everything seemed to be good on the hardware side. After some research the Rep. asked me about my ram (memory cards). I had in the past installed two 3rd party cards to boost my ram from 4GB to 8GB. The rep. suggested that I go home and test the issue with the original ram my computer came with before we go any farther. So far, I haven't had any issues.
I hope this helps,
Josef

Shared Lightroom Catalog???

I use Lightroom exclusively for my photos.   I initially used it with my desktop Mac (PowerPC G5) and then started using it also on my laptop (Macbook Pro). Both computers have all photos on external drives. There is a separate Lightroom catalog on each computer corresponding to each computer with it's individual external drive.   You can imagine my problem now, I'm sure. I have, effectively, TWO Lightroom catalogs, each with unique images, but also I've copied some photos over between them. The problem is growing exponentially.
Here's what I'd LIKE to do.   I'd like to install a shared NAS drive (perhaps an Apple Time Capsule drive) on my central hub in my house (my whole house is wired for Ethernet so that's not a problem), then put all photos on that single hub, thereby using a single Lightroom catalog and with it's images from either computer. If I have to travel somewhere and take some photos with me, I can deal with that because that it is typically the exception, not the rule.
Has anyone tried to do this?   I don't need to nor expect to hit the shared catalog from both computers at the same time. I'll be using one or the other, but not both. But I'd like to bring these two environments together.
I'd love some insight from forum members who've attacked this problem and solved it. I just don't know if Lightroom will allow the catalog to be on a shared drive, thus accessed by either computer.    If it will, then I imagine the work I need to do is:
1)     create a large shared NAS drive.
2)     copy all images to that drive.
3)     pick one of the two Lightroom catalogs and make that the master and somehow point it to the NAS drive.
4)     import the remainder of the photos on the NAS drive to Lightroom.
5)     make sure that both computers reference the Lightroom catalog on the NAS drive.
or maybe not. Maybe there's a better way. I'd like your input.
if this won't work, then has anyone successfully merged two Lightroom catalogs together.   One of my catalogs has about 80,000 images, and the other about 35,000 images.   At least 50% of all images are keyworded and I'd really hate to lose my keywords and collections that I've created.
anyway, insight is welcome. Tell me if I'm nuts too.
Thanks in advance.
Dennis

The closest think to this that will work is to put all the images on a large Firewire 800 drive with the LR catalog on the same drive, possibly in another partition. And alternately plug the drive into one machin or the other.
It is Networked drives where one can't put a Catalog, as John says.
Don

Importing into lightroom catalog on a mac

I just moved my lightroom catalog on an external drive to a mac from a pc. I got the entire catalog moved with no issues or problems except for this. When I try to import new photos i get a message saying that the file cannont be read and that the files were not imported. Has anyone else run into this issue while using a mac? Thanks for any help

How did you format the external drive? It needs to be FAT32 if you want it to be able to be read and written by both PC and Mac. Sometimes when LR says "cannot be read" it also or instead means "cannot be written".
John
John G. Blair Studio
Occidental, California

Lightroom catalog maintenance question.

The Lightroom catalog is a convenient feature that allows changes to photographs without making changes to the original picture.
I have had problems when I have to reorganize folders and files in Windows. If I rename a folder in Windows I damage the path to the pictures and I lose the Lightroom catalog.
I have a very dynamic set of image files that have to be created and filed away (deleted) very frequently and the stability of the Lightroom catalog seems to be in the way. Maintenance of the Catalog feels like an extra burden.
What is the best way to repair (modify) the Catalog links to the Windows files when they have been deleted or renamed?
Thanks in advance.
Al

You can change the links via
http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm
I have a very dynamic set of image files that have to be created and filed away (deleted) very frequently and the stability of the Lightroom catalog seems to be in the way.
Most people don't delete photos once imported into LR, and everything works very smoothly. Once the photo is imported, leave it in Lightroom. Saves you some work.
Furthermore, the idea of importing the photos to a certain location, working with the photos and then moving the photos somewhere else might make sense in your operating system, but in Lightroom this is an extra step with no obvious benefits (in my opinion). Better would be to import the photos to their destination, and not perform the two-step Move to Folder A followed by Move to Folder B.
By the way, I hope you understand that if you delete photos from Lightroom (but not from your hard disk), your edits may not stay with the actual photos. By default, the edits and other metadata are not stored with the photo files.
And as John said, an organization scheme that uses keywords and other metadata will be far superior in the long-run than moving photos from folder to folder and location to location.

Lightroom catalog not complete

I'm in a bit of a pickle. Yesterday I installed OSXC yosemite on my iMac 2013. Prior to doing this I opened lightroom and backed up my catalog, which is stored along with all my pictures on an external thunderbolt drive.
I installed yosemite clean, meaning I formatted my hard drive. installed lightroom and told it to open my catalog which is on the external.
the problem is when it opened, it was missing about 6 months of work and files?? it was not up to date??
i right click on the folder and tell it to synchronize. so indeed all files are there but the main issue is all those presets, changes i made to each file are gone.
it means I now have to redo all the work on the original files, cropping, exposure and all that.
is there a way to get it all back?
why did it not pickup exactly where it left off - which is what i expected
any help is very much appreciated as I've lost over 6 months of work
again, files all seem to be intact but the actual work done to the image is gone.

When i open lightroom, prior to installing and updating to yosemite, it would open the catalog stored on the external drive.
the date on that file is 10-17-2014, thus current.
my lightroom catalog is stored on the external drive, same place where all my pictures are.
as for backups, they are identical, same issue.
i dont understand why lightroom when opening my catalog on 10-17 was fine but when i update to yosemite and open exact same catalog its missing 6 months of information, despite the fact date on catalog is 10-17 and is same file on same location on an external drive.
i tried a backup file and same thing.

Lightroom Catalog is Huge

I have 129,980 in my lightroom catalog. The photos go back to January 2000 and are only about 350GB but this previews file is over 116GB. This seems excessive.
Is the alternative to simply take a moment to build previews when I go to a folder? Most of my folders are pretty small.

PictureTakerGuy wrote:
My concern is both wasted space and disk overhead. 120GB seems like a high percentage of overhead for a 350GB collection. Especially when I consider I might never edit many of the photos there.
If you've got a number in mind that's too much, then there's a problem.
Many people don't worry until there's a performance issue, in which case it doesn't sound like there's a problem.
I'm coming from ACDSee world where there was little overhead and blazing fast photo thumbnails created when you went into a directory.
How would I do same in LR. I like LR and I'm not trying to bash it. I just don't feel comfortable with the amount of wasted space where I need to back it up, etc.
You need to understand that these are two very different programs which operate under very different principles. If you want the fastest performance out of Lightroom, then I think you want to have the largest possible previews, and they are left on your hard disk forever and beyond.
When I run WinDirStat it takes forever to even figure out how many files are in that catalog. It takes less time to get the pictures counted than the catalog or preview files.
Time it takes WinDirStat to finish? Hmmm ... I have never seen anyone complain about that before. Seems like you are inventing a problem. Lightroom is designed to produce a lot of preview files.

Shared Lightroom catalog with Mac OS X Lion

I keep my Lightroom catalog on my Macbook Pro so I have access to my pictures while travelling. But for editing, I use a desktop PC running Lightroom on Windows 7 on the same catalog. My process for doing this is:
On the Mac, enable SMB sharing.
On Windows, mount the SMB share.
On Windows, use "subst" to map the SMB share to a new drive root.
(This avoids Lightroom's spurious error about not supporting network volumes.)
On Windows, launch Lightroom and open the catalog on the mapped drive.
This worked in Snow Leopard. But after upgrading to Lion, Step 4 gives me an error:
Lightroom cannot use the catalog named "Lightroom 3 catalog" because it is not writable and cannot be opened.
This could be caused by incorrect permissions or because another Lightroom application is using the catalog. You may try to correct the problem or you may select a different catalog.
Permissions seem OK: I can edit the catalog and the Previews.lrdata folder in Windows Explorer. And I see no stray .lrcat.lock file that might prevent it from opening the catalog.
The Mac version of Lightroom can open the catalog just fine, so I suspect Lion's new SMB implementation broke this somehow.
Has anyone got a shared Lion -> Windows catalog to work?

OK, I found a solution. The following page describes how to manually install an SMB implementation (Samba) that actually works. It requires installing Xcode from the App Store, installing MacPorts, and some command-line tinkering to configure Samba:
http://forums.sonos.com/showthread.php?t=24022
Once you've done that , follow the instructions in this post to create launchd entries that will start Samba at boot time:
http://forums.boxee.tv/showpost.php?p=205428&postcount=48
More details are here if you run into trouble:
http://forums.boxee.tv/showthread.php?t=38629
While I can now access my LR library again from Windows, this is just the latest in a series of annoying bugs with OS X Lion. I am not a happy camper— but I'll save that for the Apple forums.

Network Lightroom Catalog

Is there anyway to network a Lightroom Catalog as I work with both a desk top and Wacom tablet

That is probably one of the most requested features that we see. But, unfortunately, isn't possible. Some people resolve the problem by putting the catalog in a dropbox folder. Another alternative is to put the images and the catalog on an external drive. I can't give you any details about the dropbox idea because I've never tried it. Using an external hard drive has worked well for me in the past. But Lightroom does not support the catalog being on a network drive.

How to reconcile 2 lightroom catalogs in separate locations along with images and metadata?

I split my time between two locations where I need access to all of my images and lightroom catalog... I've been trying to keep everything in sync by transporting new images on hard drives, exporting new updates to a "migration" catalog and then importing that along with the images when I travel back to the other location. This works as long a I don't get lazy, or in a hurry... which I have, of course and now I need to get everything back in order--as best as can be expected.
What would be the best way to do this? I need to migrate changes in both directions... If it was just location A to B, or B to A, then that's not much of a problem. unfortunately, i need to reconcile changes from A to B and B to A...
I learned my lesson, but I still need to resolve this mess.
Any tips appreciated.
Thanks.
kb

Try using the keyer and see if you can pull the blown sky. You should be able to get something acceptable,

Lightroom catalog permission problem!

Similar Messages

Maybe you are looking for