Lightroom 5 File Placement Problem

Snow Leopard. Importing from a camera CF card in a card reader.
My LR folder contains a subfolder named 2013. Subfolders within the 2013 folder are named by date, e.g., "2013-07-01." Recently, however, when I import photographs, LR creates a folder within 2013, also named 2013, and then creates a folder within that folder with the date of the import as the name of the folder.
For example, the hierarchy for today, 31 July 2013, is ~/Pictures/Lightroom/2013/2013/2013-07-31/mygreatpic-1.CR2 etc.
Should it not be ~/Pictures/Lightroom/2013/2013-07-31/mygreatpic-1.CR2? And, for tomorrow, ~/Pictures/Lightroom/2013/2013-08-01/anothergreatpic-1.CR2 etc?
I don't recall having changed any settings, and I can't find a setting to fix this.
Thanks!
David Illig

I have an SSD drive that has my OS and applications. I looked in the Macintosh SSD/Users/[my username]/Library/Preferences/ directory and I do not have a com.adobe.Lightroom5.plist file.
My old Macintosh HD drive has been renamed "Macintosh HD Archive" and I now use it for file archiving. it has a Marcintosh HD Archive/Users/[my user name]/Library/Preferences/ directory which contains the preference files for my older versions of Lightroom (Lightroom, Lightroom2, and Lightroom3).
After I installed the SSD drive and used it as my startup disk I have used Lightroom 4 and Lightroom 5.
Lightroom4 and LIghtroom5 have been installed on the SSD drive. I deleted Lightroom 4 after I installed Lightroom 5.
There is no com.adobe.Lightroom5.plist list file on my Macintosh SSD drive or on my MacIntosh HD Archive drive.
Perhaps the printing problem is due to a failure to create these files with the installation of Lightroom 5.44 on the SSD drive.
I do not recgnize the name "LayoutDirection1.png" as significant any of my images, but its occurence in the console log in association with Lightroom5 at the times print attempt failed suggested that the hangup was due to a missing file.

Similar Messages

Have been using Lightroom on my Apple computer for years. Now, ever since upgrading to Apple's Yosemite operating system I get an error message (150:30) every time I try to open a lightroom file. Has anyone else experienced this problem? Also how do I s

Have been using Lightroom on my Apple computer for years. Now, ever since upgrading to Apple's Yosemite operating system I get an error message (150:30) every time I try to open a lightroom file. Has anyone else experienced this problem? Also how do I subscribe to Adobe's Premium Support? Every time I've tried (through contact support) I just get taken on an unending loop.

I think we need a lot more information.
Exactly what does the message say?
Exactly what files are you trying to open?
Exactly how are you trying to open them (what menu command or button or mouse action or keyboard shortcut)?
And lastly, what version of Lightroom are you using?

How do I do equivalent of File/Place in Photoshop

This was asked way back in 2009, and at that time the answer was no, not in V2... We're now at the end of V4 and pushing V5. So, how do I do the equivalent of the File/Place in Bridge?

Hi Rikk,
The time you use Place is:
From LR or Bridge or wherever, open an image in Photoshop. You can open it as a smart object or just a normal image.
Now go back to Bridge and take another image and do a File/Place on it. It'll go into Photoshop as a layer above the existing image,
not as a separate image.
It isn't that there's no way around it - you can always open multiple images in Photoshop then select and copy the second one.
I'm just curious whether or not this functionality from Bridge has been implemented, and if so, how I access it. If it hasn't, that's fine 'cause there's always
the brute force workaround, but it's a convenient way to assemble things when you don't have all the images you'll be using side-by-side so they're not
convenient to do an "open as layers" from LR…
Some of the folks I"ve been watching do Photoshop seminars have been exclusively using Bridge as a front-end or mini-Bridge from within Photoshop. When
I see them do some of the interaction between the tools, I usually try to figure out how to do the same thing in Lightroom since that's usually my front-end.
But, for example, (having nothing to do with the question at hand) the interaction between camera raw and Photoshop for smart objects is limited to Bridge.
You can OPEN the image in PS from Lightroom, but you can't go BACK to Lightroom to make changes. You can only go to Bridge. And I suspect once you've changed
the raw file in Bridge, Lightroom doesn't know anything about the change until you re-sync the folder. I HOPE I’m wrong because otherwise it seems like there's
a really good chance that you'll clobber the changes if you save metadata to files and haven't already sync'ed, but that's a problem for more research…
Anyhow, as I said, a seminar was the source for my question, and I found an old topic in the Lightroom forum from 2009 where it was asked. At that time, the answer
was "not yet"...

Lightroom 5.3 problems, downloading through Creative Cloud.

Lightroom 5.3 problems, downloading through Creative Cloud. Error 1624
ERROR: Install MSI payload failed with error: 1624 - Error applying transforms. Verify that the specified transform paths are valid.
MSI Error message:
ERROR: Third party payload installer Adobe_Lightroom_x64.msi failed with exit code: 1624

this is from emma at https://blogs.adobe.com/lightroomjournal/2013/12/lightroom-5-3-now-available.html
I had this same error and managed to get around it by running the .msi file that the CC app downloaded to a temp folder on my own. Steps were:
1. Find the location Adobe_Lightroom_X64.msi (in a a temp folder)
2. Run it and install (serial number was already pre-filled out)
3. Restart the CC desktop app
It then appeared as installed under ‘Your Apps’ and works as usual.

"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

In Firefox 23, with private browsing enabled, why are the addresses of websites visited being added to the file places.sqlite?

In Firefox documentation it is claimed that while a user is in private browsing Cached Web Content, Offline Web Content or User Data will be saved. I am using Firefox beta 23. With 'do not track' and 'private browsing' enabled.
An examination of the file places.sqlite stored in my profile shows it is adding to the file the addresses of every website I visit. This information is not cleared when I close Firefox. When I have closed Firefox I have deleted the file but it reappears unchanged at each fresh machine start.
As I regularly update my versions of Firefox and the file is one carried over with each update the entries in places.sqlite also record my browsing history over a long period - all of it is there whether I had private browsing enabled or not.
How is this true private browsing when this file keeps a complete record of browsing history?

Further to: In order to delete the now very large ''places.sqlite'' I exported my Bookmarks to a html file. Then from my profile I deleted the 9 ''bookmark.json'' files in the folder''' bookmarkbackups'''.
With Firefox shutdown I then deleted ''places.sqlite''. Then with Firefox open I imported the html bookmark file.
The new ''places.sqlite'' generated now only contains the links kept in Bookmarks. I do not yet know if this has solved the problem. I will use the Firefox browser for a couple of days without adding any bookmarks and then check the ''places.sqlite'' file again.

HTML Help window placement problem

Hi -
We just upgraded to R7 from X5. It seems that now, for our
newly generated Help, the HTML Help viewer will not right-align.
Even if I specify the maximum width in the Window Properties
dialog, when generated, the window only extends about 4/5 of the
available screen width and is LEFT aligned.
Our screens are 1024 x 768 and RoboHelp seems to understand
this because if I max out the window size in the Window Properties
dialog, the height shown = 767 and width = 1019.
Is anyone else experiencing this placement problem?
TIA

Hi, Jack,
> ... the HTML Help window properties dialog only accepts
hard coordinates (i.e. pixels).
> ...
> Unless someone knows differently, for HTML Help,
apparently you can't get the HTML
> Help viewer to appear right-aligned for all
screen/display configurations
Yes, this is correct on both counts. Because of limitations
in Microsoft's design of HTML Help, you cannot specify the
dimensions of the help window in anything other than pixels, and
you can only set the initial position of the window relative to the
left and top edges of the screen.
On the other hand, if you are calling the help file
programmatically from an application, there may be some scope for
controlling the position of the help window by using standard
Windows functions. This article provides a small amount of extra
information:
http://helpware.net/FAR/far_faq.htm#control
Pete

I had CS6 and now I have installed CC. I cannot open files, place files, etc directly from the File Open... or File Place... Is there something I'm missing in CC that I don't know about?

I can open files directly from my Finder window (Mac OS, running latest installment). And I can copy/paste or drag/drop graphics into an open AI file for editing. But I can't use the AI>File>Open... or AI>File>Place... (or any shortcuts). Absolutely nothing happens. It's like I never clicked anything.
Am I missing something??? I've never had this problem in CS6. Is there something different in CC that I need to add or erase?
HELP!

Deornorth wrote:
I didn't realise that the Camera Raw won't work in 64bit mode. Converting to 32bit enabled the files to be opened.
Actually, that's wrong. Camera Raw 6.3 WILL run as a 64-bit plug-in when hosted by Photoshop CS5 if CS5 is running as a 64-bit app. It'll run as a 32-bit plug-in when hosted by Bridge or Photoshop CS5 set to run as 32-bit.
So, there's something else going on here....
How are you trying to open the raw files? From within Bridge or the Finder? How did you update Camera Raw to version 6.3? From the updater? Is ACR 6.3 in the correct install location? main Library (not the User but root), Application Support/Adobe/Plug-ins/CS5/File Formats/Camera Raw.plugin
Can you open raw images from within Bridge? Have you tried to view raw files with Bridge before you updated Camera Raw? Have you trashed the cache foe the folder? In Bridge under Tools/Cache/Purge Cache

Shared File Permissions Problem

Since upgrading the Mavericks I constantly have file permissions problems when I tranfer files between computer. Let me see if I can clarify the problem procedurally.
1. I have a shared directory that I set to Read&Write privileges for Admin, (me), and Everyone.
2. I clicked the cog to apply the changes to all the enclosed items. Perfect... everything contained within the directory was changed.
3. I went to my other Maverics computer and connected to this shared directory using SMB, AFP, connect to server command-k, and using the shared feature on the finder window, which asked me to authenticate when I make the connection. I logged in with the admin account to make sure I absolutely had full privileges.
4. I transferred a file to the shared directory and it ended up with the privileges of only (me) RW and Everyone as No Access. It dropped every other set of privileges that were in the directory and set Everyone to No Access, which is a major problem since it serves the files to the web server. I checked the Sharing preferences in the System Preferences. Sure enough all groups are set to Read and Write.
The shared directory in Terminal says the privileges are drwxrwxrwx+ so it should retain those privileges for any file I place in that directory, but it doesn't.
This is a new problem to Mavericks. When I used OS 10.7 and 10.8 and chose the get info option to apply the permissions to all enclosed files it stayed that way for any file I inserted into the directory. Now you have to constantly change file permissions even going from Mavericks-to-Mavericks computers.
Does anyone know how to retain the file permissions for a shared directory when new files are placed in the directory?

see Topic: Office (2004 & v.X) can't save to AFP volumes properly
Apple wants you to enable ACLs even if your not using them. See my posting dated April 14

Ability to bring in Lightroom files directly?

Hello, I use Lightroom and don't always need to bring them into Photoshop for additional editing beyond what has already been done in Lightroom and I would like to bring them into Indesign without converting to Photoshop first. It would be nice to be able to drag and drop from Lightroom or place.

Will Automatic Duck do the trick?
It's supposed to, although I've never tried it. It's also expensive for what it does. There are other possibilities. If all your camera audio files/tracks start at the beginning of your Protools sequence, your ahead. If not, then bounce them to disk one by one starting at the exact beginning of the sequence.
In FCP, set the timeline start SMPTE to the same thing your Protools project is set to. Import your track bounces to tracks in the FCP Timeline. The audio will line up.
Or....
Export the Protools project as OMF. Import the OMF into Logic Pro. Export the Logic Pro Arrange to XML. In FCP, import the XML file. Again, be sure all SMPTE starts/settings are the same for all timelines in all three apps. Be sure you don't forget to include the media files along with the XML.
I know, it's dumb that FCP doesn't import OMF files.

Lightroom Corrupt Catalog problems- Help!

Lightroom Corrupt Catalog problems reading/writing from disk when attempting to repair - Help! I have my LR box in hand and my product keys and license info but can't find the disk. I'm assuming this is the only way to repair. Suggestions, Comments are welcome and appreciated.
Thanks in advance!!!

Corrupt catalog will not be fixed by re-installing the Lightroom software (although if I were you, I'd still find that disk!)
If I were you, I would first check a recent backup of your catalog file, and see if that will open (double-click on it in your operating system). If that opens properly, I would just use that file.
If it doesn't open properly, then one trick that sometimes works is to open a blank catalog in Lightroom, then File->Import from Another Catalog and point to the catalog file.
And if that doesn't work, please write back with a lot more details, including operating system, version of Lightroom, and much more detail abou

I am trying to find my Lightroom files

I am trying to find my Lightroom files, I unpluged my hard drive and plugged it back in
Ron

I am going to assume that you are working on some version of Windows (am I right?) and that now the external drive has a different file letter than it had before.
You can use these instructions to fix the problem http://www.computer-darkroom.com/lr2_find_folder/find-folder.htm, or have Windows re-assign the previous drive letter to the drive.
In the future, it would be helpful for you to state your operating system and state your version of Lightroom any time you ask a question so we don't have to guess

File Place, but not as Smart Object?

Can you File>Place and Image without it being a Smart Object layer?

Leaving as Smart Object is usually the way to go, but if for some reason you don't want a Smart Object you can always use: Layer: Rasterize: Smart Object.
One problem with vector smart objects is the vector data is not present in Photoshop output. Meaning if a document has vector smart objects and you save as PDF, the SO ends up as pixels in the PDF output (check by opening the PDF with Acrobat and zoom in)
You do have the option of copying vector data, then pasting as paths or shape layers. This is wrought with complications but it can yield vector output.

Faces and Places Problem

Hello,
maybe someone could help me (apple telephone support could not):
Faces problem:
I made a smart-album to sort out all the "unnamed faces". But 92 pictures have a strange behaviour. They are tagged as "unnamed" although there is no rectangle in the picture to tag. I've allready used the repair-function and deleted all cache files (telephone support advised me to do both).
Places problem:
another strange thing is places. I've got a few pictures which have more than one "place" tagged. I don't know how this could happen. If you take a look at the screenshot you can see that I made a smart-album with 4 different places (PLACE - IS - XY - AND - PLACE - IS .....) to demonstrate that kind of behaviour

I've noticed that photos I had faces from iPhoto 09 are not syncing (I only had a few).
In the manual list, the faces are not an option to select them. Tried removing and resyncing library and no avail.

File Place does not appear on my menu. Neither does Tools Photoshop Image processor.

In Bridge File>Place is grayed out on my menu. Tools>Photoshop>Image processor does not appear at all. I have reset the preferences numerous times and am good to go until I shut down my computer. When I reboot they are gone again. I have a Mac with OS 10.10.2 (Yosemite) and CC.

Mardi Carter wrote:
I shut down using "Shut Down" under the Apple menu.....always…
Well, that's fine for the OS, but sometimes not so great for Photoshop. Try QUITTING Photoshop from the Photoshop menu, or by Command Q, before you get anywhere near your Apple menu .
Gene gave you sound advice, but don't forget to run Repair Permissions with Apple's Disk Utility before and after any installation, upgrade or update of the OS or any application.
You'd think that shouldn't be necessary, but it is indeed vital, indispensable routine maintenance.
Forget about "it had never happened before", Yosemite is a work in progress. Apple never gets a major OS X release right until about the dot four or five release, so Yosemite has a way to go before it's at 10.10.4 or 10.10.5. That has proven to be the nature of the beast.

Lightroom 5 File Placement Problem

Similar Messages

Maybe you are looking for