Lightroom made a believer out of me. There are a couple factors in its favor that don’t entirely have to do with its feature set, one is the $99 educational buy I qualify for as a homeschooler, the other is it’s performance on less-than-bleeding-edge hardware. For right now my MDD 1.25 dually has to do the job, and Lightroom officially runs on it and can get the job done. Beyond that the loupe is the only thing from Aperture that I’m jealous of, but at least the RGB values are displayed and dynamically follow the cursor in Lightroom. The main selling point beyond that is that it seems to be a more transparent and less demanding front-end to Photoshop, it’s just easier to relegate it to being a “pro” RAW converter to replace the Camera RAW plug-in, and skip all the library features. “Fill light” rules! (UPDATE 3/18/10) I take back my narrow-minded view of the product and will say that I use the library features as much as the rest of it.
Archive for the ‘Software’ Category
Adobe Lightroom It Is
Monday, August 18th, 2008Thoughts on Aperture vs. Lightroom
Thursday, July 10th, 2008I haven’t spent a ton of time with these applications, but after some productive use of them thought I’d offer these observations; both seem way too bloated and clumsy, really what I think would get the job done is just a more robust RAW import tool for Photoshop, designed to be just that – the front door to Photoshop. Being able to browse a group of photos that may have something in common i.e. hard-to-get white balance shot in fluorescent lighting or some other odd environment, where you want to be able to copy the settings from one and rapidly apply to all the others en masse is nice, but I don’t need [yet] another black hole to store my photos or even a database of previews of my photos in, I just need a robust RAW access point for Photoshop. But I think Lightroom wins here as far as easily dropping in images from a shoot, processing them and then just deleting them (source files included if you wish.) That’s close to a transparent front end for Photoshop.
As far as GUIs and such, Lightroom feels more like Elements than Photoshop – the interface kind of has that dumbed-down feel, too much navigation garb that gets in the way. But I’ll give it this; it will install and run on my [ancient] Mirrored-drive door G4, and with patience gets the job done whereas Aperture has to be hacked to even install and then performance is decidedly not.
Here is an image processed first with just Camera RAW in Photoshop CS, and lots of fiddling with layers and screening and such to lighten up the grass and trees in the foreground, 10 minutes worth at least (well, okay, 5 minutes.) Now compare that to about 1 minute in Lightroom and only a noise filter pass (Noise Ninja) in Photoshop.

Photoshop Camera RAW

Lightroom
Speaker Building Tool For OS X
Thursday, July 3rd, 2008I’ve never been so excited about Windows. The de-facto standard free speaker building (mainly woofer/subwoofer cabinet calculator) application, WinISD is only available for Windows. There is a free online version, but now with an Intel based Mac you can run WinISD on a MacTel for free using Darwine. This screen shot is a bit “Beauty and the Beast” as far as GUI’s, but it works!
Free Photo EXIF Tools
Thursday, April 10th, 2008This app came in handy to address the dreaded 010101 file date issue that you get from dead batteries :~)
Digital Photography & Workflow Thoughts – Part 4
Wednesday, April 9th, 2008I was reminded on one of my own rules to live by when it comes to principles of use of a digital camera when I put my Olympus C730UZ into the hands of my 9 year old, so while it was fresh in my mind I figured I’d relay some observations and opinions about some points to ponder.
1. Spend plenty on large denominations of storage media whether CF, SD, MS or xD. Read on for the reasons. A corollary to that is buy plenty of rechargeable batteries. If your camera uses a proprietary battery buy at least a second one and keep it charged/rotated.
2. Always shoot in the highest quality/resolution JPEG possible (native resolution, not interpolated as some cameras have, that’s a farce), or RAW if you have a DSLR and will be using an advanced workflow that handles RAW well (Aperture, Lightroom, Photoshop, or asset management.)
Because… You never know how timeless, unique or otherwise valuable the images that you (or your family) capture may be. You can always throw them away after the shoot if you determine otherwise, which is a parallel to point #3. If the only purpose for your images will be 4X6 prints, maybe you can ignore that point… Maybe.
3. SHOOT! When in doubt, shoot! The only real soft expense involved in shooting more than less is the potential time it may take to wade through the images after the shoot. The main hardware expense involved in this philosophy is a one-time investment in larger media than you maybe would buy if you were far more conservative (…and hard drive space.) For just around the house use, not factoring in trips or remote events, you can probably do fine on 256MB. But the second you walk out that door, the thing you have to realize is, you can’t go to the corner gas station and buy a roll of “film” (but you can go to WalMart and buy more media
, so you have to plan ahead and make sure you’ll have enough media to capture the event or trip. Which leads to point #4.

4. Keep your media cleared off. Don’t leave images on your card for months or even weeks. This does 2 things; helps you properly file or tag your images when you import them because the event is only a few days or a week old and you’re less likely to look at an image and have no clue what it is. The other thing it does is help you get the most mileage possible out of the media you do own because you will most likely have all the space available when you go to that event.
5. Backup your images on CD and some other form of live media i.e. a secondary and/or dedicated hard drive (besides wherever you have your primary library stored) or website or something, CDs are not reliable as the sole backup of your life images – do not trust them. They may make a fair off-site backup, which is another strategy to seriously consider – storing at least CDs of your library at a family members house. With the cost of media, it’s very affordable to (and inexcusable to not:) have off-site backups, which means unless your entire town is struck by a natural disaster, you should have something to fall back on if a major catastrophe befalls your dwelling.
6. Keep the time and date set correctly on your camera. Metadata is only good if it’s accurate. When is as important to me as what and where. If you are using rechargeable AA’s this is a real factor to stay on top of. If I don’t use my C730UZ within 7-10 days, those NiMH batts are prone to running dead on me and then my clock is reset and I’ve added another 50 images with the date of 01/01/00 and time of 12:00 am.
Aperture 2 On a MDD G4
Saturday, March 29th, 2008Thanks to these hacks I’m test driving Aperture 2 on a MDD G4 (2 X 1.25GHz.) It took it nearly 24 hours to pull in my 60,000+ library, and another 12 hrs or so to build previews for them all. The MDD isn’t officially supported nor will A2 install (without help) onto it. I have to assume that the only thing the PowerBook that is supported has over it is built-in USB2 and higher end video, all of which cal easily be added. I’ve spent minimal time working with the tools but I could see where this CPU upgrade and this video upgrade would make it usable for average use by the hobbyist. Yes, for about that amount I could buy a 1.83GHz Mini. But, I have a ton of stuff in my MDD, and the storage options are more robust on the MDD. To make a fair comparison one would have to compare the upgrade package to at least the iMac to get in the same league, now you’re talking almost twice the money. I think a maxed out MDD would be a good legacy machine to keep for a link back to the world of OS9 and such.
Audio Batch Processing With Amadeus Pro
Thursday, March 20th, 2008I was on the warpath today for batch processing options, as I have been many times before. Amadeus Pro ($40) is not an app that I remember getting a hit on before when doing these searches, but I hit it today. I already had Amadeus Pro in my toolbelt, thanks to Geoff Hankerson, so I thought I’d check out these features (honestly since I have Peak I just didn’t do much exploring to start with.) As I mentioned in this post, I have a workflow I follow to generate the two different quality Mp3 files for my churches sermon downloads. I’ve been looking for a way to cut Peak out of the picture, just for the sake of doing it. Today I think I hit on another option, all things being equal. I discovered the batch processing options in Amadeus Pro. Here are some screen shots of the setup I used, the -a arg in the LAME window forces mono (even though my source files are mono I had to do this to get Amadeus to recognize and output as such, there is no option in the main encoder section for number of channels.) This also means that the bitrate selection appears to be of the output file, after channel conversion, whereas in my example with iTunes, all bitrates are stated as stereo, you just do the math to pick the one for the desired mono bitrate. Translation; I wanted 24k mono, so rather than setting it to 48k (and divide by 2) like I would in iTunes, I set it to 24k.

Encoding options showing the LAME command line args.

Adding an AudioUnits plugin to the action list, my parametric EQ setup as a high pass.

The parameters in the Parametric EQ.
There are a ton of things you can do in batch mode. After I researched the command line args for LAME I added the -a for mono conversion so I didn’t have to do it as a stereo to mono conversion though you can do that as an action item too. I also experimented with normalizing, there are a couple options there including RMS normalize and fixed percentage (or dB) normalize. You can retain the input file format, however if you want to change the bitrate of a source MP3 file, you have to specify MP3 as the output format and set your encoder options there as shown. There are more expensive options ($70) as well for the hardcore production user, unfortunately the demo does not allow batch processing so I couldn’t “let the machines speak” for themselves. Comparing it to my Peak & iTunes workflow it took 1:22 to process my test file – open in Peak, apply Parametric EQ (as low cut), export as AIFF, re-encode with iTunes. Using Amadeus Pro it took 2:38 for the same source file and the same operations. This is on the same MDD 2 X 1.25GHz G4, 10.4.11, 1.75GB RAM machine. Based on sheer speed, Amadeus was not a runaway winner. But for a large group of files and a persons sanity (or schedule), Amadeus Pro is a viable option. Granted this is an extremely narrow test (I didn’t set out to do a review, just to find a better mousetrap), other functions may be faster, and if there were more gyrations to be done that had to be done serially in Peak I wonder if Amadeus wouldn’t show a gain there as well. Tests were done on the latest version 1.2.1. Bottom line; if you’re on a budget and need to do production-like processes with audio files, Amadeus Pro has a lot to offer, especially for the money.
Some additional how-to pages on Amadeus.
Of Audio Encoders and Bits
Thursday, March 20th, 2008LameBrain has been my MP3 encoder of choice. Today I discovered Max, yet another audio encoder, but more than that a batch converter and CD ripper. It’s free, like LameBrain, but has multiple encoders including Ogg, FLAC, WAV and many others. It allows you to queue up multiple encoding options for a group of files – which is great for production type workflows where you need multiple versions of a file, though I haven’t yet discovered a way to do multiple variants of the same encoder type i.e. two different bitrate MP3 files in the same batch (it overwrites the previous version with the last version.) It can do tagging, add the output files to your iTunes library, and embed album artwork. I found it via Google for batch encoding, and that it does, like LameBrain. I did a quick speed comparison, only one file, one format and came up with LameBrain in the lead with 29 seconds vs. 34 seconds for a 2:31 stereo AIFF to 192k high quality MP3 (on a MDD dual 1.25, 10.4.11, 1.75GB RAM.) And on the same machine encoding to AAC (m4a) iTunes 7.6.1 bested it by 2 seconds on the same source track, 17 secs vs. 15 secs but this was with Max set to highest quality for AAC where iTunes gives you no choices. In Max at lowest quality AAC 128k it managed it in 8 seconds, yet for some reason iTunes says the same for all three versions – “Low Complexity”, can somebody show me a way to do high complexity?! And it’s not all about speed, there are some nice batch processing features in here for the production-minded, for free!
Apple’s Aperture Comes of Age
Tuesday, February 12th, 2008I had written off Apple’s Aperture, long in favor of iView Media Pro, until now. Not that I’m going to shell out the $$$ anytime soon necessarily (at this point I’m just an arm-chair observer), but, I never considered it previously because it insisted on having it’s own library system, which meant that I would either have to give up the way I had my images stored/filed, or, I would burn up twice as much space to store them by virtue of the copy Aperture would make. Perhaps I’m a version behind on this too, but the announcement today brought it to my attention – along with the $100 price drop. Now we’re talkin’ Apple!
Working With MPEG2 (.MOD) Files
Sunday, February 10th, 2008So you’ve got one of those hard disk based camcorders and you want to do something with the .MOD files the thing generates. They’re MPEG2 files, and you have to say the magic word to do anything with them. This free app which is a wrapper for this MPEG2 codec will get you home, on the Mac. It will allow you to do all sorts of magic with MPEG files, not just MPEG2.

