Sunday, August 29th 2010

Scanning Negatives

On and off I’ve been thinking of getting a negative scanner for quite some time. The other week I finally made a decision and ordered a Reflecta Crystalscan 7200 from German Scandig.

I have already scanned a number of films and it is amazing to see how much detail their actually is in those old photos. I’m scanning at 3600 dpi, which means I end up with 17 megapixel images. Probably slightly overkill, but storage space is not an issue so I’m going with safe, not sorry. Obviously though the detail and smoothness is nowhere near what I get out of my 50D (or even my 30D).

Here is the first roll I scanned.

The big win is really just to have all the old photographs digitized, which makes them easy to share and keeps them safer for the future (provided you have a good back-up routine). And just seeing all the photos, one by one, brings back loads of great memories.

First I will be scanning my own and my wife’s photos. After those ~100 films, if I have the energy, I might keep going with my parents photos.

Sunday, August 22nd 2010

Move Tabs to Titlebar in Firefox 4

Edit: As of the 2010-08-26 nightly, this hack seems to have stopped working. I’ll let you know if I find a new solution. It should still work with beta 4 though.

Firefox 4 beta has moved the tabs up above the navigation bar, but not all the way up in the title bar where Chrome and Opera both have put them.

Firefox 4 beta with tabs on top.

Firefox 4 beta

Opera 10.6 with tabs in title bar.

Opera 10.6

Chrome 6 beta with tabs in title bar.

Chrome 6 beta

The hack

Now, the Firefox developers seem to be working on a fix for this, but in the mean time there’s a quick hack which lets you do this right now in your Firefox 4 beta.

First, locate (or create) your userChrome.css file.

Then add the following code:

#appmenu-button-container {
position: fixed !important;
}

#navigator-toolbox[tabsontop="true"] #TabsToolbar {
padding-left: 109px !important;
padding-right: 150px !important;
padding-top: 0px !important;
}

Firefox 4 beta with the tabs in the title bar.

This will make the tabs go all the way to the top of the window, which makes them very easy to target with your mouse when the window is maximized. (Since it doesn’t matter if you push your mouse outside the screen.) However, this means you can’t grab the window above the tabs to drag it. You can still grab it to the right of the tabs though. With the code above, there will always be an area next to the minimize-maximize-close-buttons which you can drag.

If you like, you can move the tabs 2 pixels down from the edge by changing the padding-top value to 2px. (Or 3 pixels. Or 4. Or 5. Or 200. But that might not be optimal.)

Also, if you want to make the tabs slightly narrower (to give you more draggable area) you can add this to the userChrome.css file:

.tabbrowser-tab:not([pinned]) {
max-width: 180px !important;
min-width: 50px !important;
}

Hope you found this as useful as I did. Thanks to Gdgtry for the original code!

Monday, August 16th 2010

Things to like in Firefox 4

I’ve been using the nightly builds of Firefox 4 for a while now, and thought I’d just blog about a few of the nice improvements that have been made.

Sync

Firefox now lets you connect and sync your bookmarks, passwords, history and settings between different computers. Personally, I have been using the Weave extension to do this for quite a while. Specifically I have synced history and passwords between my home and work computer. Bookmarks I have intentionally kept separate.

The especially nice thing is that this works with Firefox Mobile too. And if you have an iPhone, there is the Firefox Home app which loads your Firefox history, bookmarks and tabs for the Safari browser.

Tab sets

A new feature for those who have a *lot* of tabs open. With tab sets, you can hit Ctrl+Space and organize your tabs into groups. It is hard to explain in words, so have a look at the video here.

New theme

Firefox’s look has been given a complete overhaul. The goal of the new theme is to get out of the user’s way and to leave as much space as possible for the web content.

Here’s what the end result should look like:

Mockup of Firefox 4 theme

The current betas have parts of the new theme, but not all of it.

For anyone using Windows Vista or Windows 7, this will be a welcome update since it fits better in with the operating system. Especially since the new theme supports Aero Glass, i.e. the semi transparent windows in Vista & 7.

Tabs on top

One major part of the new look is the fact that tabs have been moved to the top of the window, above the navigation and bookmark bars. (Anyone who wants the tabs below the navigation bar can move them back.)

There are pros and cons to both placements. Having them at the top feels more logical though, since the tab applies to navigation buttons and the location bar. Also, there is screen space to be saved if you push the tabs all the way to the top of the window when maximized. This hasn’t yet been fixed, but it looks like it will be.

WebM support

WebM will probably be the next big thing on the web. Imagine being able to watch video on the web without the hassle of plug-ins? Well, when the web browsers all support a common video format that could become reality. At the moment, Internet Explorer is the only browser not to support WebM.

App tabs

In Firefox 4, you can right-click a tab and make it into an “App tab”. This basically pins the tab over to the left and hides the page title. Useful for tabs that you keep open all the time, such as e-mail or Facebook. Here is a nice video explaining the feature.

Behind the scenes

Apart from the new features that are directly visible to the user, Firefox 4 has loads and loads of improvements in the way it interprets web pages. So when you do upgrade, you’re also making life easier (& more fun!) for every single web developer out there.

If you haven’t already, you can get the latest Firefox 4 beta here.

Friday, June 25th 2010

Flickr is *Finally* Being Updated

Flickr have at long last decided to release an upgrade to their users.

The upgrade is currently only visible if you’re logged in to Flickr, but will be rolled out to all visitors in the coming weeks.

There are many improvements, but the ones I like best are a larger default size (up from 500 to 640 pixels) on the photo page and a new light box mode for viewing photos larger.

Screenshot of the new Flickr photo page.

But I can’t help wondering why they didn’t go for at least 720 pixels while they were at it. Or why not – since this is 2010 – a design that adapts the photo size to the browser window, à la Picasa? Perhaps that wouldn’t make it possible for Flickr to apply their magical sharpening that gives all Flickr photos that crisp look.

The new page seems to be designed to fit into a 1024×768 screen. If that is a requirement, then I just wish they’d spend a few more pixels on the photo and a few less on the right hand column.

Are we going to have to wait another 6 years for the next size increase?

At least they made navigation more intuitive with arrows labelled Newer and Older just above the photo. If you’re viewing a set, the buttons are labelled Prev and Next. (I’ve been using Flickr since 2006 and I still haven’t learnt if older photos are to the left or to the right on the photo page.)

The new light box is much better than the old All sizes page. (The All sizes page still exists though, and has been improved too.)

Screenshot of the new Flickr light box.

Basically it is a response to the View large on black link that many users have been adding to their photo description.

This is better though. It has a dark grey background, and buttons to move back and forward through the photos. It also has a play button that gives you a simple slide-show. The old (Flash) slide-show is still available though.

One thing that has nagged me for quite some time is the fact that the 1024 pixel images look soft, especially in comparison to the medium 500/640 pixel size. I’d really like them to apply a little sharpening to the 1024 pixel images too.

To sum up, some great improvements. They’ve really identified Flickr’s weak spots, I just wish they had done even more to fix them.

Tuesday, June 22nd 2010

Family Photo Shoot

The other week I had the privilege of taking some family portraits of my cousin, his girlfriend and their daughter. It was great fun, and since they’re all so photogenic we ended up with loads of good photos. Here are just a few of them.

B01210 - 2010-06-13 kl 19.41-1B01124 - 2010-06-13 kl 19.28-2B01163 - 2010-06-13 kl 19.35B01084 - 2010-06-13 kl 19.25-1B01064 - 2010-06-13 kl 19.22-2B01147 - 2010-06-13 kl 19.33B01277 - 2010-06-13 kl 19.55-2B01247 - 2010-06-13 kl 19.52-1B01341 - 2010-06-13 kl 20.09-1

Tuesday, June 22nd 2010

Converting to DNG

After having thought about it loosely for ages, I decided to finally convert all my raw (CR2) files into the open DNG (digital negative) file format. But before I did so I sat down and did plenty of internet research to make sure I wasn’t doing something stupid.

If you didn’t know, DNG is Adobe’s attempt to create a universal and openly documented raw image file format. The (perhaps optimistic) idea being that camera makers will start using it instead of their proprietary raw formats (*cough* nikoncanon *splutter*). Whether or not this will ever become true remains to be seen.

Thankfully all photographers that want to can make use of DNG and its benefits regardless of which camera make they have, thanks to Adobe’s free DNG Converter.

Here are the factors that made me convert …

Future proof

Imagine the following scenario. Canon make a few bad decisions on their camera line-up. Nikon make a few really good ones. Nikon gains loads and loads of market share, making Canon a minor player. Canon is bought by Sony or Nikon, who proceed to terminate Canon’s own camera production. (Nikon users: Imagine the opposite.)

That could all happen in say five–ten years in a worst case scenario.

Then, in 2019, it is time to buy a new computer. And with a new computer comes a new operating system. Then, it turns out, there is no software for Windows 10 that reads CR2 files from a Canon EOS 30D. Dead end? Well, probably not, but there would be a lot of hassle for sure.

Actually, even if Canon are still around in 2019 it is quite possible that they won’t release software to cater for the oldest camera models and their raw files.

With DNG files the chance of there not being compatible software is much smaller since the specification is entirely open. (Read it here if you like.) Even if Adobe were to be blasted off the face of the earth, the DNG specification would live on. And someone in the intersection between photography geeks and computer geeks would most certainly write a program that can read DNGs.

Granted, you could argue that as long as Adobe’s DNG Converter is around there is no need to rush. And there isn’t really, but there are a few more pros that made me do the switch now. Read on.

Previews and metadata

DNGs will contain a preview JPEG (tiny, medium or full size) and all the metadata of the original raw file, plus any metadata you want to add such as keywords, titles, captions or develop settings. For anyone using Adobe Lightroom, Bridge or Camera Raw this means that you’ll have one DNG file instead of a CR2/NEF image file and an XMP metadata file next to it.

Also, when you’ve changed the appearance of a photo you can render a new preview JPEG and embed it in the DNG. (In Lightroom: Right click and choose Metadata -> Update DNG Preview & Metadata.) I don’t know how NEFs work, but with CR2 files there is definitely no way of updating the embedded JPEG.

File size

DNG files are often smaller then the camera’s raw file. This is thanks to better compression, but also thanks to the possibility to use a smaller size JPEG than in the original.

I chose the medium JPEG size (1024 pixels I think) and the DNG files are on average 19 percent smaller than the CR2s from my Canon EOS 50D. My thinking here is that I don’t really need a full size preview in the raw file once I have it on the computer. In the camera it’s a different matter – there I need the full size preview to be able to check focus. And even if I do choose to embed a full size JPEG the DNG ends up ~10% smaller.

It will be a while though before I will actually see the benefit of the smaller file size, because right now I’m keeping my CR2 files in parallel with the DNGs. I also have them backed up to our two external drives (one off location) as well as on DVDs. So I have essentially doubled my storage needs.

In a few weeks though I’ll probably feel 100% comfortable with the conversion, and then I’ll delete the CR2s from my working folders and only have the three backup copies.

No negatives?

Considering that DNGs are just that, negatives, there are very few drawbacks. The only one, as I see it, is that I won’t be able to go back and use Canon’s own raw converters Raw Image Task or Digital Photo Professional. This is a rather academic point though, since I have never wanted to use either of them since moving to Lightroom. The only reason I might want to do that in the future would be to see how much better raw image processing has become since I bought my camera. So I might make such a comparison before I actually chuck the CR2 files.

Conclusion

Being a Lightroom user, the DNG format is very useful. I’m not sure if DNG is quite as sweet a deal if you’re using some other raw converter though, and DNG isn’t necessarily for everyone. But for me it definitely is a great step up from the CR2 format. So far I haven’t had any second thoughts at all, and I doubt I will have any later on either.

Thursday, June 10th 2010

More Lightroom 3 Demos

Here are a few more hover comparisons of Lightroom 2 and 3. (Here are some previous ones I made.)

Highlight edges look much better in Lightroom 3.

See how Lightroom 3 deals with the highlights. Somehow it manages to get rid of those unnatural red edges.

Lightroom 3 can deal with chromatic aberration automatically.

Here you can see how version 3 automatically deals with chromatic aberration, based on what it knows about the lens that was used. Here I used my Canon 17-55mm, which is one of the many lenses that have been profiled by Adobe. Also, you’ll notice that Lightroom 3 is much better at showing the fine branches to the right.

Automatic correction of geometric distortion in Lightroom 3.

The automatic lens correction can also deal with geometric distortion. This lets you get rid of that bulging look you often get at the wide end of a zoom lens. Since this affects cropping slightly, I’ve personally left this off by default. I’ll only use it when necessary.

Automatic vignetting correction in Lightroom 3.

LR3 can correct for lens vignetting too, but more often than not I think vignetting adds some natural punch to a photo, including the example above. So I probably won’t use this very often at all.

Wednesday, June 9th 2010

Lightroom 3 and High ISO Images

Hover this image to see what Lightroom 3 can do with a hopelessly noisy ISO 12,800 photo:

High ISO noise reduction in Lightroom 3.

(This is a 100% crop from my Canon EOS 50D.)

And since I can set up defaults based on the image’s ISO setting, I can make it do that automatically.

Tuesday, June 8th 2010

Lightroom 3 is Out!

Sooner than I dared hope, Adobe have released the final version of Lightroom 3. The biggest improvement for me will be the automatic lens correction, which deals with chromatic aberration, vignetting and distortion based on lens profiles. (Although I will probably only get rid of chromatic aberration by default.)

Now I’m going to spend all afternoon playing around with the new features, and I’ll post my thoughts later on.

Friday, May 28th 2010

10,000 photos in 7 minutes

On Saturday I will have had my 30D for exactly four years. In those four years the camera has done 27,773 exposures, or 19 clicks a day on average.

Canon EOS 30D.

Out of those 27,773 exposures I have …

  • Kept 10,668 original raws and jpegs, which means I did 2.6 clicks for each kept photo.
  • Taken 2,724 (25,5%) vertical shots and 7,944 (74,5%) horizontal shots.
  • Made 27 panoramas.
  • Made 131 HDR’s.

Someone asked me, at the photography course last week, what I usually photograph. I’m always stumped by that question and never have a good answer. But now I do.

I’ve put all the 10,668 photos together into a stop motion video, or a 25 frame per second slide-show if you wish. This is probably not interesting to anyone but myself, but I guess it may inspire some other crazy (creative?) person to do the same with their photos. It does make your eyes rather sore after a few minutes though …

Here’s a table showing which lenses I’ve used the most:

Lens Number of kept photos
Sigma 17-70mm f/2.8-4.5 4,864
Sigma 10-20mm f/4-5.6 1,967
Canon EF 50mm f/1.4 1,495
Canon EF 70-300mm f/4-5.6 IS 1,433
Canon EF 75-300mm f/4-5.6 519
Canon EF-S 17-55mm f/2.8 IS 384
Canon EF 80-200mm f/4.5-5.6 4
Canon EF-S 60mm f/2.8 Macro 2

My workhorse has obviously been the Sigma 17-70mm, and it has served me well. In January I got a second hand Canon 17-55mm IS and sold the Sigma. The last two lenses in the table belong to a friend, I just tried them once.

The longest exposure I’ve taken was 28 minutes 25 seconds:

Star trails 2

Tomorrow (Friday) there’s a guy coming over who is interested in buying the 30D. This camera has a lot of life left in it, so whoever gets it I’m sure they’ll have plenty of fun with it.