Jul 18, 2006

Adobe Lightroom Beta 3 for Windows Released

Adobe has released the long awaited Adobe Lightroom Beta 3 for Windows.
Note: the main Lightroom website has not yet been updated but the Windows download for Lightroom beta 3 is listed on the download page as of 9:20PM Pacific…

After months of discussion on the Lightroom User Forums (and not so patient waiting by Windows users), Adobe has finally released the Windows version of Adobe Lightroom beta 3. Yes, it’s available for downloading from Adobe Labs.

So, just how close is the Windows version to the Mac version? Pretty darn close with a couple of features missing. There is no Web module in the Windows beta 3. That will come, probably in the next Lightroom beta. There are also some smaller aspects that are missing such as the Identity Plate (aka Vanity Plate), no music yet for the Lightroom Slideshow, no “Lights Out” screen mode and no drag and drop importing except when using the Auto-Import feature.

But the rest of the Windows beta 3 matches up surprisingly well to the Mac beta 3, a testament to Adobe’s platform agnostic coding and the desire to bring equivalance to both platform versions of Lightroom. To compare, check the June 12th PhotoshopNews story on the release of the Mac beta 3.


Click on the image to see a larger version in a new window.
Aside from the Start menu at the bottom of the screen, the Windows version looks and behaves pretty much like the Mac version, with the typical caveats about keyboard commands: Option (Mac) equals Alt (Windows) and Command (Mac) equals Control (Windows). The look and feel and general usability are the same. The figure above is the standard Library grid view.

Shift selecting multiple images and selecting the Compare button allows you to compare multiple images at once.

Click on the image to see a larger version in a new window.
This figure has had three images selected, although the brown image is “most selected”, a concept that implies that one image will be the actively worked on image.

Click on the image to see a larger version in a new window.
Clicking on the space bar will bring the most selected image to either fit or fill the center panel.

Click on the image to see a larger version in a new window.
Zooming into the selected image allows either 1:1 or 4:1 screen viewing.

In the navigation preview, you can choose the behaviors of the zoom function. You can have the image either Fit or Fill. Fit allows the entire image to be visible based upon your panel sizes and Fill will fill the image top to bottom. The zoomed in options currently are 1:1 or 4:1. One would hope that zoom options will be expanded to 2:1 and 1:2 in the future. Unlike Photoshop, there really isn’t a strong need for infinite zooming in Lightroom.


Click on the image to see a larger version in a new window.
Clicking on the Develop module (or Control 2) will bring you into the Develop module of Lightroom where more precise image adjustments can be made.

Click on the image to see a larger version in a new window.
The Windows version has the same Before/After viewing options as the Mac version.

Click on the image to see a larger version in a new window.
You can zoom into the Before/After mode as shown above…

Click on the image to see a larger version in a new window.
…or use the Split Screen option that first appeared in the Mac beta 3 version.

All of the controls are the same in Develop between the Mac and Windows versions including the presets and the history feature. In fact, with the exceptions of the missing features, the Windows version is said to be “bug for bug” the same as the Mac version.


Click on the image to see a larger version in a new window.
The Slideshow module in the Windows version works the same as the Mac version, except no music yet for slideshow presentations. That will come.

Click on the image to see a larger version in a new window.
The screen transition is rather smooth (if you have a decent video card). The figure above is a screenshot of the slideshow in “Preview” mode.


Click on the image to see a larger version in a new window.
All of the functionality of the Mac version of Print lives in the Windows version, for the most part. It’s unclear if the two main options of either letting the Printer decide color or using ICC color profiles will behave exactly the same as the Mac version due to the fundamental differences found in the platform pipeline.

Clicking on the lower left Page setup or lower right Printer setup will bring the Windows print driver up.

Currently you can print either by allowing the profile and color to be managed by the printer or select “Other…” as shown below.

The Other will allow you to select from the currently installed ICC color profiles in your system. The screenshot above shows the profiles I’ve selected to view in the drop down menu.

Click on the image to see a larger version in a new window.
Clicking Other brings up a profile selection dialog box to allow you to choose which profiles show up in the menu, useful if you have a lot of profiles.

After selecting the profile, you determine which rendering intent you wish to use.

It should be noted that the option to print using Managed by Printer is currently a problem. The only accurate color I’ve been able to print is by using the option to allow Lightroom to manage the color using the selected profile I’ve chosen. When printing this way, I get equal results from the Mac and Windows version using the same printer profile.

Click on the image to see a larger version in a new window.
After selecting the Lightroom and printer options, right-click on the template if you wish to save the settings to that template. This function is one of the better printing advances to come out of Lightroom. One difference between the Mac and Windows version is that the Print button in Windows always pops the print dialog. In the Mac version you can bypass the dialog by pressing the option key when clicking the print button.

Click on the image to see a larger version in a new window.
As in the Mac version, the Template Browser allows for a wide range of printing options. You can choose to make contact sheets as shown above and have very good control over sizes, spacing and position. You can also choose to print out image information as well as numbers on the contacts. At this point in beta 3, the output sharpening is somewhat weak. Hopefully that will be addressed.


I may catch some flack from George Jardine, Pro Photography Evangelist from Adobe for using his “mug” as the example images for describing the Import functions of Lightroom. But what the heck, what’s he gonna do to me?

Import is under the File menu and is the critical stage where you bring images into Lightroom. You don’t “Open” or “Save” them – you bring them into the Lightroom database. The following options are critical to understand and employ.

The first option is whether to reference your images in their existing locations or copy or move the files into your Lightroom Library. This can be a bit confusing at first, but once done one way to a series of images, it’s very difficult to change without just doing a new import of those images. So this is an important consideration. Reference means Lightroom notes where the image are (the exact directory path of the folders) and uses that reference to track the images. However, moving or renaming those files can cause problems down the road.

The other options, to move or copy, means the files will physically be moved or copied into your actual Library. This is simplier and easier for Lightroom to keep track of but less flexible than referencing. The last option, Copy as DNG is an interesting twist in that you can actually make a Linear DNG out of a tiff, psd or jpg image and bring it into Lightroom as a DNG. Note: you can still bring jpg/tiff/psd (with layered composite saved) and treat them with Lightroom adjustments. But those adjustments won’t actually be applied until you export the files.

You can choose to import images either by Date or Folder. By date is more useful for importing images directly from flash cards, by folder is the way you would want to import if your images are referenced and in specific named folders.

When importing, you can choose to create a metadata preset, or use one you’ve already created to aid in the process of metadata editing. The figure above shows the dialog to create a new preset.

Also, when importing you can choose to apply your own base Develop settings upon import.

At this point, there are only two times when you can actually rename files – when you import and when you export. So, if you have a naming convention you wish to use, do so upon import. It’s hoped that library file renaming will be incorporated into Lightroom, but for now it’s a limitation.

The renaming function is powerful, allowing you to edit filename text and tokens such as numbers, dates and even adding certain fields from the Exif metadata to the file name.

Click on the image to see a larger version in a new window.
Ok, this is the shot that George might get ticked about…but hey, he was the one willing to turn his hat around and look goofy, I just shot it and included it here in the story.

Click on the image to see a larger version in a new window.
I decided on a single series and wanted to select the best of that series. Here I’ve brought five images into compare to select a favorite. To be fair to George, on many of the images his expressions are rather good and even George liked most of the shots. I burned a CD for him with his selects as DNG files. You may notice there is a readout on the upper right corner indicating “1 operation in progress…”.

This is an indication that Lightroom is doing a background process. While working in the background, foreground operations can be a bit sluggish. Hopefully, the current beta speed of both the Mac and Windows will get a good round of code optimization before version 1.0 ships.

Click on the image to see a larger version in a new window.
I chose one of the images for fine-tuning and decided on a grayscale conversion with a bit of split toning to simulate a sepia tone with the highlights warmed and the shadows cooled.

Click on the image to see a larger version in a new window.
I wanted to apply this setting to all of the shots so I created a Develop preset called “Subtle Sepia” (I find the default sepia a bit over the top colorwise).

Click on the image to see a larger version in a new window.
In the figure above, I’ve returned to the Library grid and selected all. I’m selecting the just saved preset from the Preset drop down menu and that will apply the setting to all the selected images. I’m tempted to make a comment about the wine glass shot, I can’t remember exactly what we were drinking at that stage, but I suspect it was something Greg Gorman had opened. George, do you remember?

Click on the image to see a larger version in a new window.
Here the Subtle Sepia setting has been applied to all of the images. I actually got some nice shots of George that night as well as a few others while they were in my studio during the weekend of the Chicago Epson Print Academy. You can see additional shots in my story On the Road to Washington DC and scroll to the bottom of the story.

Click on the image to see a larger version in a new window.
One of the things some people misunderstand is how to easily apply Develop settings to more than one image. There are three ways; Copy Settings, Syncronize and Copy Previous. In the figure above, I have two images selected. Note that the figure is showing the fact I’ve set the ranking of the top image to 4 stars. I did that by using the keyboard shortcut of clicking the number 4 key.

Click on the image to see a larger version in a new window.
Whether you Copy Settings or use the Synchronize Settings option, you’ll still get a dialog box allowing you to select which parameters to use. At this point, there is no drop down to select subgroups as there is in Camera Raw. I hope that gets into a future version. It’s also a bit vague as to the relative benefits between Copy and Sync. Each command will apply the settings to any selected images. Currently, when in the Develop module, there is no way to have the current image settings be applied to other selected images as there is in the Filmstrip mode of Camera Raw. Copy and Paste settings started in Bridge while Synchronize Settings started in the Filmstrip mode of Camera Raw. Here in Lightroom we have both options.

The Copy Previous is somewhat confusing in that it selects all of the parameters of the last selected image and applies them to the currently selected image/images. Use this option with caution because you can’t differentiate between subsettings as you can with Copy and Sync.

Click on the image to see a larger version in a new window.
Going back to the Library grid view, I’ve chosen to to sort these images by rank. This allows for putting the top ranked images at the top and makes it easier to select images for putting into a slideshow or printing.

Click on the image to see a larger version in a new window.
In this figure, I’ve sorted the images based upon rank. I’ve also used the tool panel options to collapse most of the tools. As you can see on the right Info panel, there is a single keyword already entered: Antarctica, which was entered when I imported the images initially into Lightroom.

In general, my approach is to enter as many global keywords for a specific shoot as is possible upon first import. However, the granularity of the keywording is then enhanced, often image by image. The more metadata I can enter into the image, the easier it will be to organize and find it, down the road.

The Metadata panel allows for quick groupings of various metadata views. The previous figure had the “Quick Describe” view.

I can also select the IPTC view to show and allow complete IPTC for XMP compatibility. It should be noted, however, that keywording and other metadata is not actually embedded into the image while working in Lightroom. Lightroom stores all the metadata in its database and applies it to images only upon export (or opening into Photoshop).

Click on the image to see a larger version in a new window.
In the event you have imported images by reference, the exact location of the image on your hard drive is important. Lightroom offers you the ability to find exactly where the image is located by clicking on the File Path button.

Click on the image to see a larger version in a new window.
This will show you not only where the image is located but actually open the directory where the file is contained.


The fundamental concept of Lightroom is a database driven image organization application. As such, there is no “Open”, “Close” or “Save” in Lightroom. You import images to get them into Lightroom and when you need to use the images elsewhere, you Export them. This is the Export dialog where you control where the file will be exported, the name, the file format and color space (if appropriate) as well as the image size and resolution. Think of this as Lightroom’s “Image Processor”.

The export naming options allow you to use your own naming convention and use tokens as the Import dialog allows.

You can also choose the file format. Note: at this time, exporting an image as a DNG will only be fully compatible with Lightroom as Camera Raw & Bridge do not yet understand Lightroom raw settings. The other image metadata will, however, be embedded in the file.

If you choose TIFF, PSD or JPG as a file format, you can choose the color space in which to export your files. Yes, there is only a choice of three color spaces, but this is a situation where less is more. It should also be noted that as of beta 3, there is still an issue where down-sizing in Lightroom produces less than optimal results. Adobe is aware of the issue and it will be addressed in the future, but down-sizing should only be done in Lightroom where optimal quality is NOT required.

The Preferences for Lightroom are simplistic at this point in time but hold some important features and functionality options. In the General tab, the Build previews in background option can impact the relative speed of thumbnail and preview generation. Clicking this option allows Lightroom to work in the background creating and loading previews but this option can slow down the overall Lightroom response. If you have a real fast machine you probably will want to keep this option on, but if you are working at the low end of speed, turning this option off will improve UI response time at the expense of fast building and loading of previews.

Under Import the important feature is the Auto-Import function of setting a “Watched” folder. This allows you to designate a specific directory or folder for Lightroom to watch while running. As soon as an image or folder of images is copied into that folder, Lightroom will auto-import the images into Lightroom. This is particularly useful when shooting tethered or when shooting multiple cards on a shoot. You can setup the way in which Lightroom will handle the file naming, shoot organization and additional info such as metadata embedding, Develop settings and initial keywords. Done once in the morning, an entire day’s worth of shooting can be auto-imported simply by dropping the images into your Watched folder.

Under File Management you can tell Lightroom what size to set your image cache. If you are working on a small portable computer, you might need to lower the cache size to limit how much disk space Lightroom will cache to. Doing so will reduce the amount of caching size and require more time for preview and thumbnail generation. If you have a big drive with plenty of free space, you’ll get better performance by setting to the max.

Under Interface you can choose the main Fill Color for the Lightroom background canvas and the Overlay Texture as shown below. This portion of the Interface preferences will probably grow in the future.

If you are interested, the screenshots for this story were done on an Apple MacIntel 17″ iMac with 2 gigs of ram, a 1.83GHz Intel Core Duo chip set running Windows XP (SP2) via Apple’s Bootcamp. The performance was rather respectable considering I was running a “foreign” operating system. I also tested the Windows version on a Dell with a Pentium 4, 2.8 ghz and 2 gigs of ram. The Core Duo machine was noticeably faster.

For Windows, Adobe Lightroom beta 3 requires Windows XP with Service Pack 2, an Intel Pentium 4 processor, 768 MB of RAM (1 GB recommended), and 1 GB or more free hard drive space, and a monitor with 1,024 x 768 screen resolution. So far, not much in Lightroom seems to be using GPU acceleration, so your graphics card will not play a huge role in performance. I hope that changes.

If you are regular visitor to the Lightroom forums, you’ll have noticed that the Windows forum has been populated with a variety of characters who seem to be taking great joy poking fun at and generally deriding Adobe for not releasing a Windows beta if not first, then at least shortly after the release of the Mac betas. I can tell you that Adobe would have loved to have released a Windows beta a long time ago, but the realities of cross-platform engineering prevented that.

The original Shadowland Application Icon

Lightroom (code named Shadowland) first started development on the Mac and it took an enormous effort by the engineers to bring platform equivalency to Lightroom. To read more about the trials and tribulations of Shadowland, read the PhotoshopNews story The Shadowland/Lightroom Development Story

In particular, Seetha Narayanan (AKA “Seetha”) came onto the Lightroom engineering teams and whipped up some solid code. You can read more about Seetha’s Fan Club in this PhotoshopNews story from last year. You can also listen to the Lightroom Podcast #6 to hear Seetha, Zalman Stern and Dave Story talk about some of the challenges of cross-platform development.

That’s not to say there weren’t a ton of other people busting butts to get the Windows version out. There were a lot of engineers in both San Jose as well as Minnesota that were pulled off feature development for the Windows effort. You can meet some of those engineers in the PhotshopNews story A Visit to the Adobe Lightroom Engineers

So, there you have it, the Windows version of beta 3. Adobe has fulfilled their promise to release the Windows version of Adobe Lightroom “in the summer” and now users from both platform camps can hammer and test the public beta of Adobe’s new application currently named Adobe Lighroom.

To download the Beta 3 or to get involved with the forums, be sure to visit the Lightroom home on

25 Responses to “Adobe Lightroom Beta 3 for Windows Released”

  1. Chris Says:

    It runs like crap on my Athlon 3700 w/2GB of memory. Impressive.

  2. Jeff Schewe Says:

    Well, it runs ok on a Pentium 4 2.8 ghz and runs rather nice on a iMac Core Duo with 2 gigs of ram running XP via Bootcamp…what sort of files are you improting? Since your post was @ 11:42pm, can you honestly say that you’ve actually done anything other than download it, install it and started playing?

  3. Mark Says:

    After messing around with it for a bit here are some random thoughts:

    -It seemed to take as long as Bridge to cache my .nef files initially. Panning photos at 100% is a bit faster than Bridge but it seems to take significantly longer to actually apply changes to the preview. It takes a really long time to fully resolve the photo at 100% intially.

    -The interface is aesthetically pleasing but I have to wonder how much overhead is due to all the fancy transition fading/zooming. I don’t really care about perfectly smooth zooms from 10%-100% if it means a huge memory footprint, frequent 100% CPU utilization spikes and/or massive hard-drive caching and thrashing.

    -The library/develop/slideshow/print framework is pretty well set up. It would be nice to have hotkeys to switch between the different modes so that you can permanently hide the outsize top bar.

    -The combination of the pan and zoom tools is a bit awkward. Maybe make left-click for pan and right-click for zoom? It would also be nice to be able to double-click a photo to switch between grid and loupe modes.

    -The curve diagram needs to be grabable. The greyscale mixer is great. Split-toning looks to be useful.

  4. Biofx Says:

    I run on Athlon 64 3500+ with 2go ram, and it’s pretty slow….Compare to iview.

    I hope the final speed execution will be increase, especially in view path.

  5. Andy Says:


    While I am waiting for Lightroom to generate it’s database and thumbnails of my images on my laptop (1.5hrs so far :-( ) I wanted to ask you something Jeff …

    I took another look at your Mac-LR-B3 introduction on JUNE 12th. I noticed in the first screenshot of the Windows version running on your Mac what seems to be a “web” module in the top right-hand corner of the screen. Was this the case? Did your pre-release copy have the “web” module? It is not clear in the photo. Do you believe it is Adobes intention to release a “B3 update” in the month or so to complete the B3 functionality on PC? I am just curious as I think it is important for Adobe to syncronize the functionality of the PC version to that of the current Mac B3 before we (possibly) get a B4 in a few months.

    Andy :-)

  6. drak Says:

    Its work faster when imac core duo on P4 3.4 and Windows Xp
    interface it good, but sometimes some sliders are slowly open and close.
    we are waiting a release =)

  7. Harrie Frericks Says:

    It doesn’t run at all on my XP SP1 machine (let alone earlier NT versions)


  8. drak Says:

    to Harrie Frericks

    it need WinXp SP2

  9. ian Says:

    It will not run if your my docs folder is mapped to a network drive. I had to log in as a local admin to get it to work.


  10. A Wise Says:

    I don’t know why these posters are complaining about.

    Works excellent on my windows machine Dell XPS 400 3.06 Dual Core with 3gb of ram with my 24″ monitor.
    off course on an old jalopy PC it won’t work fast, what did they expact?

    Note to all Windows Users: YOU NEED A LOT OF RAM for any digital imaging work, AND take care of your PC clean it from all the mess out there.

    Adobe-Lightroom engineers, keep up with the great work I am especially grateful to you, you are making my life easier.

    A Wise

  11. Chris Says:

    My computer is not an “old jalopy PC”. Lightroom should not require the kind of resources it uses for simple raw processing. It takes around 13 seconds to generate a full size preview of a 30D raw, whereas ACR takes 2-3 seconds and Capture One is even faster. Lightroom also uses 99% CPU for most of the time it’s open. Capture One has one of the worst interfaces I’ve ever come across, but at least it isn’t such a resource hog.

  12. TrudyKAS Says:

    I am delighted to leard that Lightroom is finally available for Windows. Having followed the development of the Mac beta, I know that it will have some advantages over PSCS.
    I’ve been using PS since version 5, and Corel products before that on Windows.
    Thousands of images on negative and slides over the past 58 years, some are scanned and archived.
    Just a few common problems though, with Lightroom!
    I have established at least half a dozen passwords with Adobe and Macromedia over the years, and a common thread is recurring.
    Adobe will not recognize my password, and even though I have tried each and every password several times, reported several times that I have “forgotten my password”, the email message to update the password is not to be found. aLL THAT SINCE ABOUT 10:00 a.m.
    I’m sure I will get to see Lightroom operating on my system in a few days. I am patient. Things should go a lot more smoothly when the downloading buzz slows down.

  13. Josh Says:

    Lightroom wasn’t very snappy on my olde Powerbook G4 laptop with a 5400rpm hard drive and 1.5GB of RAM. Though it worked ok, I never took the time to test it beyond loading a couple of sample images – the laptop is far less pleasurable to do digital postprocessing on than my Athlon X2 4400+ desktop with 4GB of RAM, a 10kRPM hard drive, and a 21″ LCD.

    Having just downloaded it an hour ago, and having had my time for LR experimentation intermixed with a need for supper, I can’t say that I’ve done any more than just reference a few DNGs from my existing photo library. For what it’s worth, the performance seems good for a beta, and I am more than pleased to see that it is using more than one processor (it doesn’t drive both of them at 100% usage yet, but I presume Adobe will fix that before the final release). Of course, I have a few comments about improvements that I’d like to see in the beta, but writing to Adobe about those issues would be more useful than whining about them here. One thing is certain – returning to Bridge+ACR+Photoshop for real work is going to be very painful after testing LR, simply because the latter is already so close to entirely meeting my everyday postprocessing needs as an advanced amateur. I can’t wait for the final version to become available.

  14. m0nstermike Says:

    P4 3GHz, 1 GB RAM. I really tried to be impressed, especially because I still have a learning curve ahead of me, but I must admit to being underwhelmed. In certain ways, I was reminded of DXO’s clunky interface rather than the very direct interaction methods I’m used to from ACR. Only time will tell, of course… but I’m not making the immediate switch I expected after reading all the rave reviews.

  15. Bob Klein Says:

    Being a PC user, I am a big fan of Raw Shooter Premium for raw conversions. Since Adobe has just acquired its parent Pixmantec, I wonder when RSP’s technology will be intergrated into Lightroom. It’s certainly not in this version.

  16. Sean Naghib Says:


    I don’t know what the fuss is all about. Running on Centrino Duo with 1 GB of Ram it works fine. The only thing is need admin rights to run it. Double clicking on the icon and nothing happens run as admin and bingo.

    I am so busy trying it out that I no longer have time to check the forum so regularly :)

    Nice one.

  17. Jack Gilbert Says:

    First impressions, runs like a snail, not really impressed, wonder what all the hype is about. I do not blame my machine as C1 and CS2 run fine. as off this moment in time I will stick with them for my needs. Could not figure out how to put more than one keyword in for a picture, again exstensis is for me. Am i expecting to much

  18. Tom Brechet Says:

    It looks like LR is slow on AMD’s but fast on Intels. Can we confirm this here? Its certainly slow on my AMD with 2GB Ram on which RSP and CS2 run like a breeze.

  19. Bob Walters Says:

    >>It looks like LR is slow on AMD’s but fast on Intels. Can we confirm this here?

  20. Dave New Says:

    Maybe not only an AMD vs Intel issue, but it looks most certainly a sensitivity to network-mounted drives.

    I’ve encountered a lot of problems with network drives in recent Mac/Windows photo-centric applications, in particular programs like iView’s MediaPro. I tried to import a couple thousand images from a networked drive, and after letting it run all night with only a few hundred imported, I finally canceled the process. Doing the same from a local drive completed in a matter of minutes.

    I’ve also quit trying to do any intensive operations from within Bridge or PSCS2 on networked drives on Windows, for similar reasons.

    Is it something about the Windows SMB networking protocol that is broken, or is it that Mac programmers don’t know how to write networking code for Windows? Whatever it is, it is really aggravating. I have any number of Windows-only programs that run just fine on network mounts, thank you.

    Windows networking performance for Mac/Windows programs really needs some attention. We really aren’t just making this up. Dealing with this stuff is a far cry from the old days where Sun workstations (known as ‘gutless wonders’) mounted not only their home directories, but their swap drive over the network, for Pete’s sake. It may have been slower than local mounts, but those NFS mounts weren’t thousands of times slower, by any account.

  21. Alessandro Says:

    I know everyone is drooling over the Slider based curve adjustments, but I find that they are not as intuitive as Ctrl-Clicking to find the exact point on the curve and then adjust that way.

    The other thing that I miss is that you could add an anchor point, play with it, and if you didn’t like it, drag it right off of the curve and you would be back to the point where you started before making the adjustment.

    As for performance, that is fine when I tried it with the test library that you download with Lightroom.

  22. Designer Scott Says:

    Resouce Hog indeed!
    I use my 2ghz 1.5gb tabletpc as a workhorse with all of the other adobe programs, and use Digital Photo Pro for my canon shots because I can’t wait 10 seconds for every minor adjustment I make for a single RAW file.
    I have never had my computer lag that bad, and I use photoshop extensively. I sincerely hope that gets fixed!

  23. Martin Beebee Says:


    Just started playing around with Lightroom, and it seems to have a lot of potential for being a “go-to” application. But I’m surprised at how slow it is.

    I’m running a Dell with Windows XP SP2, P4 3GHz, 1GB RAM. Making a simple curve adjustment (moving the slider) takes 4 sec to process (RAW or DNG). Yikes! PS CS2 runs lightning-fast (with Nikon Capture and iTunes open), so it’s not my machine.

    Hopefully it will run faster in the “real” version? I can’t see buying LR in the future if it’s going to run this slow — any time savings in workflow will be swamped by processing time.

    (And hopefully it will read Photoshop files (all my master files are in PSD format, and thus inaccessible in LR)? Isn’t that a hoot?)

  24. jim van kennen Says:

    am unable to run LR on amd 1.39 ghz machine despite fresh install of xp and sp2. runs fine on older intel machine. any thoughts?

  25. Ronald Laine Says:


    The following are a few comments in connection with Lightroom:

    System: Dell- Windows XP-SP-Intel 3.4 GHZ- 1 GB RAM

    File Processing:

    JPEG to DNG – Batch runs consisting of 100 files per batch; From Canon 20D

    JPEG FILE SIZE-2.7 to 3.9 M
    DNG resulting file size- 8.2M

    Processing time is about 2 seconds per file.

    Exporting files as DNG to external hard drive utilizing USB 2 requires about 3 seconds per file.

    Adjustments in DEVELOP occur as fast as I make them.

    Questions I have concerning Light room;

    1-Why percentage for R G B instead of numeric values?

    2- In PRINT-PRINT JOB SETTINGS-Color Management-Profile-Other, I am presented with only the options showing printers configured on my PC. I do not find any ICC profiles. Is this a function of BETA 3?

    I currently have on my PC in part the following:

    Adobe CS2
    Canon DPP
    Breeze Browser Pro
    Capture One (Trial Version)
    Bibble 4.8 (Trial Version)
    DXO Optics Pro 3.5 (Trial Version)
    RSP (Trial Version)

Leave a Reply

You must be logged in to post a comment.