Lightroom 5 CC: Finder vs catalogue relationship

I am unclear as to the relationship of photos in finder and in the Lightroom Catalogue. Before I begin to import my photos from Finder picture file can anyone advise me re:
1) Lightroom only contains links to photos in Finder, is this correct
2) If I delete a photo from a folder in finder will this impact the links in Lightroom
3) If I delete a complete folder from finder will this impact lightroom
4) If I stop using ever stop my subscription to lightroom and remove the software, will this impact the photos in my picture folders in finder
5) If I rename my photos upon import, does this actually change the name of the photos in my picture folder in finder or is it changed as part of the catalogue link in lightroom
Any assurances you can provide to help me understand before I import my photos would be appreciated

Thanks for the quick answer. You indicate that I should not manage my photos in finder but do it in lightroom. You also said that I should not delete a photo in finder. so...
1) If I manage in lightroom and delete a photo from lightroom, I am only deleting a link, correct? How then can I delete an actual photo
2) when I import directly from a camera and create a folder in lightroom, is that folder created in finder and is the actual photo stored in finder?
I will take your advice and manage in lightroom but just for my info, what is the impact of me deleting a photo in finder?

Similar Messages

Lightroom can't find external disk by itself

Since uprgrading to Lightroom 2 (currently 2.2) I'm having this strange problem (this is on a Macbook Pro (OSX 10.5.6).
I keep my photo's and my catalog on an external SATAlink harddrive. Often when I start Lightroom, it tells me that it can't find my catalog and gives me the option to manually browse for it. When I select my external drive, I notice that somehow there's been added a number to my external drive's name (the current name that LR uses is 'external disk 8', where the disks real name is just 'external disk'. The pattern is such that when I'll open LR tomorrow, LR will probably not be able to find my catalogue, and when I browse for it, I'll find that LR (or my OS?) has renamed my external disk to 'external disk 9'.
Also, LR hasn't been able to locate my catalogue backup folder (which is also on the external drive). I have to manually direct LR to the backup folder each time. I guess this is the same problem.
If anybody has a clue what the problem could be, I'd very much like to hear it. It's not a huge problem to browse for the external disk when LR starts, but it's anoying nevertheless...
Richard

Richard-
Delete your Prefs file, always make sure your external is mounted before launching LR, then launch by double clicking on the proper .lrcat file. I'd frankly change the name of my external. as anything that even looks like a default name is a no-no in my book.

Lightroom can't find file - very strange behavior

I really do like working with Lightroom (2.4), even though it has several annoying characteristics (including its speed relative to Lightroom 1). But I haven't encountered anything that is as strange as this:
I sometimes will open a collection intending to select an image in order to print it, or edit it, and the intended image bears a banner announcing that "The file named "[name of image/file]" is offline or missing." I right click on the image and select "Show in Finder" and I get an alert box that says, "The photo '[name of file]' could not be used because the original file could not be found. Would you like to locate it?" Below that it says, "Previous location: ..."
("Previous location:" is followed by the original path to the file.)
Up to this point, what I have described is no different than a missing file problem described here by other users. I hope the rest of this isn't too confusing; please bear with me.
If I click the "Locate" button in that alert box, I am taken to a folder somewhere in the middle of the hierarchy described in "Previous location." If I do a search for the named file (via my iMac's file search function), I find that the actual file is in the folder shown at the end of the folder hierarchy, exactly where Lightroom says it last found it. But Lightroom won't take me all the way there.
On closer inspection, I see that the folder (as shown in "Previous location" not the actual folder) that FOLLOWS the folder to which "Locate" takes me (this is an actual example from today) is called "desktop 12:09" -- but no such name could have been used, colons not being permitted in file names. I follow the path shown in the alert box as I navigate through the actual folders. When I get to the folder one level up from "desktop 12:09" (that is, the folder to which "Locate" will take me - and yes, I could have started there, but chose to follow the entire path for purely academic reasons), I see that there is a folder called "desktop 12/9". Inside that folder is the next folder shown in the hierarchy previously referred to.
Further down in the hierarchy there are two more folders with colons rather than slashes in their names, but of course the actual folders are named with slashes. Lightroom appears to have substituted the colons for the slashes, for some reason (or lack of reason) and now can't find the file.
I did navigate down (through Lightroom) to find the original, but had to copy the path into a text editor so I could follow it. Alas, this particular file was located many layers down. Other images that have been lost track of by Lightroom (also colons in the folder names) luckily were closer to the surface.
I do regular computer maintenance, Lightroom backups, catalog integrity checks, etc. Does this make any sense at all to anyone? I can't figure where Lightroom would have gotten those colons.
I'd love to figure this out, not just for my own curiosity, but because the process of locating the files via Lightroom is quite time consuming.
Thanks.
Leonard
p.s.: I am using an iMac (1.9 GHz G5 processor), OS X (10.4.11), 2.5 G RAM
[Screen name, lkajsdt, created by randomly pressing keys. The registration system would not accept any sensible pseudonym I tried.]

Thanks, John,
I had a suspicion that the slashes might somehow be implicated, but all of the other folders in the hierarchy (as shown in Lightroom's alert box) that have dates in their names have slashes which were not somehow converted to colons (I do not use colons, nor will the Mac allow me to use them; this was all LR's doing). When actually navigating down to the file via Lightroom, not the Finder, the offending folder(s) appear with slashes, not colons -- exactly as they appear in the Finder. Where Lightroom gets the colons, I don't know, especially since they do not appear when I am navigating through the path VIA Lightroom.
I'll work with it again later. I just caught your message on my way out the door. Thanks again for your thoughts.
L.

Old Problem/New Problem: Lightroom can't find file, then finds, but won't edit it.

(Lightroom 2; Macintosh G5; OS X (10.4.11))
First, the old problem which, though unresolved, is here mostly for background:
A little over a month ago, I posted a question (at http://forums.adobe.com/thread/480423?tstart=0 ).
The short version of that problem is that certain previously accessible images were not able to be opened in Lighroom. The preview image appeared in the main window accompanied by this message across the top of it:
"The file named "[name of image/file]" is offline or missing."
When I right clicked on the image and selected "Show in finder" I got this message:
"The photo '[name of file]' could not be used because the original file could not be found. Would you like to locate it?"
Below which was shown the original path to the file. In the middle of that path, one or more folders appeared with colons in their names in place of the slashes originally part of the names (some folders have dates in their names). Following the path via the Finder, the file was exactly where it was supposed to be, although, of course, slashes appeared instead of the colons that were in the Lightroom summary of the original path, but Lightroom couldn't find them.
I was convinced that Lightroom was renaming the folders (but only in its interface; the original folders had correct names in the finder -- which is the only way they could have been named, since colons are illegal characters and won't be accepted as part of a file name). But I see now that there is some weird thing going on in the Finder itself. Even though I see the correct name on a folder when I search for it, or navigate through the hierarchy, if I click on the file at the end of that hierarchy (the file that Lightroom said it couldn't find) and ask for file info (via Command - I, or other method), the path to that file shows colons where slashes should be, but only in the names of the folders that were so named in Lightroom. All other folders with slashes in their names are listed correctly. So it's a Finder problem. Though this is still a mystery, I have been able to work around the problem. But how is this happening? (Note that I will be reformulating the question and posting it on the Apple discussion groups soon; I don't expect this forum to deal with Apple system issues. Just thought that others here may have had the same problem.)
Now, the new problem, possibly related to the old one:
In the same collection where I noted the previous problem, I selected an image that I wanted to print. The preview came up with this message:
"The file could not be found."
But when I right click on the image and select "Show in finder" it opens the correct Finder window with the file in question highlighted. The file, a TIFF, opens normally in Preview or Photoshop.
So why does Lightroom think it's not there? (even though it can show me exactly where it is)
I have edited this photo in Lightroom before. I have printed it from Lightroom before (as shown in the Lightroom history). But today it can't be edited, won't print and "could not be found"!!!
I know I can print from Photoshop, or re-import this photo into Lightroom (along with any others that Lightroom "can't find"), though both would require time and re-editing the original. I would rather understand (if that's possible) why this is happening in the first place, so hopefully I can avoid such wackiness in the future.
I realize that may have to burn some sage and hire a Shaman, but any ideas that won't smoke up the house or scare the cats would be most welcome.
Thanks for reading.
Leonard B.

If you have an old goat around that's not doing so well, consider the sacrifice.
The one thing that occurs to me besides the Gremlin, is the use of colons or slashes or some other character that the OS or LR doesn't like in some file name or other. I think you'd have to change same in Finder, then show LR where the images are.

I just got a new Mac Mini, and now when I try to import photos into Lightroom, iPhoto try to load them first, then Lightroom can't find the files. Big problem. What to do?

I just got a new Mac Mini, and now when I try to import photos into Lightroom, iPhoto ties to load them first, then Lightroom can't find the files. Big problem. What to do?

Simple:
File -> Export to get your photos out of the iPhoto Library. In the Export dialogue you can set the kind to Original and you'll get back exactly what you put in.
Apps like iPhoto2Disk or PhotoShare will help you export to a Folder tree matching your Events.
Once exported, you can then trash the iPhoto Library - just drag it from the Pictures Folder to the trash and empty it.
After that, if you're entirely neurotic about it, just put the iPhoto app in the trash and empty it.
Regards
TD

Lightroom V3 unable to import catalogue due to unknown error

Mac OS X 10.6.4
I have Lightroom V2.6 and V3 beta 2. I have just purchased Lightroom V3 upgrade.
I installed Lightroon V3 and upon first start up imported my V2 catalogue (only one catalogue on V2 exists) - this has worked fine.
I also have a single catalogue on V3 beta 2 that I need to import.
V3 began importing Lightroom catalogue V3 (beta 2) but stopped with the following message:
Lightroom could not import this catalogue because of an unknown error.
I understand from trawling these forums that Lightroom V3 may have a bug in relation to importing duplicate files from previous catalogues but in my case I cannot see any files or folders that have been imported from Lightroom V3 beta 2 - the majority of the folders or files catalogued in V3 beta 2 have never been catalogued in Lightroom V2.
Any ideas for a fix?

It'sa bug. Duplicate folders prevent the import. You'll have to wait for 3.1 along with the rest of us.
The folks at Adobe know about it, but you can file a bug report if you wsh.

I have move all Pic to new drive, lightroom can't find PSD pictures?

I have moved all pictures and LRCAT to new drive, Lightroom can't find any PSD pictures? Is this a problem with Lightroom?

1. I exported all pictures using export as a catalog to a new external hard drive. I’m using lightroom 5. The file was large. I have about 3000 missing pictures after to import to new drive. sing find, I try to find the pictures. I discovered that lightroom could not find any pictures with .PSD extension. I would go to the prior drive and do a search using window explorer, I would find the picture with the PSD extension and go back to “find” again, I would get to the correct folder and Lightroom would say there were no pictures in the folder. I’m using the “!” on the corner of the missing picture to start the “ find” and I work backwards until I find the correct folder that I identified using windows exployer. Normally this process works great. Suggestions?

Lightroom can't find PSCS3 as an external editor

I recently upgraded to CS3. Now Lightroom can't find PS as the perferred external editor. I have tried a clean install. What gives?

Sorry, wrong FAQ. Try
LR Extras FAQ Compatibility Issues.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

Lightroom can't find photoshop.exe

Lightroom hadn't find photoshop. So Str+E is not possible. How can I solve this problem?

Have a look at this link from Adobe : http://kb.adobe.com/selfservice/viewContent.do?externalId=kb401629&sliceId=1<br /><br /><[email protected]> schreef in bericht news:[email protected]..<br />> Lightroom hadn't find photoshop. So Str+E is not possible. How can I solve this problem?

Find parent/child relationships At More Than 2 Levels

Hello,
Does anyone have a solution to find parent/child relationship for data more than 2 levels deep?
I have a solution when there's a simple parent-child relationship but not when there's a grandparent-parent-child relationship or deeper.
Ex. I have a table company_parent_child that stores the relationship betwen a company and it's direct parent.
create table TEMP_COMPANY_PARENT_CHILD
PARENT_ID NUMBER(10),
COMPANY_ID NUMBER(10)
insert into TEMP_COMPANY_PARENT_CHILD values (1, 10);
insert into TEMP_COMPANY_PARENT_CHILD values (1, 11);
insert into TEMP_COMPANY_PARENT_CHILD values (1, 12);
insert into TEMP_COMPANY_PARENT_CHILD values (2, 13);
insert into TEMP_COMPANY_PARENT_CHILD values (10, 100);
insert into TEMP_COMPANY_PARENT_CHILD values (10, 101);
insert into TEMP_COMPANY_PARENT_CHILD values (10, 102);
insert into TEMP_COMPANY_PARENT_CHILD values (11, 103);
1->
___10->
______100,101,102,
___11->103
Companies 100, 101 and 102 are under parent 10 and grandparent 1.
I need to create such a view or another temp table so that when I pass the parent ID, I will pull all the children on all levels. In addition, and this is the tricky part, when I join this new temp table or view to another data table without any parameters, the data should not be duplicate, ie. each company ID should appear only once.
create table TEMP_JOIN
company_id number(10),
order_id varchar2(10)
insert into TEMP_JOIN values (100, 'a');
insert into TEMP_JOIN values (101, 'b');
insert into TEMP_JOIN values (102, 'c');
insert into TEMP_JOIN values (103, 'd');
insert into TEMP_JOIN values (10, 'e');
insert into TEMP_JOIN values (11, 'f');
insert into TEMP_JOIN values (12, 'e');
insert into TEMP_JOIN values (13, 'f');
Thanks.

start by learning CONNECT BY/START WITH. once you've
written a query to read the grandparent-parent-child
relationship, then come back with more questionsYes. we did look heavily into connect by/start with, in fact along with "connect_by_iscycle","connect_by_isleaf","connect_by_root" as well.
Our dilemma is that when a joint is made between those two tables mentioned above TEMP_COMPANY_PARENT_CHILD and TEMP_JOIN, we are not able to create a view that would contain distinct company_ids, each mapped to a unique order id.
The problem is we cannot have this type of joint when there are "n" level relationship between companies (or company_id). Basically, I think we should have our unique order id mapped to a unique key. This unique key should be a specialized key that we can know at anytime the entire path of the ancestry which we can know by sys_connect_by_path(company_id,'/') path.
How do we know which path to take. The best bet is to "connect_by_isleaf" and just have the distinct "deep" path which form the specialized unique key. If you need help on this let me know. (A hint, sort by LEVEL and then do a rank after partitioning by company id and then filter the records by rank = 1, try this one!!!)
So, we will eventually have a joint (say Table X) like
PATH ORDER_ID
/1/10/100 a
/1/10/101 b
/1/10/102 c
/1/10 e
/1
/1/11/103 d
/1/11 f
I think this is the best view we can have to maintain a joint with no repetition along PATH as well as ORDER_ID. If you have any other thoughts, let me know.
Then you query by path using INSTR to pull records by company_id.
for example, if you want to get all the children for company_id "10" you would just say
select * from X where INSTR(PATH,10,1,1) <> 0
or if you want to get all the children for company_id "11" you would just say
select * from X where INSTR(PATH,11,1,1) <> 0
What do you think? Has anyone used the path information for traversing the tree? Or is there any article that tells us how to make effective use of sys_connect_by_path(company_id,'/') path.
Thank you. Hope it made sense!

Upgraded drive, now Lightroom can't find my main catalogue

I have a separate data drive in my system. When it filled up, I upgraded to a larger data drive. The person who set it up for me transferred all the dotage to the new drive. Now Lightproof can't find my main catalogue although for some reason my collections are listed.
Message was edited by moderator: fixed formatting and title, but not spelling

If you know where the catalog is located you can browse to that folder and double-click on the catalog. Lightroom will open the catalog and you can continue.

Lightroom Import cannot find files

   Lightroom 5.5 has been working fine until today. I have a Windows 7 64-bit computer with 12 GB ram and 1.5 TB free hard drive space available.
   LR seems to load OK, but when I press the Import button it slows down to a crawl and then finally comes back with the message that it cannot find any files to import. I have been importing directly from my camera via USB w/o a problem until today. If I try to transfer the files through Windows Explorer - there is no delay, so LR seems to be the problem.
   Any ideas? suggestions? Thanks in advance, george

Do you want to import the photos to the organizer? Then the previous poster gave you the right answer. However, it's not necessary to use the organizer if you already have your photos catalogued in lightroom. Instead, you can set PSE as your external editor and send the photos directly from LR. Lightroom preferences>external editor tab>browse to PSE. Then when you're in the editor or library modules, right click and choose to send the photo to elements.

Lightroom 4 keeps asking for catalogue upgrade every time

Hi,
I have upgraded to LR4 from LR3, went through all the steps and created a new LR4 .lcat catalogue, but every time i re-open LR4 I get the prompt to upgrade the catalogue again as below:. I repeated the upgrade but same thing happens each time. Now, I am "choosing a different catlogue" and manually selecting the LR$ catalogue I created, I check the box to open this every time but it wont stick....
The LR4 shortcut wont stay in the Mac dock either...
I am using Mac Lion....have had other issues since I upgraded from Leopard so dont know if this is a unique issue?
Any suggestions?

Anthony,
do you try to open the upgraded catalog(for example: catalog file is EAP_LR3_Laptop-2.lrcatalog) manually:
Steps: navigate the EAP_LR3_Laptop-2.lrcatalog file in Finder; then double click the catalog file(alternative way: right-click(control+click) the catalog file, prompt open with context menu, select Lightroom 4 application)

I love lightroom but am finding the adjustment brush slow to respond to brush strokes

My cpu works fine with huge photoshop files - why is lightroom so slow to draw adjustment strokes or erase the mask?

i experience the same behavior regardless of LR version (1.x, 2.x and now 3.x) from time to time. the file size - 10MP or 21MP DNG files does not seem to matter. the behavior seems to occur random since most of the time the brush works fine. often i experience it in fullscreen mode. i also had the idea that my 8GB DDR2 RAM machine may be responsible or something within LR that cannot handle an excess of 4GB RAM. it often helps to restart LR to get rid of the jerky brush (i guess purging the cache as in olden days with PS and large files). another idea is that my switching between LR fullscreen mode and ie the desktop or another running program (winamp, outlook etc) may cause the glitch for some reason as i have seen similar behavior in video games which shut down after several trips to the desktop. now as i mentioned i have no exact idea why this behavior is caused i am only stating my experience with LR. before this post i did not even regard this behavior as exceptional and just put it off as being "typical LR" since i have had it for so long.
btw in the time i had LR (since 1.x beta version came out) my hardware configuration changed several times always improving the computational power of the machine but this behavior always remain. my catalogue in 2.6 which handles my EOS 400D files (10MP DNG) has about 60.000 images and my catalogue in LR 3.b2 which handles my EOS 5D MKII files (21MP DNG) has 2.000 images. so i would not blame it on catalogue size. the HDD the images and catalogues are on is a Samsung HD154UI 650GB SATA 2 drive with 7.200 rpm and 32MB cache (in case that should matter).
cheers
viktor
ps: although i have 8GB RAM LR has never used more than 2GB of it - also the system (vista 64bit ultimate) never used more than 4.8GB RAM regardless of filesize and application i run. there is always more than 50% RAM idle and not being used - what is that about? all 8GB and all 4 RAM modules are being recognized fine.

Elements 11 Can't Find My Catalogues

Having successfully restored 2 catalogues from PS Elements 6 backups on an EHD, I was quite happy working in the last restored catalogue, but on trying to revert to the earlier transferred catalogue, (that I had fully viewed and verified in PS 11 after the original restore), I note that neither of my 2 catalogs appear in the available catalog list when using the Manage Catalog command. This is particularly strange as the correct location of the catalog I'm currently using shows in the System Info. I have tried all 3 options for locating the catalogs (that are stored in hidden folders in My Pictures, rather than the default location) and getting them to list in the Manage Catalogs window without success. In using the Browse option I first tried specifying My Pictures as the location of the catalogs with the Catalogue folders hidden, and then in desperation unhiding them and specifying the hidden folders themselves, but nothing comes up. Help.

Go to your hidden folder for the catalog you want in My Pictures.
Find the following file:
catalog.pse11db
Right-click on that file and choose: Open

Lightroom 5 CC: Finder vs catalogue relationship

Similar Messages

Maybe you are looking for