September 2, 2008
It seems that nVidia users seem to draw the short straw with Lightroom. When Version 1 was released, it took a while to find out that certain performance issues were due to the use of nView. Now with Version 2 it seems there are different performance issues with nVidia.
However Flickr user MarkW Photo has found settings that greatly aid in the speed of the brush tool for Lightroom 2 nVidia users.
“I have finally fixed my slow performance issues with LR2! Today I did a bit of playing around with different performance settings. I’m using LR2 on a HP Pavillion 6258se Laptop. It has an 80GB Hard Drive, 2GB of Ram and the processor is a 1.8 GHz AMD Turion ™ 64 X2 Dual-Core. I had Windows Vista installed months ago but I downgraded back to XP due to Vista issues. First I opened the windows task manager so I could monitor the performance of Windows while using LR2. I noticed when using the develop tasks the performance stayed around 50%. When I used the retouch brush tools the performance still stayed around 50% but the brush tools were still slow. The more I brushed on the image the slower the brush refresh became. This told me that there must be a video performance issue and not necessarily a processor problem.
December 29, 2007
Ian Lyons has posted an excellent tutorial on printing from Leopard with Lightroom 1.3.1. He’s specifically targeting the Epson range of printers using the new 6.X range of Printer Drivers.
“This tutorial will concentrate on what is known as application color management, which basically means that the ICC profile associated with a particular paper/ink combination must be selected in Lightroom rather than the print driver itself. Also, since the tutorial is intended to be useful to new and existing Lightroom users I will also include some of the basics associated with Page Setup and saving Print Templates.”
Read the whole article.
December 17, 2007
Author: Tom Hogarty
Source: Lightroom Journal
One of the most common issues Lightroom users have been having is print output. Particularly those mac users who have recently ugraded to the latest Leopard Max OS X 10.5 operating system. In this blog post, Tom Hogarty outlines some of the reasons why this can be so and points out the need to update the print drivers for your printers. If you are experiencing print output problems from Mac OS X 10.5, do read this post and use the Comments section to cross check with other users and their shared findings.
December 3, 2007
Source: Lightroom Journal
From the Lightroom engineering team come a few pointers on known compatibility issues with Lightroom 1.3 and the Macintosh OS X 10.5 OS:
The Lightroom 1.3 release addresses many Leopard OS X 10.5 issues but a few outstanding problems remain or have been discovered.
- Time Machine compatibility still remains unclear at this time. Running Time Machine backup or restore operations while Lightroom is in use is not recommended until more information can be obtained. Interim solutions:
- Have Time Machine exclude the directories where Lightroom catalogs are stored and use Lightroom to backup the catalog files
- Run Time Machine when Lightroom is not running.
- There is a bug in the Lightroom 1.3 Print Module that can cause the application to crash on either OS X 10.5 or 10.5.1. Minimizing the template preview in the upper left corner can help reduce the frequency of this issue.
- The Finder in Mac OS X 10.5 and 10.5.1 can crash when viewing files that contain Lightroom XMP Snapshot data created in the develop module. This is an error in how the Finder reads metadata and will require an operating system update to solve. (I believe that this occurs more frequently with JPEG or TIFF files)
- Importing directly from a card may not copy all of the image files or may fail. Please copy the images to a local drive using the Finder first if you experience problems.
We will provide an update to address the print module issue but have not set a release date for that update.
November 21, 2007
Author: John Beardsworth
John Beardsworth is a member of the core Adobe Lightroom beta testing team, so as you might expect, he should know a thing or two about Lightroom and in particular how to organise photos in a catalog, which is one of his main specialities (apart from being a professional photographer too). So I was interested in the following article where John expresses his views on the usefulness of multiple catalogs.
Just because you can, it doesn’t mean you should : one or many Lightroom catalogues
Lightroom 1.1 made it easier to create and work with more than one catalogue, and it’s making some people think that’s how they should work. I’m not talking about when you’re travelling or need to move pictures between computers, but as a routine way of working. Apart from seeing it in blog posts and forum threads, I’ve been asked about it on a couple of occasions recently, and was also forwarded a discussion where one photographer quoted from my book:
November 5, 2007
Ian Lyons of Computer-Darkroom, has pin-pointed a problem with the latest Mac OS X 10.5, Leopard Apple operating system and finder crashes when navigating photos with the new CoverFlow navigator, where the photos have had the metadata saved to them via Lightroom. The following extract is taken (with permission) from a thread currently running on the Adobe Lightroom User to User forums in which Ian has come up with a workaround to this bug. Hopefully Apple will be able to address this metadata compatibility issue in a future OS release.
September 15, 2007
Andy Rahn, from the Adobe Lightroom team, has an excellent walkthrough on solving an installation issue with Lightroom 1.2. What is a clever move on the part of the installer, is turning out to be a problem for a number of non English users. Basically Lightroom checks your regional settings and installs itself with the relevant regional language, even with the installer in English (French & German being the other languages in the normal installer). Not all users want to use this version and would prefer to work through English. This article shows how to get the English version instead of the regional version.