What exactly does that Lightroom preset do?

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A couple of weeks ago, I was messing around with some presets I’d downloaded from the ‘net for Adobe Lightroom.  I quite liked the effect but I wanted to know what they were doing.  The version of Lightroom that I’m using (2.6) doesn’t let me edit an existing preset so I turned to the ‘net to find out how to work out what settings were being applied.  After asking my question on Quora it was less than 24 hours before Rob Sylvan responded and explained it’s as simple as exporting the preset as a .lrtemplate file and viewing it with a text editor.

Unlike Adobe’s extensible metadata platfrom (.XMP) files, Lightroom presets do not use XML but the format is pretty easy to follow (Mike Sweeney has written about Lightroom 3 presets and they look pretty similar in Lightroom 2.x to me). By examining the contents it should be possible to work out the changes that the preset makes.

Here’s an example I picked up from the ‘net that emulates Ilford HP4+ black and white film:

s = {
id = “D6783909-3334-45C7-A277-10FF62F8D9CE”,
internalName = “Ilford FP4+”,
title = “Ilford FP4+”,
type = “Develop”,
value = {
settings = {
AutoBrightness = false,
AutoContrast = false,
AutoExposure = false,
AutoShadows = false,
Brightness = 50,
ChromaticAberrationB = 0,
ChromaticAberrationR = 0,
Clarity = 30,
Contrast = 25,
ConvertToGrayscale = true,
Defringe = 0,
EnableColorAdjustments = true,
EnableDetail = true,
EnableGrayscaleMix = true,
EnableSplitToning = true,
EnableVignettes = true,
Exposure = 0,
FillLight = 0,
GrayMixerAqua = 36,
GrayMixerBlue = 10,
GrayMixerGreen = 36,
GrayMixerMagenta = -14,
GrayMixerOrange = 10,
GrayMixerPurple = -20,
GrayMixerRed = -25,
GrayMixerYellow = 38,
HighlightRecovery = 0,
LuminanceSmoothing = 0,
ParametricDarks = -6,
ParametricHighlightSplit = 75,
ParametricHighlights = 0,
ParametricLights = 5,
ParametricMidtoneSplit = 50,
ParametricShadowSplit = 25,
ParametricShadows = 0,
PostCropVignetteAmount = 0,
PostCropVignetteFeather = 50,
PostCropVignetteMidpoint = 50,
PostCropVignetteRoundness = 0,
Shadows = 5,
SharpenDetail = 25,
SharpenEdgeMasking = 0,
SharpenRadius = 1,
Sharpness = 25,
SplitToningBalance = 0,
SplitToningHighlightHue = 0,
SplitToningHighlightSaturation = 0,
SplitToningShadowHue = 0,
SplitToningShadowSaturation = 0,
ToneCurve = {
0,
0,
32,
22,
64,
56,
128,
128,
192,
196,
255,
255,
},
ToneCurveName = “Medium Contrast”,
VignetteAmount = 0,
VignetteMidpoint = 50,
},
uuid = “92CAD954-CC15-49BE-89C1-46F88058904E”,
},
version = 0,
}

Cloning my Mac’s hard drive to gain some extra space

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My MacBook (bought in 2008, unfortunately just before the unibody MacBook Pros were introduced) has always been running with upgraded memory and storage but it was starting to creak.  Performance is okay (it’s not earth-shattering but all I do on this machine is digital photography-related workflow) and it won’t take any more RAM than the 4GB I have installed but I was constantly battling against a full hard disk.

After a recent holiday when I was unable to archive the day’s shots and had to start filling my “spare” (read old and slow) memory cards to avoid deleting unarchived images, I decided to upgrade the disk. I did briefly consider switching to a solid state solution (until I saw the price – enough to buy a new computer), then I looked at a hybrid device, before I realised that I could swap out the 320GB Western Digital SATA HDD for a 750GB model from Seagate. The disk only cost me around £73 but next day shipping bumped it up a bit further (from Misco – other retailers were offering better pricing but had no stock). Even so, it was a worthwhile upgrade because it means all of my pictures are stored on a single disk again, rather than spread all over various media.

Of course, no image really exists until it’s in at least two places (so I do have multiple backups) but the key point is that, when I’m travelling, Lightroom can see all of my images.

I didn’t want to go through the process of reinstalling Mac OS X, Lightroom, Photoshop CS4, etc. so I decided to clone my installation between the two disks.  After giving up on a rather Heath Robinson USB to IDE/SATA cable solution that I have, I dropped another £24.99 on a docking station for SATA disk drives (an emergency purchase from PC World).

I’m used to cloning disks in Windows, using a variety of approaches with both free OS deployment tools from Microsoft and third party applications. As it happens, cloning disks in OS X is pretty straightforward too; indeed it’s how I do my backups, using a utility called Carbon Copy Cloner (some people prefer Super Duper). Using this approach I: created a new partition on the new disk (in Disk Utility), then cloned the contents of my old hard disk to the new partition (with Carbon Copy Cloner); then test boot with both drives in place (holding down the Alt/Option key to select the boot device); before finally swapping the disks over, once I knew that the copy had been successful.  Because it’s a file level copy, it took some time (just under six hours) but I have no issues with partition layouts – the software simply recreated the original file system on the partition that I specified on the new disk.  There’s more details of the cloning process in a blog post from Low End Mac but it certainly saved me a lot of time compared with a complete system rebuild.

Now all I need to do is sort out those images…

From snapshots to social media – the changing picture of photography (@davidfrohlich at #digitalsurrey)

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My visits to Surrey seem to be getting more frequent… earlier tonight I was in Reigate, at Canon‘s UK headquarters for another great Digital Surrey talk.

The guest speaker was Professor David Frohlich (@davidfrohlich) from the University of Surrey Digital World Research Centre, who spoke about the changing picture of photography and the relationship between snapshots and social media, three eras of domestic photography, the birth and death of the album and lessons for social media innovation.

I often comment that I have little time for photography these days and all I do is “take snapshots of the kids” but my wife disagrees – she’s far less critical of my work and says I take some good pictures. It was interesting to see a definition of a snapshot though, with it’s origins in 1860’s hunting and “shooting from the hip” (without careful aim!). Later it became “an amateur photograph” so I guess yes, I do mainly take snapshots of the kids!

Professor Frohlich spoke of three values of snapshots (from research by Richard Chalfen in 1987 and Christopher Musello in 1979):

  • Identity.
  • Memory (triggers – not necessarily of when the photograph was taken but of events around that time).
  • Communication.

He then looked at a definition of social media (i.e. it’s a media for social interaction) and suggested that photographs were an early form of social media (since integrated into newer forms)!

Another element to consider is that of innovation and, using Philip Anderson and Michael L Tushman’s 1990 theory as an example, he described how old technological paths hit disruption, there’s then an era of fermentation (i.e. discontinuous development) before a dominant design appears and things stabilise again.  In Geoff Mulgan’s 2007 Process of Social Innovation it’s simply described as new ideas that work, or changing practice (i.e. everyday behaviour).

This led to the discussion of three eras of domestic photography. Following the invention of photography (1830-1840) we saw:

  1. The portrait path [plate images] (1839-1888) including cartes-de-visite (1854-1870)
  2. The Kodak path [roll film] (1888-1990) from the Kodak No. 1 camera in 1888, through the first Polaroid camera (1947), colour film cartridges (1963) which was disrupted with the birth of electronic still video photography (1980-1990)
  3. The digital path (from 1990)

What we find is that the three values of snapshots overlay this perfectly (although the digital era also has elements of identity it is mainly about communication):

Whilst the inventor of the photograph is known (actually Fox-Talbot’s Calotype/Talbottype and Daguerre’s Daguerrotype were both patented in 1839), it’s less well-known who invented the album.

Professor Frohlich explained that the album came into being after people swapped cartes-de-visite (just like today’s photographic business cards!) which became popular around 1850 as a standard portrait sized at 2.5″ x 4″.  These cards could be of individuals, or even famous people (Abraham Lincoln, or Queen Victoria) and in 1854, Disderi’s camera allowed mass production of images with several on a single sheet of paper.  By 1860 albums had been created to store these cards – a development from an earlier past-time of collecting autographs and these albums were effectively filled with images of family, people who visited and famous people – just as Facebook is today!

The Kodak era commenced after George Eastman‘s patent was awarded on 4 September 1888 for a personalised camera which was more accessible, less complex than portrait cameras, and marketed to women around the concept of the Kodak family album.  Filled with images of “high days and holidays” – achievements, celebrations and vacations – these were the albums that most of us know (some of us still maintain) and the concept lasted for the next century (arguably it’s still in existence today, although increasingly marginalised).

Whilst there were some threats (like Polaroid images) they never quite changed the dominant path of photography. Later, as people became more affluent, there were more prints and people built up private archives with many albums and loose photographs (stored in cupboards – just as my many of my family’s are in our loft!).

As photography met ICT infrastructure, the things that we could do with photography expanded but things also became more complex, with a complex mesh involving PCs, printers and digital camera. Whilst some manufacturers cut out the requirement for a computer (with cameras communicating directly to printers), there were two inventions that really changed things: the camera phone and the Internet:

  • Camera phones were already communications-centric (from the phone element), creating a new type of content, that was more about communications than storing memories. In 2002, Turo-Kimmo Lehtonen, Ilpo Koskinen and Esko Kurvine studied the use of mobile digital pictures, not as images for an album but images to say “look where I am”. Whilst technologies such as MMS were not used as much as companies like Nokia expected [largely due to transmission costs imposed by networks] we did see an explosion in online sharing of images.
  • Now we have semi-public sharing, with our friends on Facebook (Google+, etc.) and even wider distribution on Flickr. In addition, photographs have become multimedia objects and Professor Frohlich experimented with adding several types of audio to still images in 2004 as digital story telling.

By 2008, Abigail Durrant was researching photographic displays and intergenerational relationships at home. She looked at a variety of display devices but, critically, found that there was a requirement for some kind of agreement as to what could be displayed where (some kind of meta rules for display).

Looking to the future there are many developments taking place that move beyond the album and on to the archive. Nowadays we have home media collections – could we end up browsing beautiful ePaper books that access our libraries?Could we even see the day where photographic images have a “birthday” and prompt us to remember things (e.g. do you remember when this image was taken, 3 years ago today?)

Professor Frohlich finished up with some lessons for social media innovation:

  • Innovation results from the interaction of four factors: practice; technology; business; and design.
  • Business positioning and social shaping are as important to innovation as technology and it’s design.
  • Social media evolve over long periods of time (so don’t give up if something doesn’t happen quickly).
  • Features change faster than practices and values (social networking is a partial return to identity – e.g. tagging oneself – and not just about communications).
  • Some ideas come around again (like the stereograph developing into 3D cinema).
  • Infrastructure and standards are increasingly key to success (for example, a standard image size).

I do admit to being in admiration of the Digital Surrey team for organising these events – in my three visits I’ve seen some great speakers. Hopefully, I’ve covered the main points from this event but Andy Piper (@andypiper) sums it up for me in a single tweet:

 

Allowing people to download a subset of images on Flickr

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My photostream on Flickr is reasonably well locked down.  I try to strike a balance between sharing and protecting my intellectual property (not that I use it to generate an income…).  Basically, I don’t add watermarks but everything is All Rights Reserved © (although they could be licensed, if they were good enough); only I can access my original image files; only I can print my images; and only I can download images.

RNLI Little Haven 7A few weeks ago though, I was enjoying a family holiday in Wales and I saw the local RNLI lifeboat crew returning from an exercise. I picked up my camera and grabbed some snapshots (and that’s all they were – there was no planning; I was shooting straight into the sun, etc.) but the Helmsman asked if I could send the images to him. Email’s not great for shipping around 12 megapixel images, so I thought I’d share them via Flickr. Unfortunately it seemed that I couldn’t let him download the images… not unless I dropped the security on the whole photostream.

Then I found a workaround.  Even though the default license I selected is All Rights Reserved ©, I can change the license on selected images. Granting a Creative Commons (i.e. Some Rights Reserved) license to the Little Haven lifeboat images gave others the option to download them. Result.

I’m sure this information is buried somewhere in the Flickr website but it didn’t come easily to me, so I’m sharing it here – hopefully it’s useful to someone else!

Rating images as part of a digital workflow

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Earlier this week, I was at my local camera club meeting and fellow geek Haydn Langley was presenting on digital asset management (together with a few technical tips and tricks for photo editing).

One particular “lightbulb moment” was when Haydn put up an example of rating images (e.g. in Adobe Bridge or Lightroom). I’ve never been able to get my head around this because, over time, my idea of what makes a good image changes (as I, hopefully, get better at it). Now I think the key is to adopt a system that works and stick with it – any rating will be subjective but at least you’ll be consistent.

Haydn suggested rating images using a system similar to this (based on a system proposed by Mark Sabatella):

  • 1 star: images that are of no real quality (e.g. out of focus) and won’t be missed if deleted.
  • 2 stars: acceptable image but not one of the best. Nothing special, but could be kept as a record shot.
  • 3 stars: one of the better images of a subject. A “keeper”.
  • 4 stars: one of the best images: worth sharing with others (e.g. on Flickr), or printing large.
  • 5 stars: comparable to pros that we admire. Worthy of competition entry.

I might adapt this slightly, but it’s a good starting point.

He also suggested using colours to indicate where a particular image has reached in the workflow, for example:

  • Red: stage 1 – ingested (i.e. imported, renamed, etc.)
  • Yellow: stage 2 – global metadata assigned (copyright, etc.)
  • Green: stage 3 – survived initial cull
  • Blue: stage 4 – post-processed, survived final cull
  • Purple: stage 5- image-specific metadata assigned (keyword tags for subject/content/style, etc.)

As I’m approaching 10000 shots since I bought my D700 2 years ago, I’ve got some work to do to “sort everything out” but this system should help a lot.  I guess I should also think about renaming images on import rather than storing them as _DSCnnnn.NEF!

Photographing the night sky

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Last Saturday saw a “supermoon” – where the Earth’s moon is both full and in perigeesyzygy and so appears larger than usual.  I went out to try and shoot some images of the moon over the river but it was too high in the sky for the effect I was really after and it slipped behind some clouds.  Later on, the sky cleared and I got out my longest lens to take a picture of the moon (albeit without anything to put its size into context) and this was the result:

Supermoon 2

I was pretty pleased with this – especially when I compared it with one taken from the International Space Station! – although  some of the other shots in the press showed an aeroplane silhouetted agains the moon, or the moon appearing more “yellow” as it rose.  It’s just a straight shot from my DSLR with a 500mm lens, tripod mounted, at a mid-aperture (f11) and slow-ish 1/125″ shutter speed, with ISO set to 200, and with exposure compensation set at -5 EV (to stop the moon from “bleaching out”). Other than a crop and saving it as a JPG, that’s about all it’s had done to it.

But taking photos of the night sky is not usually so straightforward and, previously, my best results had been using a similar setup, but shooting in daylight.  The image below was taken a couple of summers ago, whilst on holiday in France:

La Lune

For this shot, I used an entirely different technique – it was actually taken with a clear blue sky, in the evening, converted to black and white and then the black clipping was increased to make sure the blacks really were black.

Anyway, back to the supermoon – nice though it is, anyone can take pictures of the moon – but what about planets in our solar system? Without a telescope?

SaturnJoe Baguley tipped me off that Saturn was just down and to the left of the moon at that time and sent me a link to his shot, in which Saturn is just 12 pixels wide but its rings are clearly visible. My response: “Wow!”. I went back outside with my gear and tried to replicate it but it seems that, on this occasion, his Canon 5D Mk2’s pixel density beat my Nikon D700’s – 12 pixels wide at 400mm equates to 15 pixels at 500mm, but with 2,400,000 pixels per cm2 on the 5D vs. 1.4 on the D700. That meant I was looking at something just 9px wide and that sky was very, very dark… maybe I need to go out and buy a telescope (for my sons of course!).

(Thanks to Benjamin Ellis, who inspired me to go and take pictures of the moon on Saturday evening, to Joe Baguley for permission to use his picture of Saturn, and to Andy Sinclair, who suggested I should write this post. The two images of the moon used in this post are © 2009-2011 Mark Wilson, all rights reserved. The image of Saturn is © 2011 Joe Baguley, all rights reserved. All three images are therefore excluded from the Creative Commons license used for the rest of this site.)

Hardware lineup for 2011

This content is 14 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

This is a bit of a copycat post really but I saw Mike Taulty and Phil Winstanley‘s hardware lineups and thought it was a good idea. So, here it is, a summary of the technology I use pretty much every day and how I see that changing this year.

Car: Audi A4 Avant 2.0 TDI 170 S-Line

Audi A4 Avant 20 TDI 170 S-LineMy wife and I have been Volkswagen fans for a few years now (we find them to be good, solid, reliable cars that hold their value well) so, a couple of years ago, when I heard that Volkswagen and Audi were being added to our company car scheme, I held back on replacing my previous vehicle in order to take advantage. I did consider getting a Passat but the A4 (although smaller) had a newer generation of engine and lower emissions, so it didn’t actually cost much more in tax/monthly lease costs.

After a year or so, I’m normally bored/infuriated with my company cars but I still really enjoy my A4 – so much so that I will consider purchasing this one at the end of its lease next year. My only reservations are that I would really like something larger, sometimes a little more power would be nice (although this has 170PS, which is pretty good for a 2 litre diesel) and I do sometimes think that the money I contribute to the car might be better spent on reducing the mortgage (I add some of my salary to lease a better car than my grade entitles me to).

Either way, it’s on lease until I hit 3 years or 60,000 miles, so it’s a keeper for 2011.

Verdict 9/10. Hold.

Phone: Apple iPhone 3GS 16GB

Apple iPhone 3GSI actually have two phones (personal and work SIMs) but my personal needs are pretty basic (a feature phone with Bluetooth connectivity for hands free operation in the car) and I recycled my iPhone 3G when I was given a 3GS to use for work.

After having owned iPhones for a few years now (this is my third one), I don’t feel that the platform, which was once revolutionary, has kept pace and it now feels dated. As a result, I’m tempted by an Android or Windows Phone 7 device but neither of these platforms is currently supported for connection my corporate e-mail service.

The main advantages of this device for me are the apps and the Bluetooth connectivity to the car (although I needed to buy a cable for media access). I use Spotify and Runkeeper when I’m running but there are a whole host of apps to help me when I’m out and about with work (National Rail Enquiries, etc.) and, of course, it lets me triage my bulging mailbox and manage my calendar when I’m on the move. Unfortunately, the camera is awful and it’s not much use as a phone either, but it does the job.

I could get an iPhone 4 (or 5 this summer?) but I’d say it’s pretty unlikely, unless something happened to this one and I was forced to replace it.

Verdict 3/10. Not mine to sell!

Tablet: Apple iPad 3G 64GB

Apple iPadAfter several weeks (maybe months) of thinking “do I? don’t I?”, I bought an iPad last year and I use it extensively. Perhaps it’s a bit worrying that I take it to bed with me at night (I often catch up on Twitter before going to sleep, or use it as an e-book reader) but the “instant on” and long battery life make this device stand out from the competition when I’m out and about.

2011 will be an interesting year for tablets – at CES they were all over the place but I’ve been pretty vocal (both on this blog, and on Twitter) about my views on Windows as a tablet operating system and many of the Android devices are lacking something – Android 3 (Gingerbread [correction] Honeycomb) should change that. One possible alternative is Lenovo’s convertible notebook/tablet which runs Windows but features a slide out screen that functions as an Android tablet (very innovative).

I may upgrade to an iPad 2, if I can get a good resale price for my first generation iPad, but even Apple’s puritanical anti-Adobe Flash stand (which means many websites are unavailable to me) is not enough to make me move away from this device in 2011.

Verdict 8/10. Hold.

Everyday PC: Fujitsu Lifebook S7220 (Intel Core 2 Duo P8400 2.2GHz, 4GB RAM, 250GB hard disk)

Fujitsu Lifebook S7220My personal preference for notebook PCs is a ThinkPad – I liked them when they were manufactured by IBM and Lenovo seem to have retained the overall quality associated with the brand – but, given who pays my salary, it’s no surprise that I use a Fujitsu notebook PC. Mine’s a couple of years old now and so it’s branded Fujitsu-Siemens but it’s the same model that was sold under the Fujitsu name outside Europe. It’s a solid, well-built notebook PC and I have enough CPU, memory and disk to run Windows 7 (x64) well.

Unfortunately it’s crippled with some awful full disk encryption software (I won’t name the vendor but I’d rather be using the built-in BitLocker capabilities which I feel are better integrated and less obtrusive) and, even though the chipset supports Intel vPro/AMT (to install the Citrix XenClient hypervisor), the BIOS won’t allow me to activate the VT-d features. As a result, I have to run separate machines for some of my technical testing (I’m doing far less of that at work anyway these days) and to meet my personal (i.e. non-work) computing requirements.

My hope is that we’ll introduce a bring your own computer (BYOC) scheme at work and I can rationalise things but, if not, it’ll be another two years before I can order a replacement and this will soldier on for a while yet.

Verdict 6/10. Holding out for a BYOC scheme at work.

Netbook: Lenovo S10e (Intel Atom N270 1.6GHz, 2GB RAM, 160GB hard disk)

Lenovo IdeaPad S10In its day, my netbook was great. It’s small, light, can be used on the train when the seatback tables are too small for a normal laptop and I used mine extensively for personal computing whilst working away from home. It was a bit slow (on file transfers) but it does the job – and the small keyboard is ideal for my young children (although even they could do with a larger screen resolution).

Nowadays my netbook it sits on the shelf, unloved, replaced by my iPad. It was inexpensive and, ultimately, consumable.

Verdict 2/10. Sell, or more likely use it to geek out and play with Linux.

Digital Camera: Nikon D700

Nikon D700After a series of Minoltas in the 1980s and 1990s, I’ve had Nikon cameras for several years now, having owned an F90x, a D70 and now a D700. I also use my wife’s D40 from time to time and we have a Canon Ixus 70 too (my son has adopted that). With a sizeable investment in Nikon lenses, etc., I can’t see myself changing brands again – although some of my glass could do with an upgrade, and I’d like an external flash unit.

The D700 gives me a lot of flexibility and has a high enough pixel count, with minimal noise and good low-light performance. It’s a professional-grade DSLR and a bit heavy for some people (I like the weight). It’s also too valuable for some trips (which is when I use the D40) but I always miss the flexibility and functionality that the D700 body provides. Maybe sometimes I think some video capabilities would be nice but I won’t be changing it yet.

Verdict 9/10. Hold.

Photography PC: Apple MacBook MB062LL/B (Intel Core 2 Duo T7500 2.2GHz, 4GB RAM, 320GB hard disk)

Apple Macbook White (late 2007)It’s been three years since I bought my MacBook and, much as I’d like one of the current range of MacBook Pros it’ll be a while before I replace it because they are so expensive! In fairness, it’s doing it’s job well – as soon as I bought it I ungraded the hard disk and memory, and whilst the the CPU is nt as fast as a modern Core i5 or i7, it’s not that slow either.

For a machine that was not exactly inexpensive, I’ve been disappointed with the build quality (it’s had two new keyboard top covers and a replacement battery) but Apple’s customer service meant that all were replaced under warranty (I wouldn’t fancy my chances at getting a new battery from many other PC OEMs).

I use this machine exclusively for photography and the Mac OS suits me well for this. It’s not “better” than Windows, just “different” and, whilst some people would consider me to be a Microsoft fanboi and an iHater, the list of kit on this page might say otherwise. I like to consider myself to have objective views that cut through the Redmond or Cupertino rhetoric!

So, back to the Mac – I may dive into Photoshop from time to time but Adobe Lightroom, Flickr Uploadr, VueScan and a few specialist utilities like Sofortbild are my main tools. I need to sweat this asset for a while longer before I can replace it.

Verdict 5/10. Hold.

Media: Apple Mac Mini MA206LL/A (Intel Core Duo 1.66GHz, 2GB RAM, 120GB hard disk)

(+ iPad, iPhone 3GS, various iPods, Altec Lansing iM7 iPod speakers)

Apple Mac MiniMy Mac Mini was the first Intel Mac I bought (I had one of the original iMacs but that’s long gone) and it’s proved to be a great little machine. It was replaced by the MacBook but has variously been used in Windows and Mac OS X forms as a home media PC. These days it’s just used for iTunes and Spotify, but I plan to buy a keyboard to have a play with Garage Band too.

It may not be the most powerful of my PCs, but it’s more than up to this kind of work and it takes up almost no space at all.

Verdict 6/10. Hold.

Gaming: Microsoft Xbox 360 S 250GB with Kinect Sensor

Microsoft Xbox 360sI’m not a gamer – I sold my Playstation a few years ago because the driving games that I enjoyed made me feel ill! Even so, I was blown away by the Xbox with Kinect when I saw it last month. I bought myself a 250GB model and now Kinect Adventures and Kinect Sports have become family favourites (with a bit of Dance Central thrown in!). I can’t see myself getting into first person shooters, but I can see us doing more and more with the Xbox, particularly if I can use the Connect 360 application to hook into my media library. The final piece of the jigsaw would be BBC iPlayer on Xbox – but that looks unlikely to come to fruition.

Verdict 9/10. Hold.

Servers and Storage: Atom-based PC, Dell PowerEdge 840, 2x Netgear ReadyNAS Duo

As my work becomes less technical, I no longer run a full network infrastructure at home (I don’t find myself building quite so many virtual machines either) so I moved the main infrastructure roles (Active Directory, DHCP, DNS, TFTP, etc.) to a low-power server based on an Intel Atom CPU. I still have my PowerEdge 840 for the occasions when I do need to run up a test environment but it’s really just gathering dust. Storage is provided by a couple of Netgear ReadyNAS devices and it’s likely that I’ll upgrade the disks and then move one to a family member’s house, remote syncing to provide an off-site backup solution (instead of a variety of external USB drives).

Verdict 6/10. Hold (perhaps sell the server, but more likely to leave it under the desk…).

Cleaning my DSLR’s sensor… the quick (and inexpensive) way

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Right now, I’m attending photography workshop in North Wales, learning a bit more about digital photographic imaging. It’s been a good experience so far but, yesterday afternoon, I experienced a small disaster as not only dust but a tiny hair had appeared on all of the images I took, indicating that I had some sort of debris on my sensor (actually, it’s on the anti-aliasing filter, not the sensor but that’s being pedantic…).

Being in the middle of the Snowdonia National Park (albeit in overcast/wet weather) and on a course where I would take a lot of photos, this was not exactly welcome and I feared I’d need a costly professional sensor clean (after a weekend of creating images with hair on them). No-one in the class had any sensor cleaning swabs (not that I’ve ever used them, and I would have been a little nervous too on my still-in-warranty Nikon D700) but, luckily, one of the guys passed me an air blower and said “try this – but make sure you hold the camera body face down as you use it!”.

With the mirror locked up, I puffed some air around inside the body (it’s important not to use compressed air for this) and took a reference image – thankfully the debris was gone (and, because the front of the camera was facing down, it should have fallen out, not gone further back into the camera).

I breathed a big sigh of relief and thanked my fellow classmate. In just over a week its the Focus on Imaging exhibition – hopefully I’ll get along to it and one of the items on my shopping list will be a Giottos Rocket Air Blower

Backing up and restoring Adobe Lightroom 2.x on a Mac

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Over the last few days, I’ve been rebuilding the MacBook that I use for all my digital photography (which is a pretty risky thing to do immediately before heading off on a photography workshop) and one of the things I was pretty concerned about was backing up and restoring my Adobe Lightroom settings as these are at the heart of my workflow.

I store my images in two places (Lightroom backs them up to one of my Netgear ReadyNAS devices on import) and, on this occasion I’d also made two extra backups (I really should organise one in the cloud too, although syncing 130GB of images could take some time…).

I also backup the Lightroom catalog each time Lightroom runs (unfortunately the only option is to do this at startup, not shutdown), so that handles all of my keywords, develop settings, etc. What I needed to know was how to backup my preferences and presets – and how to restore everything.

It’s actually quite straightforward – this is how it worked for me – of course, I take no responsibility for anyone else’s backups and, as they say, your mileage may vary.  Also, PC users will find the process similar, but the file locations change:

I also made sure that the backups and restores were done at the same release (v2.3) but, once I was sure everything was working, I updated to the latest version (v2.6).

Reading EXIF data to find out the number of shutter activations on a Nikon DSLR

This content is 15 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few years ago, I wrote about some digital photography utilities that I use on my Mac.  These days most of my post-processing is handled by Adobe Lightroom (which includes Adobe Camera Raw), with a bit of Photoshop CS4 (using plugins like Noise Ninja) for the high-end stuff but these tools still come in useful from time to time.  Unfortunately, Simple EXIF Viewer doesn’t work with Nikon raw images (.NEF files) and so it’s less useful to me than it once was.

Recently, I bought my wife a DSLR and, as I’m a Nikon user (I have a D700), it made sense that her body should fit my lenses so I picked up a Nikon refurbished D40 kit from London Camera Exchange.  Whilst the body looked new, I wanted to know how many times the shutter had been activated (DSLR shutter mechanisms have a limited life – about 50,000 for the D40) and the D40’s firmware won’t display this information – although it is captured in the EXIF data for each image.

After some googling, I found a link to Phil Harvey’s ExifTool, a platform independent library with a command line interface for accessing EXIF data in a variety of image formats. A few seconds later and I had run the exiftool -nikon dsc_0001.nef command (exiftool --? gives help) on a test image and it told me a perfectly respectable shutter count of 67.  For reference, I tried a similar command on some images from my late Father’s Canon EOS 1000D but shutter count was not one of the available metrics – even so the ExifTool provides a wealth of information from a variety of image formats.