January
February
March
April
May
And May is the month that our daughters’ ballet studio has their big recital
June
July
August
September
October
November
December
January
February
March
April
May
And May is the month that our daughters’ ballet studio has their big recital
June
July
August
September
October
November
December
The folks at O’Reilly sent me a copy of Mikkel Aaland’s Photoshop Lightroom 2 Adventure. You would think that a book about Lightroom wouldn’t really be necessary, but it turns out to be useful, especially since software doesn’t come with manuals anymore. The number of Lightroom books is also probably a gauge of the demand. In any case, I was interested in the first version of this book, Photoshop Lightroom Adventure because of Aaland’s columns on O’Reilly’s Inside Lightroom blog, and because of an interview that I heard on one of George Jardine’s Lightroom podcasts.
The book is a guide to Lightroom, and is populated with pictures and stories from an adventure trip that Aaland and a number of other distinguished photographers took to Tasmania. In the first edition, they took a trip to Iceland, which has now given me the bug to take a photo trip there someday. I found the book to be very helpful. I learned a bunch of shortcuts which I didn’t previously know, and I got to see examples of how to do the same tasks that I do, but using a different mechanism (a lot of this involved direct manipulation of the histogram in the Develop module).
The chapters on the Develop module are the strongest point of the book, partially because this is the strongest part of Lightroom. There is good introductory material, but there is also good stuff for advanced users, like how to hack the textual representation of develop presets. I added several presets to my repertoire by using this trick. My favorite of the Develop chapters was the one about the recipes from the various photographers on the Adventure. I always find it instructive to see how someone has done the post processing on a particular image. Know how much (or little) someone has done helps when you look at the finished picture, and gives you an idea of how far you’ll be able to take your own images straight out of the camera.
If you’re interested in getting more out of Lightroom, I’d have no problems recommending Photoshop Lightroom 2 Adventure.
Much is being made of Apple’s decision to leave the Macworld show. You can look at this from several angles:
New Product Announcements
From Apple’s point of view, leaving Macworld is a major win. This unbinds them from the need to pull out all the stops in order to have new products ready for an arbitrary deadline. It also will improve Apple’s holiday sales. No person knowledgeable about Apple would buy anything (unless it was freshly announced) in the 2-3 months before Macworld. You’d be nuts to. Now consumers won’t be able to count on an event to in order to help guide their buying decisions.
My guess is that it has become harder and harder to for Apple to time their announcements for the show. On the computer side, the Macintosh hardware cycle is now irrevocably linked to Intel’s hardware roadmap. Intel has their own schedule about when they ship products, and it overlaps badly with Macworld. Take the Nehalem release as an example. If Apple stays true to form and uses server Nehalem’s in the Mac Pro and laptop Nehalems in the iMac, then there is no reason to believe that there will be significant (non clock speed bump) release of either the Mac Pro or the iMac this January. As far as Intel has said, the Nehalem launch dates simply won’t allow it. On the other hand, Intel is reasonably good about telegraphing the direction of their hardware, so you might be able use these dates as a guide for new computer product launches.
As an individual purchaser of Apple products, I’m not excited about this, because it increases the risk that I’m going to buy something and then be unhappily surprised. But as an Apple stockholder, I think that this will actually be a better move for Apple’s business in the long run.
The Macintosh community
Some people are lamenting the end of the Macworld show (not a forgone conclusion) as a blow to the Macintosh community. I’m not sure that I agree with this. Macworld doesn’t have to die just because Apple is pulling out, and even if Macworld did die, then maybe there would be another event to spring up in it’s place. For me personally, I’m getting more than my fill of Macintosh news, commentary, and other interaction via the Internet. Back when I lived in Boston, I used to attend Macworld, but my attendance was mostly walking the exhibit floor, occasionally talking to a vendor, and then taking off. I actually have much better relationships with Mac developers now. All I have to do is drop them e-mail. Personally, I think it’s pretty clear that there’s something wrong with the traditional trade show / conference model — and I don’t just mean Macworld, here. I’d like to see something different emerge, and I hope that the problems with the economy will force that different thing into existence.
Apple’s succession plan / Steve Jobs is sick
This is perhaps the most troubling angle. People (rightly or wrongly) attribute a large amount of Apple’s success to Steve Jobs. I’ve personally experienced the Steve Jobs effect – he returned to Apple when I was working there. Many of us also remember the train of ineffective CEO’s that preceded Steve’s return. Could Apple continue on its path of success if Jobs were to leave the company? With the right leadership, it could, but it is hard to know if the rest of the team is up to the job. I hope they are.
A while back I finished another Photoshop book, Vincent Versace’s Welcome to Oz: A Cinematic Approach to Digital Still Photography with Photoshop.
This is an advanced Photoshop book, because I consider any book that spends two chapters on how to combine several images (not via HDR) to obtain a single image to be advanced. The first chapter alone was worth it for me. Versace talks about how to control how the viewer’s eye moves around in a photograph and then shows how one might take a photograph and process it so that the viewer would take in the photograph in the desired manner. He introduces the technique of creating image maps which are then used to guide the various post processing steps.
In addition to white and black points, curves, layer blending modes and gaussian blurs, this is the first book that I’ve read that discussed the use of Photoshop’s Lighting Effects filter. Being a lighting guy, I’m not sure how I feel about that, but it was interesting to observe the rationale and effects of this particular filter. I’m not sure that I will ever use Versace’s technique of harvesting several images to obtain a single image, but it was interesting to see the thought process, which might be of use when composing pictures in the viewfinder and assessing the goodness or badness of a shot.
I have yet to actually try Versace’s method on a photograph, but there are many stunning photographs in the book. I’m looking forward to things slowing down enough for me to actually sit down and try my hand at some of the more basic techniques that he described.
CommunityOne is not as well known as its older brother, JavaOne. 2008 was the first year that I got to go. The event is going to be a bit bigger in 2009 — in fact, the event will be held both on the west coast and on the east coast. The conference is focused on “open source innovation and implementation”, and this year the conference planners are looking for talks on “cloud computing and virtualization, dynamic languages and scripting (PHP, Ajax, Python, Ruby, JavaScript), databases (MySQL, postgreSQL), web and application servers (GlassFish, Apache), operating systems (OpenSolaris, Linux), mobile development (Java ME, Android, Symbian), and tools (NetBeans, Eclipse, Sun Studio)”.
Here are the details:
CommunityOne East – March 18-19, 2009 – New York City
CommunityOne West – June 1-2, 2009 – San Francisco
Deadline to submit speaking abstracts: Dec. 11, 2008
For more information on these events: <http://developers.sun.com/events/communityone/>
If you are interested in submitting a talk: <http://www.eventreg.com/sun/communityone09/cfp>
I have usernames on most of the major lifestreaming services (Twitter, FriendFeed, identi.ca, and so on). For a variety of reasons, I really only use Twitter, and the only way that Twitter is useful / manageable for me is the existence of rich client side applications.
Mac OS X
For some time, I’ve been using Craig Hockenberry’s excellent Twitterific. I liked the UI, and the feature set was good. From time to time, I would try the Adobe AIR based twhirl, which had the virtue of also being a FriendFeed and identi.ca client. Unfortunately, I could never keep twhirl because of a bug in AIR 1.1 that caused clicked URLs to open in a new Firefox window instead of a new tab. That bug was fixed in this weeks AIR 1.5 release, so I gave twhirl another try earlier this week. I liked having FriendFeed and identi.ca up (having identi.ca up meant that I saw Allison Randall’s messages about the Parrot Developer summit and their new release schedule). I didn’t like having a window for each service — I don’t care about keeping it separate, and I’m still having some trouble finding a theme that works for my aging eyes. Twhirl also doesn’t seem to remember window positions between runs, which makes the multiple windows even more of a pain. I also miss seeing people’s “real names” and the Growl notifications that I was getting from Twitterific. I put twhirl back on the shelf, but will probably come back to it again.
A week or two ago, I discovered Syrinx, which is a Twitter only client. There were a few things that persuaded me to try it out. The ability to set a bookmark at some point in the message stream and then go back to it. This seems to work better for my style of reading than individual read/unread markers on each Tweet. The keyboard shortcut means that I can jump right to where I left off, which is nice. Syrinx also lets you search the stream, which is useful. I follow enough people that searching is useful. I was also (incorrectly) under the impression that Syrinx would save a slice of the message stream locally, which would be a nicety. I can page backwards on the Twitter site, but that way lies pain. Syrinx has a way of tracking twitter “conversations” and finding the supposedly relevant tweets and presenting them. I like this idea, I just wish it wouldn’t take over the main message stream window in order to show it. The biggest problem with Syrinx is that there something awfully bloated in there, which means that after some time, the app is eating memory and slowing down. Which means you have to restart it, which means you have to catch up first. MRR, the author of Syrinx, knows that this is a problem and is working on a solution. I hope that won’t take a long time.
Because of the AIR 1.5 release I also tried TweetDeck this week. I tried it, and there were some interesting features. I liked the ability to make my own groups of people – but Twitter should be supporting that. I also liked the way that replies and direct messages could be in their own column – I really liked that, actually. I liked the idea of TwitScoop, but what I’d really like would be a TwitScoop of my Twitter network – that would be cool. TweetDeck was great when I put it on my 30″ main display. You can see lots of stuff and quickly see if there is anything useful. Unfortunately, I’m not willing to dedicate that much screen real estate — whatever client I use has to live (and share) on the “outboard” main LCD of the MacBook Pro.
iPhone
When I got my iPhone, I started using Twinkle. There pretty much wasn’t anything else, and I sort of liked the idea of having some kind of location awareness of people using the service. Turns out that very few people that I know use the Twinkle location stuff, and I’ve pretty much switched to using Brightkite for that kind of thing, and even there, the jury is out. User interface wise, I like the fact that it colors replies and direct messages differently — it makes them much easier to pick out. I don’t like that I have to tap on a tweet containing a link in order to open the link.
I’ve since switched to using the iPhone version of Twitterific. I don’t have to tap on tweets to follow links, and Twitterific is pretty good about storing a decent number of tweets on the phone. I can usually take a 2 hour plane flight and not have missed much when I land on the other side. I’d love to not miss anything at all. One annoyance is that Twitterific for iPhone doesn’t remember the last tweet that I was looking at very well, so I end up doing a lot more scrolling than I should have to.
Wish List
Here’s a consolidation of the some of the things that I think are important in rich clients for Twitter and services like it.
On the mobile side, there is one feature that I would consider killer.
I want a “direct message” rolodex. There are people who I want to direct message on a frequent basis. I don’t remember everybody’s twitter user name – that’s what computers are for. I want a “picker” that contains a “speed direct message” list. That would be awesome.
This is one space where rich/desktop applications are by no means dead.
It’s been a while since I reported on the state of my Macintosh. Here are a few apps that I’ve been using a lot recently.
Evernote
I’ve had Evernote installed for quite some time, but I didn’t really start using it until after I got my iPhone. So I was interested to read Ars Technica’s report that 57% of Evernote’s users are using the iPhone client. Evernote is a great example of the “rich application architecture of the future”. Evernote’s family of applications include desktop clients for Mac OS X and Windows, a web applications, and mobile clients, most notably the iPhone. All of these pieces work together to make a great integrated solution. This is the kind of ecosystem that we were building around Chandler, although we never got to the mobile part, and as the Evernote data suggests, we would have been fine just creating an iPhone client. Of course, hindsight is 20/20.
Apple helped Evernote tremendously by providing a barely functional notes application on the iPhone, and then providing no way to sync notes back to a Mac. So the iPhone Evernote client fills a great hole in the iPhone application suite. That got me started using Evernote for information that might need to move back and forth between desktop and device. The next step up for me was that I started using Evernote to take notes for conferences. I used to use Ecto for that, and I would then rewrite my notes into a blog post. But I missed having the raw notes, so I decided that instead of creating a billion drafts in Ecto to hold the raw notes, I would just take all the notes in Evernote, and then write the posts in Ecto. This of course had the added benefit of me being able to use other features of Evernote. I definitely think that the Evernote team is doing something that desktop and mobile software developers ought to be paying attention to.
1Passwd
Another good example of this desktop/web/mobile trend is the fantastic 1Passwd password manager for Mac OS X and iPhone. I got 1Passwd as part of a MacUpdate software bundle some time back. It took me quite some time to start using it, because I was happily using Firefox’s built in password manager. 1Passwd has the advantage of working with Firefox, Safari, and NetNewsWire on my desktop. It does a much better job of dealing with odd web site logins. It does a great job of managing my ridiculous number of passwords. Actually it has a great password generator built in, which makes it easy to stop the common practice of having a few relatively easy to remember passwords that you use everywhere. Which is just plain bad security. 1Passwd also has an iPhone version, which means that accessing sites from my iPhone is no problem at all either. Great piece of software.
PathFinder
The last piece of software is PathFinder, which is PODS (plain old desktop software). PathFinder is a great replacement for the Finder, and the latest version, 5.0, adds a dual plan feature that makes file management tasks much easier. You can also manage sets of tabs. I use this feature to manage projects, by creating a set of tabs for each project. I can then flip a PathFinder pane into exactly the configuration that I want for working on that project. It’s a shame that Apple has been so lackadasical about improving the Finder. Maybe this will improve with the rewrite of the Finder for Snow Leopard. In the meantime, PathFinder is a good solution for those of us that need a little more than what the Finder provides.
Congratulations to the Apache CouchDB project, which has graduated from the Apache Incubator and become a top level project of the Apache Software Foundation.
Along with today’s launch of NetBeans 6.5, Sun, in cooperation with the NBPython community, are releasing an early access version of Python support for NetBeans. This is a result of the collaboration between Sun people and the NBPython project that I wrote about back in July. This release has been tested by folks in the NetBeans community and some folks from Sun’s NetBeans QA team, and it’s in pretty good shape for an early access release. We’re interested in getting people’s feedback. We would also love to see more people get involved with NBPython.
How to get it?
You can get NetBeans Python from the NetBeans download page.
What’s in it?
The basic feature set for the early access release consists of an editor for Python, the ability to execute Python programs (using CPython or Jython), and a debugger.
There’s a tutorial up on the NetBeans wiki.
Tor Norbye, who did most of the work on the editor, has written a series of blog posts detailing various features of the Python editor.
Who did it
Allan Davis – project and platform management, interactive console.
Jean-Yves Mengant – Jean-Yves is the author of the jpydbg debugger, which he’s merged into NBPython.
Amit Saha – documentation and help sets – Amit works for Sun, but he’s doing Python on his own time.
Tor Norbye (Sun) – editing.
Tomas Zezula (Sun) – project and platform management.
Ted Leung (me) (Sun) – various behind the scenes stuff.
Frank Wierzbicki (Sun) – NBPython is using Jython’s parser and Frank worked with Tor to add support for positions and better error reporting.
Peter Lam (Sun) – Sun QA
Tony Beckham (Sun) – Sun QA
The NetBeans CAT community as well as those folks who drove by and reported bugs.
How to get involved
NBPython has become a full fledged NetBeans project, so the main project page is now on NetBeans.org, as are the issue tracker and mailing lists:
nbpython-dev@netbeans.org
nbpython-issues@netbeans.org
nbpython-commits@netbeans.org
nbpython@netbeans.org
I’ve been dithering back and forth about writing this, but Duncan’s recent posts about his new D700, as well as several camera discussions that I had at ApacheCon have pushed me over the edge.
Back in April I bought a new camera. When I got my first digital SLR back in 2005, I was just getting (back) into photography, and I had no idea if was going to really take to it or whether I would be any good. As a result, I went for the best cheapest camera that you could get at the time, which was Canon’s Digital Rebel XT. That camera served me well, but thanks to the digital format, I’ve been getting better at a pretty decent rate, and I was starting to run into areas where the camera was interfering with my ability to get the shots that I wanted. I knew that a new camera was not going to bump my work up a huge amount, but I was starting to get frustrated with it. It also wasn’t a smart idea for me to play with a Nikon D300 at one of the Seattle Flickr Meetups.
If I was going to upgrade cameras, I was also probably going to go full frame, because I like very shallow depth of field shots, and the possibilities for thin depth of field are better on full frame. This presented a problem. I only had one really good lens in my Canon set, the 17-55mm EF-S lens. The Canon EF-S lenses are unusable on the Canon full frame cameras, which basically meant that I would have to start over in terms of good lenses. Since I was going to have to start over, it only made sense to look at all the cameras in the marketplace.
When I did that, I was really impressed with the ergonomics of the Nikon cameras, so I started really looking at them much more seriously. Nikon has been been very aggressive about improving their cameras. This is in contrast to Canon, which had not dramatically improved the 20D/30D/40D series, had yet to announce the 5DMk2 and which has had very public problems with the top of the line 1DMk3. Back in April, there was only a single full frame Nikon camera, the D3. So after a bunch of deep breaths, that’s what I decided to buy.
Likes
So far, I am really happy with the camera. It is sensitive to light in a way that goes even beyond what my eyes normally see (unless I am really careful). As an example, at a recent Flickr get together, I took a shot of some chairs up against a red wall. When I looked at the picture on the back of the camera, there was a definite gradient in the lighting, but neither I nor several people that I asked saw the gradient without the benefit of the D3 picture.
When I was in Prague back in July, I was able to take a number of night shots completely hand held. Ordinarily, I would have had to use a tripod for many of these, but these shots are more than passable for handheld.
As far as image quality goes, I am very happy. I am quite satisfied with the sharpness and color rendition of D3 images. The Nikon white balance does a pretty good job, better than the XT’s auto white balance, but of course, that’s not a very fair comparison at all. The biggest thing that I’ve run into is that the exposure really needs to be spot on, because the camera is so sensitive to light, that it is easy to blow out highlights. High ISO performance is really good, and when the noise starts to creep in, it looks much less objectionable than the noise that I’m used to on the Canon sensors. I shoot entirely in RAW, and I’ve brought back both badly over and underexposed shots in postproduction (I’m pushing myself to shoot fully manual as much as possible, and sometimes I forget to adjust). One drawback is that the 12MP RAW files take up around 12-13MB. The D3 eats CF cards very quickly, and I rarely shoot in one of the burst modes. This translates into demands for more hard disk space and bandwidth, and ultimately ends up pushing the computer harder, as Lightroom and Photoshop have to work harder to get all that data into memory and then do all the image processing operations. A Mac Pro is definitely in my future for these reasons, and I don’t even want to think about what this means for people shooting the Canon 5dMk2, 1DsMK3, or the Sony A900, at 20+MP resolutions.
The build quality is fantastic. Everything is solid and well crafted. Even though my hands probably on the smaller side, I find that the camera fits my hands well, and that the camera is well balanced, even with a 70-200 zoom lens mounted on the front. My hands fall naturally on the command dials and the autofocus point selector, whether I am using the main controls or the vertical controls on the grip. All the build quality means extra weight, which is taking a little getting used to, but it is good exercise.
It’s taken me a little while to get used to all the controls, but I much prefer Nikon’s system of using buttons in combination with dials as opposed to forcing me to take the camera from my eye in order to change things in a menu. I’m finding that I’m very quick to make adjustments, with one exception. I still haven’t quite gotten the hang of switching metering modes without taking the camera down from my eye. The control for this is up on the prism housing, and requires a decent amount of force to switch. In some low light situations, I tend to switch back and forth between evaluative (matrix) and spot metering modes, so this is an inconvenience. The alternative is for me to spend more time shooting in manual mode and learning to compensate for how the meter behaves, which is probably a good skill to be developing anyhow.
The autofocus system has performed really well. I’ve been able to accurately track fast moving action, and even in fully automatic mode, the camera finds the correct focus point a high percentage of the time. For portrait work, I still switch to a mode where I can select the focus point, because I just want the extra level of control. The only thing that I have noticed is that under some very low light situations, the camera can take a little while to lock. It’s still not entirely predictable to me when this is likely to happen. I love the huge viewfinder on the D3. I frequently had shots where I framed carefully in the camera, only to have extra stuff creep into the picture due to incomplete coverage in the viewfinder. I like this more than I expected to.
It seems to be conventional wisdom that Nikon’s TTL flash system is better than Canon’s, and based on my experience I’d have to agree. For the most part, I am an off camera lighting guy, but there are some situations, like parties and wedding receptions, where you just don’t have the time to make the adjustments for manual lighting. So far, I’ve found that the iTTL system works better than the Canon system. The D3’s high ISO performance adds to this by allowing you to shoot bounce flash pictures in rooms with much higher ceilings than previously possible.
There are lots of smaller things to like. The battery for the D3 lasts forever. I shot three ballet performances in one weekend, using a big image stabilized zoom in continuous focus mode, on a single battery charge. There was plenty of charge remaining. The other thing that I like is the dual Compact Flash card slots. I like the flexibility of using two smaller cards and overflowing from one slot to another. It means less worrying about managing cards in high volume shooting situations.
Dislikes
There’s one major thing that I have found that I dislike. On Canon’s you can switch between Aperture Priority and Manual modes, and have two different aperture settings. This makes it easy to have a set of manuals setting for strobes, and then flip to Aperture Priority for natural light. On the Nikon, whatever Aperture you set, will be the same for both modes. So if you are at f/8, 1/250th in Manual, but need to shoot at f/2.8 in Aperture Priority, when you switch from Manual to Aperture Priority, you’ll need to also switch the Aperture to f/2.8. And when you go back to manual, you need to go back to f/8. I can understand why it’s designed this way, but for the way that I use the camera, it’s something that I miss from the Canon.
Another dislike (well, I don’t mind it that much) is that the shutter snap on the D3 is pretty loud. Back in May I spent a day shooting with some wedding photographers. Almost all of them were shooting Canon 5D’s, and a few people exclaimed over how loud the shutter was. I guess that Kevlar shutter is going to last.
The D3/D700 start at ISO200. You can get down to an ISO 100 equivalent, but its an extension. If you are outside trying to knock down the Sun with strobes, ISO200 is one stop higher than you want to be. This is one area where the 5D/5Dmk2 have a nice advantage — you can get down to ISO50, 2 stops better. I guess you can always bring more watt/seconds, but it’s kind of a pain. Or you could use something like RadioPoppers to get your sync speed up several stops.
It’s annoying that Nikon didn’t put the dust shaker from the D700 into the D3. I’ve learned to clean the sensor myself, but it is annoying. On the other hand, even people with dust shakers need to have their cameras cleaned periodically, so maybe it’s just not that big a deal.
Some shots
This is an awesome camera – so if you see bad shots from me, you know it can’t possibly be the equipment.