...is exactly what I've been looking for to replace BreezeBrowser Pro and do all the front-end file management stuff before I even start into Adobe Lightroom.
I'm able to sit on one (or two, although not both at once) of my new Win 7 boxes and look at Canon RAW files that are on my file server, over my network.
I can move, delete, and re-name files at will.
And all much, much faster than I'd been able to do it on the file server box itself, which is running Ubuntu 10.10 and where I have to use gthumb to view files in the Canon RAW format via dcraw.
Totally cool!
Showing posts with label adobe. Show all posts
Showing posts with label adobe. Show all posts
Thursday, January 6, 2011
Monday, December 27, 2010
OK: Adobe Lightroom...
...is simply an extraordinary piece of software on any number of levels: possibly more so than any other software I've purchased in a long time.
(Disclaimer: a lot of that hyperbole is due to the fact that I've been running Open Source/Free as in Beer software -- currently Ubuntu Linux -- for a good ten years and I simply don't buy a lot of software. But, whatever...)
Two core issues have presented themselves in the last several months.
1) I've been shooting an overwhelming number of photos at any given event -- on the order of several thousand for a Saturday's pair of Vashon Island Soccer matches, for example.
2) I had one of my two years-old mainline photo processing computers (Intel P4, 2 GB ram -- actually it was the root hard drive, a 250 GB Seagate, that fried) die as a direct result of the wind storm/power outages we had in late November.
So it became clear that something was trying to tell me it was past time to bite the bullet, get out the credit cards, purchase some contemporary computer hardware and finally make the move to Adobe Lightroom, with Photoshop CS5 available in the background for the really heavy lifting.
Long story short: I now have two Intel Core I5's, each with 8 GB ram and middling-good gaming level NVidia video running Windows 7 Professional 64 bit.
And Adobe Lightroom 3, and Adobe Photoshop CS5 on each.
Lightroom is amazing.
Fundamentally it's a DBMS: a database management system.
The focus (hahaha) is on cataloging photos. Lots of photos.
I've just gotten started using Lightroom and so far I've got over 4,500 photos pulled into the generic Catalog "All Photos" for the two instances I'm running.
These are keyworded as they're pulled in off a file server box out on my home network, and can then be grouped and categorized by keywords, meta-data, date shot, time shot, camera body shot with, lens shot with, ISO used, f-stop used, etc etc etc...
Once categorized photos can be pulled into a Collection -- which in my case is a single event -- at which point I can start to actually "develop" the individual photos in (wait for it) the Develop module.
Except that entire groups of photos (or an entire Collection, if needed) can be "developed" using the same settings such that often the only photo-by-photo adjustments I find myself doing are to rotate slightly, and crop.
When happy, I export to whatever the specific end-use is: jpegs 600 pixels wide to go up on FinchHaven.com, for example.
Except that all of this done non-destructively, such that all the original Canon RAW images back on the file server are untouched.
All Lightroom is doing, really, is recording an (apparently) unlimited list of state-changes (white balance, exposure compensation, hue, saturation, luminance, rotation, cropping) without doing anything to the original images until they're exported.
Only then does some actual new image come into existence.
And all the work done to get to that end point is recorded step-by-step and is completely reversable, such that creating an image for my web site, or outputting an image to the printer for a reprint as part of an order are completely decoupled one from the other, and yet the labor put into sort of one end point is both permanently retained, and yet completely segregated.
Hard to get your head around the idea until you've done a few things with Lightroom, but extremely powerful.
More later...
(Disclaimer: a lot of that hyperbole is due to the fact that I've been running Open Source/Free as in Beer software -- currently Ubuntu Linux -- for a good ten years and I simply don't buy a lot of software. But, whatever...)
Two core issues have presented themselves in the last several months.
1) I've been shooting an overwhelming number of photos at any given event -- on the order of several thousand for a Saturday's pair of Vashon Island Soccer matches, for example.
2) I had one of my two years-old mainline photo processing computers (Intel P4, 2 GB ram -- actually it was the root hard drive, a 250 GB Seagate, that fried) die as a direct result of the wind storm/power outages we had in late November.
So it became clear that something was trying to tell me it was past time to bite the bullet, get out the credit cards, purchase some contemporary computer hardware and finally make the move to Adobe Lightroom, with Photoshop CS5 available in the background for the really heavy lifting.
Long story short: I now have two Intel Core I5's, each with 8 GB ram and middling-good gaming level NVidia video running Windows 7 Professional 64 bit.
And Adobe Lightroom 3, and Adobe Photoshop CS5 on each.
Lightroom is amazing.
Fundamentally it's a DBMS: a database management system.
The focus (hahaha) is on cataloging photos. Lots of photos.
I've just gotten started using Lightroom and so far I've got over 4,500 photos pulled into the generic Catalog "All Photos" for the two instances I'm running.
These are keyworded as they're pulled in off a file server box out on my home network, and can then be grouped and categorized by keywords, meta-data, date shot, time shot, camera body shot with, lens shot with, ISO used, f-stop used, etc etc etc...
Once categorized photos can be pulled into a Collection -- which in my case is a single event -- at which point I can start to actually "develop" the individual photos in (wait for it) the Develop module.
Except that entire groups of photos (or an entire Collection, if needed) can be "developed" using the same settings such that often the only photo-by-photo adjustments I find myself doing are to rotate slightly, and crop.
When happy, I export to whatever the specific end-use is: jpegs 600 pixels wide to go up on FinchHaven.com, for example.
Except that all of this done non-destructively, such that all the original Canon RAW images back on the file server are untouched.
All Lightroom is doing, really, is recording an (apparently) unlimited list of state-changes (white balance, exposure compensation, hue, saturation, luminance, rotation, cropping) without doing anything to the original images until they're exported.
Only then does some actual new image come into existence.
And all the work done to get to that end point is recorded step-by-step and is completely reversable, such that creating an image for my web site, or outputting an image to the printer for a reprint as part of an order are completely decoupled one from the other, and yet the labor put into sort of one end point is both permanently retained, and yet completely segregated.
Hard to get your head around the idea until you've done a few things with Lightroom, but extremely powerful.
More later...
Subscribe to:
Posts (Atom)