Lightroom 3 tethered 7d file naming

I know there's other things similar to this that say 'known issue'... I figured I'd write this to help clear up what I was seeing. Hopefully it's not all currently known, but if nothing else hopefully the next person googling finds this info useful.
lightroom 3.0 build 677000
All files on CF are CR2 files (if that matters).
Canon 7d - tethered:
The behaviour of lightroom appears to be:
- take the modified date of the file
- apply GMT offset - already discussed elsewhere, may be a filesystem thing, no idea here...
Same CF card in a USB2 reader:
- metadata 'date' taken and applied unmodified
The reason i found out about the modified time, is that i copied all my holiday photos back onto the CF card as an 'easier' way of moving the photos from my laptop to my PC. All my photos that i had to copy on after my holiday were shown to be taken as the date they were copied as. I took the card out and back into the USB reader to get all the dates correct.
My expectation would be that lightroom should not be taking the modified time of the file on disk, but actually read the metadata consistently as it does copying data off the CF. The modified time shouldn't be looked at for the file - it's very possible that its incorrect.
Anyway, i'm happy to hear if any of this is incorrect, but that's my take on it.

I'm pretty aware it'll be a shortcut - and I'm usually prefer a shortcut where it will give the same result.
This shortcut very potentially won't give the same result. For this to work, you'll need to have not touched any files on the CF since taking, and you'll need to be in GMT+0 timezone. I'd suggest that one or both of those is very potentially not the case.
What I'd *really* like is to at least have a checkbox to give me the choice to have lightroom use the files metadata. I'd argue that should be default, but i can understand it not being default.
The perfect solution would be to remove this shortcut, but if it has to stay, at least give a choice to get the accurate data.

Similar Messages

Why do i get the following message when i attempt to open my backup file for lightroom cc? "Lightroom cannot use the catalog named "Lightroom Catalog" because it is not writable and cannot be opened". This message just started coming up after downloadi

why do i get the following message when i attempt to open my backup file for lightroom cc? "Lightroom cannot use the catalog named "Lightroom Catalog" because it is not writable and cannot be opened". This message just started coming up after downloading lightroom cc (previously using lightroom 5)...am i backing up properly or not???

Open Pictures folder and move the files named lrcat-journal and lrcat.lock to Desktop.
Make sure that , they are not inside Pictures folder any more and try to open backup from Lighrtroom and check..
Any LRcat file with .lock extension , move it to Desktop.

I have a new Mac Pro computer and have migrated my files from my older computer to the new computer. In trying to open a Lightroom catalog on an external hard drive I keep on getting the message "lightroom cannot use the catalog named " " because it is

I have a new Mac Pro computer and have migrated my files from my older computer to the new computer. In trying to open a Lightroom catalog on an external hard drive I keep on getting the message "lightroom cannot use the catalog named " " because it is not writable and cannot be opened. I have fixed all the "permissions" and yet it will still not open. How do I fix this?

Hello Forum Members,
I figured it out. You have to select the actual logo of the Lightroom catalog and then click on "get info" and allow what ever your new user name to "read and write". That worked!
Henri Silberman

Lightroom 2.1 Auto import file naming adding -1

I have used lightroom's (2.1) auto import function on 5 separate shoots with no problem. On my last shoot lightroom has been adding a "-1" to the file name. I am using "Custom name - Original File". So what used to be "Jen-1007" is now "Jen-1-1007", "Jen-1-1008", "Jen-1-1009", etc. I tried to use the other methods of naming but a -1 still comes up in some part of the file name. I would appreciate any help. Thanks

First I would check the file naming preset to make sure that it hasn't been accidentally edited, then I would choose a new empty location to write to (destination).

On lightroom 5.6 (mac) message says "the file named _dsc0189.Nef could not be moved to trash folder. what do I do besides manually search and move hundreds of files?

message button pops up saying The file named _dsc0189.NEF could not be moved to the trash folder.
I have hundreds if not a couple thousand images that I will be wanting to delete. Any suggestions besides manually
search for these files and dragging them to the trash.
Mac
I have tried restarting the computer and lightroom

Same issue here!

How can I edit lightroom 5 smart previews on mac book pro (mbp) when the lightroom 5 master image files are on my external hard drive is disconnected from the mbp

How can I edit lightroom 5 smart previews on mac book pro (mbp) when the lightroom 5 master image files are on my external hard drive is disconnected from the mbp? So far when I try to disconnect the external HD from the mbp, I get the following pop up window: The disk "external hard drive A" couldn't be ejected because "Lightroom" is using it. Quit that application and try to eject this disk again. When I do that and restart Lightroom 5, the Adobe Photoshop Lightroom - Select Catalog screen pops up but doesn't list my external hard drive A as a choice.
I've reviewed Adobe's Lightroom Help | Smart Previews Lightroom 5 web page and still haven't been able to figure what I'm doing wrong. Any help would be appreciated.

Your internal HDD. by default, is named 'Macintosh HD'. From what information you supplied, it looks like there is already a Lightroom catalog installed on you local (internal) HDD using the standard naming convention Adobe uses as well as a Lightroom catalog on your external drive which you created. To be sure of which catalog Lightroom is loading when it starts up, To do this, start Lightroom as you normally would. After it starts, select the Lightroom menu item, then select the Catalog Preferences item and finally, navigate to the General tab. The Location information will tell you exactly what catalog Lightroom is opening by default. This will likely be the Photography Mac Book Pro Versions catalog on your external HDD. Once that is confirmed, you are ready to proceed. As an additional test/verification, you can shut down Lightroom and, this time, start Lightroom while holding down the ALT/OPTION key. This will cause Lightroom to pause and display a screen which will allow you to chose a different catalog to open. Navigate to the /Users/[user name]/Pictures/Lightroom folder and select the Lightroom 5 Catalog.lrcat file. When Lightroom comes up, there should be no previews or folders as this catalog should be empty. Now you can be certain which catalog is being used and which catalog has all your data and you are ready to migrate your current catalog. Shut down Lightroom.
To migrate your current catalog, use Finder to locate your Photography Mac Book Pro Versions folder on your external drive. Select the folder and select COPY from the context menu. Next, use Finder to navigate to the /Users/[user name]/Pictures/Lightroom folder on you internal HDD. You can start at the Macintosh HD level and work your way down by opening each level (Macintosh HD/Users/[user name]/Pictures). Select the /Pictures folder and then select PASTE... from the context menu. When the COPY/PASTE is complete, you should see the following files on the Macintosh HD:
Macintosh HD/Users/[user name]/Pictures/Lightroom/ and
Macintosh HD/Users/[user name]/Pictures/Photography Mac Book Pro Versions
The Macintosh HD/Users/[user name]/Pictures/Lightroom folder will contain the empty default catalog the Adobe created when Lightroom was installed and Macintosh HD/Users/[user name]/Pictures/Photography Mac Book Pro Versions will contain a copy of the catalog you created on your external HDD.
You are almost done now. Make sure your external drive is still attached for this step. Restart Lightroom using the ALT/OPTION key again. When the Select Catalog screen appears, select the Choose a Different Catalog button (lower left side). When you do, a Finder window will open to allow you to navigate to a catalog of your choosing. Navigate to Macintosh HD/Users/[user name]/Pictures/Photography Mac Book Pro Versions and select the file Photography Mac Book Pro Version.lrcat. This is the copy you just created. Select the Open button and Lightroom should start. You should see all of your previews and settings just as before. Also, in the left hand panel, all of your folder should show up and none of them should be dimmed and none of your previews should display a small exclamation point badge. Either a dimmed folder name or an exclamation point badge indicates that Lightroom can't find the associated image file. If everything looks good, go to the Lightroom menu, select Preferences and then select the General tab. Under Default Catalog, select an option to either load the LAST catalog opened or select the Users/[user name]/Pictures/Photography Mac Book Pro Versions catalog from the drop down. Shut down Lightroom and then restart it normally. This time, when Lightroom starts, you should be viewing the new copy of your catalog. You can confirm this by looking at the General tab on the Catalog Preferences screen (Lightroom/Catalog Preferences menu items). Shut down Lightroom once again and this time, eject your external drive before restarting. This time, your folders in the left hand panel will be dimmed but you should be able to work with your smart previews. If Lightroom should display a Select Catalog screen with the external drive detached, double check your settings as it indicates Lightroom is still looking at the copy of the catalog on the external drive rather than the new copy you made.
Finally, if you are seeing dimmed folders and/or exclamation point badges with the external drive attached, this indicates a problem. You can select any folder and select Update Folder Location from the context menu. This will allow you to navigate to the copy on the external drive and select it. Lightroom will then update the catalog (select to synchronize the content). This will not only clear the dimmed folder problem but also remove the exclamation point badges for all photos in that missing folder. However, it may indicate that not all went well with the copy of the catalog so make sure to verify all went well. You can use the Get Info option on the two folders. You should see the same number of files/folders for both the copy on the internal drive as well as on the external drive but you can't rely on the byte count because of the possibility of differences between the geometry of the two drives. Hope this all helps!

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.

File naming: sequencing by date

In the Filename Template Editor and Rename Photos (F2) function, I'd like to be able to sequence my file names by date, with the sequence beginning with 1 for each day, and incrementing regardless how many imports I do.
For example, the first image for January 2, 2008 might be called "08-01-02_001". On that day I may perform three or four imports, and the sequence continues to increment from 001 to however many images I import on that day. The following day the sequence automatically resets to 1.
If images are imported that were recorded on an earlier date, this function would have to increment from the highest number of the date the image was recorded (because this is how Lightroom's date function works). For example, if on December 28, 2007 I shot 243 images and today I import another image that was shot on that day, the file name would be 07-12-28_244.
(I currently sequence by month, manually specifying the start number for each import sequence, but I sometimes forget to change the sequence starting number.)
Thank you for all you've done. I can't imagine working without Lightroom.

I would like to see exactly the same enhancement. Perhaps for some file naming schemes it would be helpful to parameterize that function, e.g., "Resent sequence number [to xxx] whenever [date|month|year|camera ...] changes].
As part of that, I would like very much to have more options/control for the file organization. In particular, I would like to see yyyy/yyyymm/yyyymmdd (e.g., 2008/2008-01/2008-01-15 with the "-" being optional). Right now, the closest you can come to that is yyyy/mm/dd, which leaves too much opportunity for file/folder name confusion.
dds

File Naming with parts of names and dates (substrings)

I am trying to settle on a filenaming convention that Lightroom doesn't support, but does exist in Breezebrowser and in many database languages.
It is a function that allows using just part of one of the other available file naming elements, instead of the full thing. This helps keep file names shorter but still meaningful.
For example, one piece of the naming convention I'm trying for is just the sequential number generated by my camera, but without the camera specific designator. For file '_C8P7692', for example, I just want to use the '7692' part.
This could be accomplished if I could specify in the file name builder that I only want to use those characters. It would look something like:
SUBSTRING(filename,5,4), where 5 is the character I want to start with, and 4 is the number of characters I want to take.
This would also address some of the other feature requests for variations on the date formats built into the file name builder.
Paul Wasserman

You can do that one in LR easily.
Use "(filename or original) number suffix" instead of "filename".

How do I restore original file naming on an import

Through a process of idiocy and confusion, I've ended up with TWO creation dates on my files, e.g. 20140112-20140112-Johnny at the beach. I tried the step back, step back, step back system, or "undo, undo" but that didn't succeed. I've tried creating a new catalogue to re-import the photos from iPhoto, but I've mislaid the File Renaming Panel that my Lightroom tutor's handout mentions as being on the right-hand side of the screen. I can only see Histogram and Keyword list.
When I try and rename the files individually, I don't get an option to merely remove one of the 201401112 key strings, I get a series of checkboxes.
I know I've done wrong, but I want to undo it and not make it worse. I'm scared that if I restore original settings, I'll delete all of my images - all 1400+ of them!
Anyone who can give a solution gets a lovely cake.

I suggest you stop Re-Naming your images on import and place them in folders by the date they were shot. Lightroom can do that for you on import from card or camera or you can do it yourself manually before you import them into LR. You could also put the Sub-folders by date in a top level folder by year or just in one folder named whatever you like.
Not sure why people Re-Name their images when copying them from the card/camera to their hard drive. To me that makes no sense at all. If I have images that I want to separate from others I will manually re-name them and or assign a keyword or rating to them. You can also have collections of images by subject, location, date or whatever you like and those collections can be from any folder imported into LR.
The only time I would even think about re-naming images on import, and or copying to my hard drive, is if I have 2 identical cameras. Which I have in the past. But even then I changed the file naming in the camera having one cameras files start with 1 and the other start with 2

Sequence Number By Date Option For File Naming

I would like to see Lightroom have the option to have the sequence numbers be reset when the date changes and increment accordingly. For example, I have the file naming set to use Date (YYYYMMDD) Sequence Number (0001) and the sequence number starting at 1. As Lightroom is now I will end up with 200909010001, 200909010002, 200909020003, 200909020004, 200909030005 200909030006 etc. and what I would like to see is the option for 200909010001, 200909010002, 200909020001, 200909020002, 200909030001 200909030002.
This would make it much faster for renaming or import when using this combination of date and sequence in file names.

Hi
For the Transport Protocol "File Transfer Protocol (FTP)" files are always processed in ascending alphabetical order
If you want the file to be processed in sequence then you can use Quality of Service EOIO in the sender adapter.
The files are processed in the sequence they are picked up.
otherwise use BPM for File Sequencing..
Refer the following Threads
FTP Sender Adapter - Processing Sequence
Processing Sequence issue of FTP protocol
Regards
Abhijit
Edited by: Abhijit Bolakhe on Nov 4, 2009 10:32 AM

Lightroom cannot open the catalog named "lightroom 4 good" located on volume "LIGHTROOM" because Lig

Lightroom cannot open the catalog named “lightroom 4 good” located on volume “LIGHTROOM” because Lightroom cannot save changes to this location. This is what I am receiving even from my back-up
Serial Number removed by: PECourtejoie

You need to have writing permission where a LR catalog is stored.
Even for just opening a catalog, since this database does not have a save-to-catalog command.
Maybe it makes sense that you do not have them for a backup storage location in order to prevent accidental overwriting?
If you agree, first copy the lrcat-file to your usual working folder where you have writing permission, maybe renaming it if that would overwrite you real working catalog.
If you do not agree, remedy the writing permission for your user account at the backup spot.
Cornelia

Originals lost - anyway to extract the Lightroom images as working files

I work on a Mac, OS 10.4.11
Somehow, I must have unknowingly complettely deleted the Canon 5D .CR2 RAW images from a very important job before I backed them up, as the original files have completely disappeared from my computer.
However, those images still appear in Lightroom, but since the originals cannot be found, the Lightroom screen images cannot be opened in Photoshop.
However, I can go into the develop mode, pull up one of the Lightroom images and zoom in to 1:1 and there is enough information in what I see that if I could somehow extract this image from Lightroom into a workable file, such as tif or jpg or anything that Photoshop can recognize, I could still save myself to a degree. I can never restore the full information of the original files, but I could produce files that my client could make use of, so long as the blowups were not too drastic, and they would certainly be adequate for Power Point presentations. I see enough information in the Lightroom images that I know I could do something even for print, particularly with interpolation software, if only I can extract those images as workable files.
Does anybody have a solution?
Thank you
PS: I have done a thorough data recovery search using Data Rescue II and I found all kinds of deleted images, but not the ones I need.

Close LR.
On your harddrive, next to your LR catalog file, you will have a package named: "XXXXX Previews.lrdata"
(The XXXXX is whatever you have named your LR catalog file to, if your catalog is named "Lightroom.lrcat" your previews package will be named "Lightroom Previews.lrdata".'
Take a copy of this file to make sure you don't mess it up.
(Or don't, but don't blame me if you mess it up ;-)
Right click on the package and choose "Show Package Content".
Now you get access to LR previews.
You can navigate down the folder structure to find files named like "3A0D27C0-AA5A-11DB-B0C5-00112488B2E4-514d8ee17112aeee3852fda5392a8ee8-10.lr-preview.noin dex"
Each of these files can contain a number of jpeg previews.
Drag any of this files onto filejuicer to extract the previews.
Or drag the entire preview package onto filejuicer an it will extract all previews.
It might require a lot of diskspace though.
How do you find the particular previews that belongs to the images you have lost?
I really don't know
/Andreas

Lightroom cannot use the Catalog named "Lightroom 5" because it is not ........

I keep getting an error after closing Lightoom "Lightroom cannot use the Catalog named "Lightroom 5" because it is not writable and cannot be opened"
Eventually I have been able to regain acess only to have it happen again, it is happening every day now. I have tried shutting down services and programs, sometimes it works. I have restarted my computer, I have deleted previews.lrdat and that worked once, but not always. I have saved and optimised the catalog, still happens. there is no journal file open or in existence when this error happens and finally, now I have lost my publish services which represent the record of hudreds, even thousands of online images. HELP

Have you checked the permissions on the folder where the catalog is stored and the permissions on the catalog file itself? Does it show write permission or something else?
And just a wild shot in the dark, you should also check to see if the catalog file or its folder is shown as Read Only by your operating system (It should not be)

Lightroom 3 tethered 7d file naming

Similar Messages

Maybe you are looking for