Lightroom 1.1 Documentation

When I look at the documentation in the 1.1 folder it only lists 1.0 PDF file, and the very general help HTML files. Is there an updated manual for 1.1? The link for the manual when 1.1 installs is to a User Guide "Lightroom 1.0 Help.pdf". Where do I get information on the new cataloging capabilities and exporting catalogs?
Sorry about starting a new topic, but the 1.1 Update topic would not allow me to reply.
Jeff in Lincoln

I just had to rebuild my WinXP laptop from scratch. Installed LR 1.1 without installing the 1.0 version first.
The installation created a "User Guide" link in the start menu which pointed to "C:\Program Files\Adobe\Adobe Photoshop Lightroom 1.1\Resources\en\help\Lightroom 1.0 Help.pdf"
The User Guide shipped with my downloaded copy of LR 1.1 was in fact the old guide for LR 1.0. The link provided in the note prior to this one enables you to download the correct PDF file, but the one I downloaded was named: "learn_lightroom_helppdf_en.pdf".
Hope this information helps someone,
Dan

Similar Messages

Missing Selection in Lightroom 3.2, Metadata

In the local Lightroom 3.2 Documentation it indicates that the options for the Library, Metadata, Options include …
Home / Using Photoshop Lightroom 3 / Organizing photos in the catalog / Viewing and editing metadata
View photo metadata
In the Library module, the Metadata panel displays the filename, file path, rating, text label, and EXIF and IPTC metadata of selected photos. Use the pop-up menu to choose a set of metadata fields. Lightroom has premade sets that display different combinations of metadata.
With one or more photos selected in the Grid view, or with a single photo selected in the Filmstrip in Loupe, Compare, or Survey view, choose any of the following from the pop-up menu at the top of the Metadata panel:
Default
Shows the filename, copy name, folder, rating, text label, and a subset of IPTC and EXIF metadata.
All
Shows the filename, copy name, file path, rating, text label, and all EXIF and IPTC metadata.
All Plug-In Metadata
Displays custom metadata created by third-party plug-ins. If you don’t have any plug-ins installed, filename, copy name, and folder are displayed.
EXIF
Shows the filename, file path, dimensions, and EXIF camera metadata such as Exposure, Focal Length, ISO Speed Rating, and Flash. If your camera records GPS metadata, the information appears as EXIF metadata.
EXIF and IPTC
Shows the filename, size, type, location, metadata status, as well as all EXIF and basic IPTC metadata.
IPTC
Shows the filename and basic IPTC metadata: Contact, Content, Image, Status, and Copyright metadata.
IPTC Extension
Shows the filename and IPTC metadata for model and artwork releases and other types of licensing rights.
Large Caption
Shows a large caption edit box and the copyright box.
Location
Shows the filename, copy name, folder, title, caption, and location fields.
Minimal
Shows the filename, rating, plus Caption and Copyright metadata.
Quick Describe
Shows the filename, copy name, file path, rating, and the following EXIF and IPTC metadata: Dimensions, Date Time, Camera, Title, Caption, Copyright, Creator, and Location.
In the Metadata panel, if an IPTC metadata field displays an arrow, clicking the arrow is a quick way to find and view all photos containing the specific metadata.
If multiple photos with different metadata settings are selected, the metadata fields display <mixed>. To show the metadata for the photo that’s targeted (active) within the selection, choose Metadata > Show Metadata For Target Photo Only. If more than one photo is selected in the Filmstrip in Loupe, Compare, or Survey view, the Metadata panel displays metadata only for the active photo.
The 3.2 version of lightroom does not include the ALL choice. Is this correct?
Thanks

The All option does appear to be missing in 3.2 (not sure if it was in 3.0 or not). In any case, I usually develop my own templates manually. You can also try out the plug-in at: http://regex.info/blog/lightroom-goodies/metadata-presets which should generate the desired template (including an "all" template) if you so desire. I am not related to this developer but you might take a look at his site for other plug-ins that might benefit your workflow.
Jeff

DNG, XMP, and Exporting

The following pertains to Lightroom 1.1 (and possibly only to the Mac version on an Intel Mac with OS 10.4.10).
I have searched Lightroom 1.1 Help, the knowledge-base, this forum, and elsewhere for simple instruction on how to do either of the following:
Task #1: Create a separate XMP sidecar file from a DNG file for which the metadata relating to picture adjustments made in the Develop module has been embedded in the DNG file or stored in the Lightroom database.
Task#2: Export a DNG file (for which the development metadata has been embedded in the DNG file or stored in the Lightroom database) while at the same time creating a separate XMP file that contains the development metadata.
I did some experimenting relating to Task #2:
In Lightroom, I set the exposure of a DNG file to +4.00 in the Develop module, then switched to the Library module and clicked on the menu item "Metadata > Update DNG Preview & Metadata", and then exported with "Original" selected as the file format. Immediately after this, I set the exposure to -4.00, without updating, and then exported with "Original" selected as the file format. Immediately after this, I exported with "DNG" selected as the file format.
Here's what I found:
1. Looking at the thumbnail preview for each in Mac OS 10.4.10's Finder window: Exports 1 & 2 look like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Export 3 looks like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). Opening any of these files within Mac OS X's Preview application shows the original state of the file without ANY of the development adjustments made before exporting.
2. Looking at the pictures in Adobe Camera Raw 3.7 (because I have only Photoshop CS2): Export 1 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Exports 2 & 3 look like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). No subsequent changes occur by going on to open the files within Photoshop CS2 after they are displayed in ACR 3.7.
3. Looking at the pictures after re-importing into Lightroom: Export 1 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Export 3 looks like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). For a few seconds, export 2 looks like the picture did the last time I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. with +4.00 exposure). Then it switches to look like the picture did at the time of the second and third exports (i.e. with -4.00 exposure). It seems this has something to do with thumbnail previews being already embedded in the files and with Lightroom displaying them temporarily before updating them.
4. All three exports, when re-imported into Lightroom, begin with two snapshots already in the Snapshots panel of the Develop module: "Import" & "Import 2". "Import" is the original file condition when the file was first imported into Lightroom (before any of my export experiments). "Import 2" is the state of the file at the time I exported it, not the state when I clicked on "Metadata > Update DNG Preview & Metadata" (i.e. "Import 2" is with -4.00 exposure) EVEN IF THE CATALOG IS DELETED AND A NEW ONE CREATED BEFORE IMPORTING THESE, THE SAME THING OCCURS.
In none of these scenarios was an XMP file created. This had me wondering whether XMP files were possible at all in conjunction with DNG files. On to...
Task #1:
Now, as I was beginning to think that the only solution for creating XMP files from DNG files was to have Lightroom set up to maintain metadata in XMP files instead of in its own database (i.e. full-time XMP files as opposed to XMP files created only when exporting), I tried to alter settings in Lightroom's preferences, clicking menu

(to Lee Jay: Yes, as I found out.) Here's the rest of my post:
...items and buttons in this sequence: Preferences > General > Go to Catalog Settings > Metadata. Nothing I tried with the settings there would induce Lightroom to create XMP files alongside DNGs.
AFTER MORE WORK WITH JPGs AND CANON RAW FILES (.CR2), I FOUND THAT I COULD CREATE XMP FILES FOR THE CANON RAW FILES ONLY.
My conclusions are:
1. Lightroom writes separate XMP sidecar files for 3rd-party proprietary RAW formats only. This view is supported by the verbiage under these headings in Lightroom Help: "About metadata and XMP" and "Synchronize metadata with Adobe Camera Raw and Bridge".
2. This means that, for other formats, enabling the following catalog settings under Preferences does not result in separate XMP files: "Write develop settings to XMP for JPG, TIFF, and PSD", "Automatically write changes into XMP".
3. Also, for the other formats, enabling these catalog settings either does not alter the files at all or else alters them in a way that shows up only within Lightroom, Photoshop CS3, and any other applications that use Adobe Camera 4.0 or later. My additional export/re-import experimentation with JPGs in Lightroom suggests the latter is the case.
4. In Lightroom settings and documentation, "to XMP", "into XMP", etc. mean "to the XMP data embedded within the file", "into the XMP data embedded within the file", etc., except for those cases in which the associated file format is 3rd-party proprietary RAW, where these phrases mean "to a/the separate XMP sidecar file", "into a/the separate XMP sidecar file", etc.
5. The problem that seems to remain is that, apparently, not all non-Adobe software that can read DNG files is able to view changes made to these files by Lightroom (e.g. Mac OS X Preview).

Scripts - Not plugins

I recently discovered a new feature in Lightroom 4 (not documented).
Add a Scripts directory (sibling of 'Modules' directory) and you can run lua scripts without making full-blown plugins.
e.g. D:\Users\{me}\AppData\Roaming\Adobe\Lightroom\Scripts\HelloWorld.lua
local LrDialogs = import 'LrDialogs'
LrDialogs.message( "Hello", "(World)" )
Appears as 'HelloWorld' in Scripts Menu (Main Lightroom Toolbar - for all modules).
(restart Lightroom after adding new scripts).
Rob

Hi Rob,
This capability has been around since Lightroom 2 (or possibly earlier) and first came to public attention when it was used to resolve a bug with upgrading Lightroom 1 catalogs to Lightroom 2. We discussed it a little in this forum nearing 4 years ago so its no wonder you didn't spot that conversation..
I used it years ago to publish a small script for relaunching Lightroom with the current catalog.
If what you are doing can be done within a plugin then it is much better to use that approach. Scripts are unsupported, and not designed for Lightroom user use, so a thrown exception, endless loop, or long running synchronous task can cause havoc for Lightroom and when first using this technique I managed to lock up Lightroom quite a few times. You need to be very careful when using this undocumented capability.
Matt

Can the Nikon D3200 shoot tethered in the newest LR? The support article was confusing.

I am considering purchasing a Nikon 3200 for use in a small Santa photo studio. I will be purchasing Lightroom, as well, and using a tethered setup to capture the images for a quick turnaround to photo or website. When I initially researched it, I swear I saw it was listed as supported. Now I don't see it under the list of tether-supported Nikon's, yet Canon has a list of specifically non-supported cameras, and the Nikon does not appear on a non-supported list. Is there any indication this camera CAN, or soon will, be able to be used for tethered shooting in Lightroom?

Official documentation does not list it as currently supported.
Future support isn't normally announced.

Lightroom 5.3 crashes when using Email Photo. This problem was documented in May 2013

When will Adobe fix this problem? I saw the first complaint on-line in May of 2013. When will Adobe publish a work-around? What's causing this problem?

Thanks for your response. Here are specific answers to your questions:
PC
Outlook 2013
Win 7 Ultimate SP1
If you're working and I'm not then maybe a simple reinstall would be helpful.
Some hardware details:
Feature
Details
PC Manufacturer
Dell Inc.
Model
Precision WorkStation 490
Motherboard Manufacturer
Dell Inc.
Product
0GU083
CPU
Intel(R) Xeon(R) CPU X5355 @ 2.66GHz
Version
Intel64 Family 6 Model 15 Stepping 7
Data Width
64 bits
L2 Cache Size
8,192 KB
Approximate Current Clock Speed
2,660 Mhz
Approximate Maximum Clock Speed
2,660 Mhz
BIOS
Phoenix ROM BIOS PLUS Version 1.10 A07
Date
12/12/2007
Version
DELL - 15
Memory slots available on motherboard
8
Installed Programs:
Name
Version
Adobe AIR
3.6.0.5970
Adobe Creative Cloud
2.3.0.322
Adobe Flash Player 11 ActiveX
11.9.900.170
Adobe Flash Player 11 Plugin
11.9.900.170
Creative Audio Control Panel
2
CANON iMAGE GATEWAY Task for ZoomBrowser EX
1.7.2.11
Canon Internet Library for ZoomBrowser EX
1.6.3.9
Canon MOV Decoder
1.5.0.7
Canon MOV Encoder
1.3.1.3
Canon RAW Codec
1.5.0.47
Canon My Printer
Adobe Media Downloader
1.0.4.878885
Creative Software AutoUpdate
1.4
Creative Sound Blaster Properties x64 Edition
Canon Utilities Digital Photo Professional 3.8
3.8.1.0
Canon Easy-PhotoPrint EX
Canon Utilities EOS Utility
2.8.1.0
LiveUpdate 3.2 (Symantec Corporation)
3.2.0.68
Logitech Vid HD
7.2 (7240)
Microsoft .NET Framework 1.1
Canon MovieEdit Task for ZoomBrowser EX
3.4.1.9
Mozilla Firefox 26.0 (x86 en-US)
26
Mozilla Maintenance Service
26
Canon MP Navigator 2.2
Norton 360
21.1.0.18
OpenAL
Canon Utilities PhotoStitch
3.1.22.46
Canon Utilities Picture Style Editor
1.7.0.0
Creative WaveStudio 7
7.14
Canon Utilities WFT Utility
3.5.1.1
Canon Utilities ZoomBrowser EX
6.5.1.15
Canon ZoomBrowser EX Memory Card Utility
1.3.0.4
Quicken 2013
22.1.12.7
Quicken 2014
23.1.5.8
Quicken 2012
21.1.7.18
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148
9.0.30729.4148
Steganos Internet Anonym 2012
2.1.3
Java 7 Update 45
7.0.450
Adobe Photoshop CC
14
Adobe Bridge CC (64 Bit)
6
Bing Bar
7.3.114.0
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729
9.0.30729
Google Earth Plug-in
7.1.2.2041
iolo technologies' System Mechanic
12.5.0
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4048
9.0.30729.4048
Perfect Photo Suite 7.5
7.5
Steganos Privacy Suite 15
15.1
Microsoft Visual C++ 2005 Redistributable
8.0.61001
Nuance OmniPage 17
17.1.0000
Adobe Photoshop CS6
13
Apple Software Update
2.1.3.127
Bing Desktop
1.3.171.0
Microsoft Visual C++ 2005 Redistributable
8.0.59193
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17
9.0.30729
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
9.0.30729.6161
Steganos Privacy Suite 14
14.2.1
Adobe Reader XI (11.0.05)
11.0.05
Norton Ghost
15.0.1.36526
QuickTime
7.74.80.86
Logitech Webcam Software
2
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
10.0.40219
Apple Application Support
2.3
Omron Health Management Software
1.31.0007
Logitech Unifying Software 2.10
2.10.37
Microsoft Mouse and Keyboard Center
2.2.173.0
NVIDIA Display Control Panel
6.14.12.5896
Microsoft Project Professional 2010
14.0.7015.1000
Microsoft Visio Professional 2010
14.0.7015.1000
Photomatix Pro version 5.0
5
Microsoft Office Professional Plus 2013 - en-us
15.0.4551.1011
Logitech SetPoint 6.32
6.32.20
Broadcom Management Programs
10.20.03
Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219
10.0.40219
Java 7 Update 45 (64-bit)
7.0.450
Adobe Photoshop Lightroom 5.3 64-bit
5.3.1
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
9.0.30729.4148
NVIDIA Performance Drivers
2.2.5.0
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729
9.0.30729
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161
9.0.30729.6161
Microsoft Visual C++ 2005 Redistributable (x64)
8.0.59192
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17
9.0.30729
Microsoft Silverlight
5.1.20913.0
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4048
9.0.30729.4048
Microsoft .NET Framework 4.5.1
4.5.50938
Microsoft Visual C++ 2005 Redistributable (x64)
8.0.61000
NVIDIA Graphics Driver 309.00
309
NVIDIA nView 136.53
136.53
WinZip 16.5
16.5.10096

Can you show slideshow within Lightroom 4.4 in Adobe RGB color space?

Can you show slideshow within Lightroom 4.4 (not export out from LR) in Adobe RGB color space provided that you are using a wide gamut monitor which is capable and hardware calibrated & profiled to show such color space?
If this is possible, what is required to do so in Windows 8 and i7-4770 & HD Graphics 4600 platform or does LR take care of it automatically?
This is very basic question, however, I could not find a clear answer/info from LR documentation, so wish that someone can advice.

Those settings are probably stored in a plist somewhere in ~/Library/Preferences. If you can locate the appropriate file, you should be able to copy it to all the network user folders.

Troubleshoot installation problems in Photoshop Lightroom on Windows Vista

This document can help you to resolve system errors that occur while you use Adobe Photoshop Lightroom on Windows Vista. System errors can manifest in many different ways, including (but not limited to) the following:
A blank or flickering dialog box
A frozen cursor or screen
A blue screen
An unexpected restart
An error message such as:
"Setup is unable to load the installation script file."
"Unable to create a directory under C:\Windows\System. Please check write-access to the directory."
"Uninstalling: C:\Program Files\Adobe\Adobe Photoshop Lightroom refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location."
Note: If you attempt to install Photoshop Lightroom to a drive that doesn't have the minimum required space available, the installation will fail. You must then completely reinstall to another location that has sufficient free space.
Many different factors can cause system errors, including conflicts among device drivers, applications, operating system settings, hardware, and corrupt elements in specific files. Although a system error may occur only when you work with Photoshop Lightroom, Photoshop Lightroom may not necessarily be the cause; it may be the only application that uses enough memory or processor cycles to expose the problem.
To benefit most from this document, perform the tasks in order. Keep track of the tasks that you perform and the results of each, including errors and other problems. Adobe Technical Support can use this information to better assist you if you need to call.
You must be logged on as an administrator to perform some of the procedures in this document.
Important: Some of the procedures in this document may initiate a User Access Control dialog that asks for your permission to continue. Read the details in the dialog to determine if you want to continue. If you choose to cancel the dialog, then you will not be able to continue with that troubleshooting step.
The steps in this document that refer to the Control Panel are in reference to the Classic view. For information on switching the Control Panel to the Classic view and many other common OS procedures, see Common Microsoft Windows Vista procedures (TechNote kb401275)
Some of these procedures require you to locate hidden files and hidden folders. Some procedures require you to locate files by their full file names, which include extensions (for example, example_filename.ini). By default, Windows Explorer doesn't show hidden files, hidden folders, and file name extensions that it recognizes.
To show hidden files, hidden folders, and all file name extensions in Windows Explorer:
In Windows Explorer, choose Organize > Folder And Search Options.
Click the View tab in the Folder Options dialog box.
In Advanced Settings, select Show Hidden Files And Folders.
Deselect Hide Extensions For Known File Types.
Click OK.
Note: The procedures in this document are based on the default interface of Windows Vista. If the interface is customized, some procedures may vary. For example, a commonly encountered difference is the navigation to Control Panel from the Start menu: You may navigate Start > Settings > Control Panel instead of Start > Control Panel. Additionally, the procedures in this document assume you are using the Classic View of the Control Panel: To view the Control Panel in the Classic View, click Switch To Classic View on the Control Panel navigation bar on the left side of the window.
Beginning troubleshooting
The tasks in this section can help you resolve the most common system errors. Before performing any of these tasks, back up all personal files (for example, Photoshop Lightroom files you created). Always restart the computer after a system error occurs to refresh system memory. Continuing to work without restarting the computer may compound the problem.
1.Make sure that the system meets the minimum requirements for PhotoshopLightroom.
Photoshop Lightroom may not run correctly on a system that doesn't meet the following requirements:
Intel Pentium 4 or equivalent processor
Microsoft Windows XP, Windows Vista, Windows 7
768 MB of RAM (1 GB recommended)
1 GB of available hard-disk space
CD-ROM drive
In addition to these requirements, a video card that supports 24-bit (16 million) or more colors, and a resolution of 1024 x 768 or higher, is recommended.
* Photoshop Lightroom 1.0 will install and run on Windows Vista but Adobe cannot guarantee the quality of the software experience until Adobe fully certifies Photoshop Lightroom for use on Windows Vista.
To check basic system information, such as processor speed and how much RAM is installed, choose Start > Control Panel > System.
2. Delete previously installed application files, especially if you had the public beta version of Photoshop Lightroom installed.
To delete files from a previous Adobe Photoshop Lightroom installation attempt:
Choose Start > Control Panels > Add or Remove Programs.
Select Adobe Photoshop Lightroom and choose to remove it.
Close the Add Or Remove Programs window and the Control Panel.
Open Windows Explorer.
If the Lightroom.exe file is still in the Program Files\Adobe\Adobe Photoshop Lightroom folder, delete it.
If the Lightroom Preferences.agprefs file is still in the Documents and Settings/[username]/Application Data/Adobe/Lightroom/Preferences folder, delete it.
Empty the Recycle Bin.
Try to reinstall. If you cannot, continue with the next two sections in this step:
Move all the folders under the Users/[username]/AppData/Roaming/Adobe/Lightroom folder into a new folder on the desktop; name the folder Lightroom Presets. These are the presets that were installed with the application and that you created.
Move all the folders under the Users/[username]/Pictures/Lightroom/Lightroom Previews.lrdata folder into a new folder on the desktop; name the folder Lightroom Previews. If you have a large number of images, you can move this folder back to its original location before you open Photoshop Lightroom, once it's installed. Or you can delete this folders to re-create it when Photoshop Lightroom opens. If there are further problems with Photoshop Lightroom after it's installed, it might be due to corruption in the previews, in which case you need to delete this folder and re-create it.
Try to reinstall.Important: Do not delete the Lightroom Database.lrdb file!
If there are further problems with Photoshop Lightroom after it's installed, these issues may be due to corruption in the preset files you created, in which case you need to remove them and re-create them, or test each preset individually.
Note: If you can reinstall, and if this is not the first time you opened Photoshop Lightroom, then Photoshop Lightroom will look for a library database file. If it does not find a library in the expected location, it will prompt you to create a new library, locate the library, or exit. Exit will close the dialog box, and Photoshop Lightroom will not open. Although you can tell Photoshop Lightroom to locate your library, it's best to put it back in the default location and then open the application.
If you can reinstall, close Photoshop Lightroom and then copy any presets you created from the Lightroom presets on the desktop back into the Users/[username]/AppData/Roaming/Adobe/Lightroom folder.
If you cannot reinstall, then move the Lightroom Database.lrdb file from the Users/[username]/Pictures/Lightroom folder into a new folder called Lightroom Database File and save this file on the desktop. This is your database, if you previously had Photoshop Lightroom installed.
Reinstall Photoshop Lightroom. If you cannot reinstall, continue with the next task in this document.
3. Log in as Administrator before installingPhotoshopLightroom.
In Windows Vista, you must be logged in with local (that is, machine) Administrator rights to install Photoshop Lightroom. If you don't have administrator rights, contact your system administrator for assistance.
4. Check the CD and CD-ROM drive.
Dust or dirt on a CD can interfere with an installation and prevent the CD-ROM drive from recognizing the CD. Examine the Photoshop Lightroom CD for dirt, dust, or fingerprints. Gently wipe the bottom of the CD from the center outward with a soft, lint-free cloth.
Verify that the CD-ROM drive can read other CDs. If it can't, examine the CD caddy or loading tray for dirt, and clean it with a lint-free cloth. If it still can't read other CDs, contact the CD-ROM drive manufacturer or the computer manufacturer.
5. Install current Windows service packs and other updates.
Updates to the Windows operating system improve its performance and compatibility with applications. You can obtain Windows service packs and other updates from the Microsoft website at www.windowsupdate.com. For assistance installing service packs and other updates, contact Microsoft technical support.
Important: Before you install a system update, check the system requirements for Photoshop Lightroom (and any third-party software or hardware you may use with Photoshop Lightroom ) to ensure compatibility. If the update isn't listed, then contact Adobe or the manufacturer of your third-party software or hardware.
6. InstallPhotoshopLightroomfrom the desktop and use the default installation folder.
Some system components such as device drivers and virus protection utilities can conflict with the Photoshop Lightroom installer and result in an incomplete or failed installation, or they can cause problems when you install to a folder or when you use a path to the default installation folder that contains a special character, such as #. To prevent these conflicts, install Photoshop Lightroom from the desktop, and use the default folder name and path.
If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
Open the Adobe Photoshop Lightroom folder on the desktop.
Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
7.Re-create thePhotoshopLightroompreferences file.
Re-create the Photoshop Lightroom preferences file to eliminate problems that a damaged preferences file might cause:
Quit Photoshop Lightroom.
Rename the Lightroom Preferences.agprefs file (for example, to Lightroom Preferences.old) in the Users/[username]/AppData/Roaming/Adobe/Lightroom/Preferences folder.
Start Photoshop Lightroom. Photoshop Lightroom creates a new preferences file.
If the problem continues, the preferences file isn't the cause. To restore custom settings, delete the new preferences file and restore the original name of the previous preferences file.
8.Install and run Photoshop Lightroom while no other applications are running.
Some applications may interfere with installing or running Photoshop Lightroom. Virus protection programs are meant to stop viruses from installing on your computer. Before installing or starting Photoshop Lightroom, disable other applications, including virus protection programs and startup items (items that start automatically with Windows).
To disable startup items and non Microsoft services:
Quit all applications.
Choose Start, type msconfig in the Search text box, and press Enter.
Write down all unselected items under the Startup and Services tabs.
Click the General tab, and choose Selective Startup.
Click the Startup tab and select Disable All.
Click the Services tab and select Hide All Microsoft Services.
Select Disable All then re-select FLEXnet Licensing Service. If you are unsure whether an item is essential, then leave it deselected (disabled).
Click Apply, and restart Windows for the changes to take effect.
Note: Upon restart, you'll be notified that the System Configuration utility has made changes to the way that Windows starts up. Click OK. When the System Configuration utility appears, click Cancel.
Right-click icons in the Notification Area and close or disable any startup items that are still active.
9. Install Photoshop Lightroom to a different hard disk after disabling startup items and installing from the hard disk.
Hard disk problems can prevent Photoshop Lightroom from installing correctly. By installing Photoshop Lightroom to a different physical hard disk, you can verify if the original hard disk is preventing installation. First, completely remove Photoshop Lightroom from the hard disk.
To install Photoshop Lightroom to a different hard disk after disabling startup items:
Follow the steps in task 8 above to disable startup items.
If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
Open the Adobe Photoshop Lightroom folder on the desktop.
Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
Click Change and select a different hard disk in the Change Current Destination Folder window. Click OK, and then follow the on-screen instructions.
Intermediate troubleshooting
If the tasks in the previous section don't solve the problem, try the following intermediate troubleshooting tasks.
10. Install and run Photoshop Lightroom in a new user account.
Create a new user account that has the same permissions as the account that you use when the problem occurs. If the problem doesn't recur, the original user account may be damaged. For instructions on creating a new user account, see To add a new user to the computer in Windows Help or contact your system administrator.
11. Optimize handling of temporary files by Windows Vista.
Windows and applications store working data in temporary (.tmp) files that they create on the hard disk. Excessive or outdated temporary files can interfere with performance of Windows or applications.
Delete temporary files by using the Disk Cleanup utility included with Windows or by using the following instructions. Make sure that at least 1 GB of free space is available on the hard disk to which temporary files are written. To start Disk Cleanup, choose Start > All Programs > Accessories > System Tools > Disk Cleanup. For information about Disk Cleanup, see Windows Help.
To manually delete temporary files:
Note: Windows deletes temporary files when Windows and applications close normally. However, when Windows or an application crashes, temporary files can accumulate on the hard disk. Windows may prevent you from deleting some temporary files as they may be in use. Delete as many temporary files as you possibly can, without deleting the files that are in use.
Quit all applications.
Choose Start and type %tmp% in the Search text box and press Enter.
Delete the contents of this folder.
Note the drive letter where this directory is located.
To ensure that at least 1 GB of free space is available on the hard disk to which temporary files are written:
Choose Start > My Computer.
Select the drive noted in step 4. Right click and select Properties.
Confirm the drive has at least 1 GB of free space.
12. Repair and defragment hard disks.
System errors can occur if hard disks contain damaged sectors or fragmented files. Repair and defragment hard disks, either by using the Error-checking tool and Disk Defragmenter utility included with Windows or by using a third-party disk utility. You should run such utilities on each hard disk or partition. More information about the Error-checking tool and Disk Defragmenter appears below; for more information about a third-party disk utility, refer to the documentation for the utility.
The Error-checking tool repairs bad sectors, lost allocation units and file fragments, cross-linked files, and invalid file names. To access the Error-checking tool, choose Start > Computer, right-click the desired hard disk, and choose Properties from the menu. In the Local Disk Properties dialog box, click the Tools tab, and then click Check Now in the Error-checking area.
Note: To prevent Disk Defragmenter from moving files to bad sectors of a disk, run the Error-checking tool before running Disk Defragmenter.
Disk Defragmenter rearranges the files and free space on your computer so that files are stored in contiguous units and free space is consolidated in one contiguous block. To access the Disk Defragmenter utility, choose Start > All Programs > Accessories > System Tools > Disk Defragmenter.
13. Scan the system for viruses.
Use current anti-virus software to check the system for viruses. Virus infections can damage software and cause system errors. For more information, see the documentation for the anti-virus software.
14. Try to install Photoshop Lightroomon a different computer.
Try to install Photoshop Lightroom on a different computer to determine if the problem is unique to your computer. If the problem is unique to your computer, contact the computer manufacturer; if the problem occurs on multiple computers, contact Adobe Technical Support.
Advanced Troubleshooting
If the tasks in the previous section don't resolve the problem, you may be able to resolve the problem by reinstalling Windows Vista and Photoshop Lightroom, reformatting your hard disk and reinstalling Windows Vista and Photoshop Lightroom, or by determining if hardware is conflicting with Photoshop Lightroom.
Disclaimer: Adobe doesn't support hardware and provides these procedures as a courtesy only. For further assistance, contact the hardware manufacturer or an authorized reseller. If you troubleshoot hardware problems yourself, you may void the warranty for your computer.
Note: Before you remove or rearrange hardware, turn off and disconnect power to the computer and any peripheral devices.
15. Log in using the built-in Administrator account.
The built-in Administrator account has a higher access level to the system than a normal local administrator account. By default the built-in Administrator account is disabled. For information about enabling and logging in to the built-in Administrator account, contact your system administrator. You can also refer to this support document on the Microsoft support website: http://support.microsoft.com/kb/926183/en-us?spid=11737&sid=73.
16. Reformat the hard disk, and reinstall only Windows Vista and Photoshop Lightroom.
Reformat the hard disk, and then install only Windows Vista and Photoshop Lightroom from the original installation media. Reformatting a disk erases all files it contains, so be sure to back up all personal files first. Also make sure that you have all application and system disks.
For instructions on performing a clean installation of Windows Vista, see document 918884, "How to install Windows Vista" on the Microsoft website at http://support.microsoft.com.
Note: Don't install additional software or hardware until you're sure that the problem is resolved. Don't back up the hard disk and restore Windows and Photoshop Lightroom instead of reinstalling them. If the problem is caused by an application or Windows, and either one is restored instead of reinstalled, the problem may recur.
After you reformat the hard disk and reinstall Windows and Photoshop Lightroom, try to re-create the problem:
If the problem no longer occurs, then install other applications one at a time and try to re-create the problem after each installation. If the problem occurs after an installation, then the recently installed application may be the cause.
If the problem occurs when only Windows and Photoshop Lightroom are installed, then the cause may be hardware-related, and you should contact the hardware manufacturer or an authorized reseller for assistance.
17. Check for problems with RAM modules.
Ensure that the RAM modules are installed properly and are not the cause of your problem. Do one or both of the following:
Change the order of the installed modules.
Remove all but the minimum number of modules needed to run Windows and [product], and test to see if the problem persists. If it does, replace the modules you removed and remove the others, testing again to see if the problem recurs. If it doesn't, then one or more of the removed modules are the cause. For assistance, contact the RAM manufacturer.

You've tried Help>Updates from within photoshop cs6?
Or this 8.3 updater
http://swupdl.adobe.com/updates/oobe/aam20/win/PhotoshopCameraRaw7-7.0/8.3.52/setup.zip
If that doesn't work, you can install camera raw 8.3 by following the directions on the following page
Adobe Camera Raw Help | Camera Raw/DNG Converter 8.4 on Mac OS 10.6, Windows XP, and Vista

Sending photos to Lightroom over network - what works, what doesn't?

This weekend, my wife and I are helping with a photo shoot (member's photo directory for a local non-profit).
Here is what we've done in the past with Picasa and what we're trying to duplicate:
Photographer takes photos, which are saved onto his Windows laptop via Firewire in the studio.
SyncBack SE running on two networked Windows PCs make copies of the photos from the laptop onto the local hard drives.
Picasa automatically detected the newly-taken photos with its "Watch Folder" feature.
My wife and I do some cropping, adjusting, etc, so that the photos can be quickly reviewed and selected by the customer.
We exported the edited photos into folders in JPEG format.
The photographer takes the JPEGs and uses them to guide his re-edits of the raw photos with PhotoShop.
Ouch! Re-editing wastes a TON of time!
This time, we plan to use LightRoom; this will ensure that our cropping and editing will go right into PhotoShop easily (or so I'm told--I haven't USED LightRoom much yet!)
Big show-stopper: testing (by the photographer) caused duplicate photos in the LightRoom library, mitigated by a manual step or two to import as a work around some LightRoom quirks. And LightRoom doesn't really play nicely with network drives, or so it seems.
I think what we're aiming for is to have a "local catalog" in LightRoom, and have the photos stored in a network drive which it will "watch". That way, all we need to do is export our cropped/edited LightRoom catalogs, which the photographer can import into LightRoom, then it's a quick jump to PhotoShop.
... or is this not the tool for the job?

Per documentation Lr is not a network operation and per several posts in this forum is stated as such. I stopped using Picasa when Lr came out for the public. With PsCS5 another tool comes up as Bridge which I have not used. I have only read the basic Adobe description. Though I do know several Pro Photographers do use Bridge with multiple users even in different states. I do not see why you are editing jpegs for Proofs and as samples for a Photographer to re-edit in a different format, no matter which software you use. My workflow uses RAW files and an Import as DNG along with make a second copy to another folder in Lr and archive of RAW files after a double check of files and I only Export as jpeg after processing. But I only use 1 Lr Catalog and not a network solution.
My way of course is just my opinion of how my service works. Does anyone here also use Adobe Bridge?

Lightroom won't launch

Hello,
When I try to open Lightroom, I am getting a message that reads "Lightroom encountered an error when reading from its preview cache and needs to quit." It states it will attempt to fix the problem next time it launches. I haven't been able to get the program to open for over three weeks. Does anyone know how to fix this problem?
It worked for over three months before encountering this problem.
I have a Dell with Windows 7.
Thanks for any help you can give.

Based on user suggestions and feedback we have updated our documentation on this issue with some new solutions.
http://helpx.adobe.com/lightroom/kb/error-unable-start-correctly-0xc00007b.html
We are locking this thread. If you have more questions or still are seeing the error, please continue the discussion on this thread: http://forums.adobe.com/message/4836005

How do I open a photo from Mac Finder in Lightroom?

Here's the problem: I frequently need to search for photos in the Mac Finder (I actually use HoudahSpot and Path Finder, but it's similar with an exception I note below). I can search for keywords, like "yosemite." But the Finder and QuickLook are rather limiting; they don't reveal much photo metadata if any, and of course they show originals, since any edits or developments are in LR, not in the files themselves. And one does not export willy nilly, for that would defeat the purpose of having a DAM.
So far, OK (I'd love to have LR integrated into more applications, as Aperture and iPhoto are in some "Insert" menus, or in dialog boxes, but that would be too useful...maybe the new Photos application? ). So I'm looking at a jpeg (because Apple still doesn't have support for my RAWs, but same result) that I think I wanna use. And I want to find it in Lightroom. But if I double click it, of course I'd get Photoshop or whatever application is the default for images. In Path Finder or some other utilities, unlike the Finder, I can actually select open in LR. But when LR does open, it shoots me to the import module. Not what I want.
So, if one is looking at an image file in Finder, or otherwise outside LR, how does one easily and quickly go to that image in LR, in the Library module? sort of a "find in LR" command?
I was looking around for Applescripts or Automator workflows, but only find ones that import, not find. There's an automator "find in iPhoto" step, but interestingly the Aperture one is deprecated. I thought I might have been able to modify it.
GraphicConverter has a very nice "service," "GraphicConverter: Open in Browser" that does exactly what I want. But I couldn't find one for LR (and it's kinda hard to search successfully online for "services" related to LR, and I didn't find any services).
Ideas?

I have written the Lr (plugin) side, and created the capability to use Windows "Send to..." context menu to send a list of folders/files to Lightroom for selection.
Here is the content of the god-aweful command file which does it in Windows, 'Lightroom File Selector.bat':
@echo off
for %%x in (%*) do (
    call :concat %%x
start "%~n0" "lightroom://com.robcole.FileListener/Select/%pstr%"
exit
:concat
set a=%1
set lc=%a:~-1%
if "%lc%%lc%"=="""" (
    set pstr=%pstr%[%a:~1,-1%];
) else (
    set pstr=%pstr%[%a%];
Note: what it's doing is wrapping/separating all the folder/filenames received as arguments to the bat file, then appending them to the base url, for example:
If you select folder "C:\MyFolder' and file 'C:\MyFiles\myfile.jpg' in Windows Explorer, then invoke the 'Send to' context menu item (or drag and drop directly on bat file), it will send the URL:
lightroom://com.robcole.FileListener/Select/[C:\MyFolder];[C:\MyFiles\myfile.jpg];
to whichever app is registered to handle it, i.e. Lightroom, which parses the plugin ID, and passes it to the plugin, which then parses the paths and then does the same thing as the "Choose Files Via OS & Select In Lightroom" script.
Although I haven't got the Mac end, the goal would be the same - somehow translate the target folder/file paths from the format they're in to the requisite URL format and submit to OS, which submits to Lr, which submits to plugin.
You can download the plugin here:
http://robcole.com/Rob/_common/DownloadEasy/Download.cfm?dir=FileListenerLrPlugin&file=rc_ FileListener_(lrplugin)_1.0.zip
There is no web page nor documentation for it, yet.
Rob

Drag&Drop from Lightroom to Premiere doesn't work! Programming an alternative?

Unfortunally the is no working Drag&Drop ability to drag a videofile from the Lightroom Library into the Premiere Project View.
(This Problem appears only on a Windows machine not on Mac)
This is becaus if you send a (valid) filepath to "Adobe Premiere Pro.exe" as a parameter it doesn't do anything! Why that?!?!?
It makes no difference if you drop a file on "Adobe Premiere Pro.exe" or if you use the windows command shell like "C:/...<path to premiere>.../Adobe Premiere Pro.exe" "myfile.avi" , simply nothing happens - at least with Premiere Pro CS5...
So the Idea is to build an Lightroom Plug-In, that opens an exe-file with the filepaths of the currently selected Viedeos from the Lightroom Library as parameter.
The exe-file should pass the information to an opened Project in Premiere an load the Videos into the Project.
With ExtendScript Tool i can get this behaviour with this code:
var myFiles = ["C:\\01.avi, ..."];
app.project.importFiles(myFiles);
I don't think that the Premiere SDK will help me out, because with that I can only build Plug-Ins that work INSIDE Premiere. I need a Executable that can send information/files to Premiere from Outside. The only thing I can think of is to load the right dll-file and call the function() for importing files to Premiere (I think this is what ExtendScript Tool does ), but I don't know how to start, because nothing is documented about the dlls...
Any Ideas

EDIT:
Ok, I identified the dll which is importing Video-Files to Premiere: HSL.dll
At my pc it is located in:
"C:\Program Files\Adobe\Adobe Premiere Pro CS5\"
The function that is called is named ImportFiles(...)
That's the whole code, reverse engineered:
HSL::ImportFiles
    std::vector <
                std::basic_string <unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >,
                std::allocator <std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > >
                >
    const&,
    bool,
    bool,
    std::vector <
                ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem>,
                std::allocator<ASL::InterfaceRef<BE::IProjectItem, BE::IProjectItem> >
                >&,
    std::vector <
                std::pair<int, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > >,
                std::allocator<std::pair<int, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >
                >&,
    ASL::InterfaceRef<BE::IProjectLoadStatus, BE::IProjectLoadStatus>&,
    DLG::ImportFromEDL::ImportFromEDLDialog*,
    std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const*,
    DLG::ImportFromEDL::ImportNewSequenceMediaParamsDialog*
Can anybody "read" that , or anybody know how to get this working with c++?

Lightroom image management - ready for professionals?

Hi
I have a client, which is doing professional gardening photography for various magazines in this topic. Her business ranges from magazine reports about individual gardens to delivering single images to different publishers as requested (for example by flower type, color etc.). The main thing is that her image portfolio isn't organized so much in individual shoots or contracts. An image can be sent to many publishers at any time. She needs to kepp track of this. She needs to know, which image has been published when and where.
Before moving to digital recently, she kept track of here jobs with cumulus, which had more database capabilities, but much less possibilities in image adjustment. Shooting only raw with a Canon 1 series camera, she choosed Lightroom as here image editing and managing tool. Beeing pleased with the friendliness of the user interface and many of its image editing and managing capabilities, she (actually we) are astonished, that even in a version 2 it is still not really possible to keep track of what happens to the images in a professional environment (despite the claim of Adobe that the product is made for professionals).
In essence the program isn't really capable of managing image data, which has a one to many relationship to the image (i.e. the instances of cases an image is sent to a customer). We experimented with virtual copies, which can carry individual metadata, collections (which cannot carry metadata) or storing the required data in the large description field. None of these possibilites were really satisfying. The most promising solution in using virtual copies, ended up in a maintenance nightmare, because it was too easy to forget, where to do which data management (at the master raw file or at the virtual copy).
Then, I learned that with Lightroom 2 there is a possibility to extend metadata, but, unfortunately with the usual limitation of not supporting one to many data (in the SDK-documentation called "spreadsheet type data"). The rest of the SDK documentation did not reveal any other helpful way of solving the problem as the SDK deals mainly with export plugin programming or web stuff, which is of no use to the client. It is rather disappointing that Lightroom's extensibility is still so limited. Where is the programming interface, that allows the development of complete new modules?
Given the slow pace, Lightroom development takes (I can expect that "breakthrough" extensions to the SDK will take even longer), I guess that my client can wait for another 3 or 5 years until anything close to true image management will come up.
So we have to look for some intermediate solutions. Whereas other software (expression media, idimager, cumulus) may have better database capabilities, they lack in raw editing completely and are often more awkward to use. Therefore, I would like to ask the community here, how they handle the tasks described above with Lightroom or with other tools? Perhaps we have overlooked a Lightroom capability?
One thing I thought of is to develop a special keyword hierarchy for contracts, but this also would not allow, all the images tracking needed.
Any ideas? I guess there aren't any plugins, which can deal with one to many data.
Kind regards
Thomas

Actually, we haven't ruled out keywords yet, in fact, at the moment it seems to be the only realistic possibility. However, I wonder if a growing keyword hierarchy can become unwieldy at the end, so I am sceptical, if this idea would deliver.
In general, I think that Lightroom should more move into the direction of beeing a platform for other vendors. The limitation to web stuff and export solutions isn't enough. I hope to see third party vendor modules, eventually one which provides more professional image management and tracking capabilites, exploring the fact that Lightroom has a database underneath it.
I would like to see a DxO raw conversion module or a lens correction module, fields where I think Lightroom and ACR are still not the best in its class (I think LightZone and DxO are the better raw processing engines).
Unfortunately, I do not see Lightroom going much into this direction. Probably this is already too late for the version 3 release, due in 2010 (?), so we need to wait until v4 (in 2012 ?) until the situation improves?
I believe many customers (especially professionals with precious time) need a fully integrated system, which can do image management and image adjustment at the same time. Lightroom is the right platform for it, if Adobe let it be.
Kind regards
Thomas

Lightroom 4 on Windows 7 no longer opens

My installation of lightroom 4.2 on Windows OS7 has been working fine until Saturday November 3. Now it generates this error: "The application was unable to start correctly (0xc000007b).Click OK to close the application."
I have uninstalled iLivid as suggested in the user Forum. I uninstalled Lightroom 4 and reinstalled. It said it installed successfully, yet I still get the same error.
I'm dead in the water here...is there a solution out there?
Diane N

Based on user suggestions and feedback we have updated our documentation on this issue with some new solutions.
http://helpx.adobe.com/lightroom/kb/error-unable-start-correctly-0xc00007b.html
We are locking this thread. If you have more questions or still are seeing the error, please continue the discussion on this thread: http://forums.adobe.com/message/4836005

Windows 8 Upgrade - 64-bit version of Lightroom -application error 0xc000007b

I've just upgraded my Desktop PC from the 64-bit Windows 7 operating system to 64 bit Windows 8 Pro. The migration has gone very smoothly, with justone exception - Adobe Lightroom 64-bit version 4.2 won't start up. As soon as I try to open the application it comes up with an error code of 0xc000007b.
Searching the web I've seen a number of suggestions which I've tried to to avail...
- uninstal, restart and then reinstall Lightroom. Same 0xc000007b error
- uninstal, restart, run ccleaner to clear registry issues, restart, download the latest version of Lightroom from Adobe website (4.2.1) and then reinstall Lightroom. Same 0xc000007b error
As a workaround I found that uninstalling Lightroom 64-bit and reinstalling the 32-bit version (by selecting the setup32.exe program, rather than using the install Lightroom 4.exe program) gives me a working copy of Lightroom again. This does however mean I'm using the the 32-bit version of Lightroom, rather than 64-bit version that I had working before the upgrade to Windows 8.
Why am I getting the 0xc00000fb problems with the 64-bit 4.2.1 version of Lightroom and how can I resolve the issue so I can go back to the 64-bit version that I had working in Windows 7 immediately before upgrading to Windows 8?
Thanks for suggestions!

Based on user suggestions and feedback we have updated our documentation on this issue with some new solutions.
http://helpx.adobe.com/lightroom/kb/error-unable-start-correctly-0xc00007b.html
We are locking this thread. If you have more questions or still are seeing the error, please continue the discussion on this thread: http://forums.adobe.com/message/4836005

Lightroom 1.1 Documentation

Similar Messages

Maybe you are looking for