Digital Photography: The Raw or JPG Question

Most digital photographers who go beyond simply taking a few snapshots encounter the question of whether to “shoot in raw” or work with the JPG images produced by most cameras. There are some excellent guides on the internet that explain the technical details behind this decision and offer balanced lists of pros and cons for you to consider. For me though, these articles seemed to say it was just a trade-off between quality and storage space. In terms of technical details that’s a fair assessment, but it’s only when this makes a significant difference to your photography that it actually matters.

When you take a picture with a digital camera, the sensor is exposed to light which produces a pattern of electrical signals that are read off by the camera electronics. This relates to the amount of red / blue / green light falling on each part of the sensor, and a bit of maths can convert the signal details into a picture. The maths needs some other inputs to convert the electrical signals into the coloured pixels making up the resulting image, and these take into account various details such as white balance, ISO, lens distortion and image enhancement features such as sharpening. The raw image format for your camera typically stores the direct readings from the camera sensor, plus the other settings at the time you took the photograph. The JPG image from your camera stores the resulting picture after the maths has been done – and for a common and fairly wide range of scenes it’ll look great.

The key difference here is that, provided that you have software that can replicate the raw -> JPG conversion that your camera can do (and in many cases this is actually possible on the camera itself), then you can re-run the conversion with other settings. For example, lighting conditions might have changed but you didn’t adjust the white balance on your camera, or maybe you underexposed an image in manual mode – no problem, you can simply go back and create a second rendering of the image using the raw data with adjusted settings for the correct white balance or effectively raising the ISO. That’s amazing – it means that you can worry less about your camera settings and more about photographing things that might never happen again.

Raw images typically also record more detail in the image (this is the quality factor) – often using 12-, 14-, or even 16-bits per colour per pixel, whereas most JPG output will be at 8-bits per colour per pixel. The most wonderful thing about this is that the extra detail recorded in very dark (or very light) parts of your image – whilst all but invisible to the human eye – can be used to recover detail using the Shadow and Highlight recovery tools in your photo processing software.

I use a Nikon D3300 which can give me the Nikon proprietary NEF (raw) format, and/or a JPG output. A common situation where I struggle with taking photographs is at stage performances. Anyone who has tried to photograph a school play will be familiar with the combination of low-level lighting, moving subjects, an awkward location to photograph from, and the pressure to come out with a photo that does justice to the performers (and the photographer). I like to ensure that the exposure is fast enough to avoid motion blur, but this often results in very dark images even with the largest aperture available, or sometimes I want to narrow the aperture to increase the depth of field. I also don’t want to use flash as it’s often the case that the ambient light is key to the mood of the image.

By using the raw format I can shoot with my desired exposure and aperture settings (often using manual mode and/or keeping the ISO low) bring the dark images down to my computer, run them through Shadow recovery (I use Adobe Lightroom – often the Auto Tone feature does 90% of the work for me) and adjust the sharpening a little, and then print or generate a JPG for uploading to Flickr. Sometimes a little bit of smoothing is needed to help reduce any noise that is inherent in low-light photography.

What started off looking like an almost completely black image ends up as a nice clear picture with the main subjects picked out in the ambient light – and any highlights aren’t blown out because I’ve used Shadow recovery rather than just increasing the overall exposure. Yes, my raw files are around 12MB where the JPGs were only 4MB, but at the rate I’m storing pictures it’s going to take several years to fill up my 2TB drive – so I’m happy to say “Hurrah for shooting in raw!”.


Follow-up / Review Meetings in Outlook

Sometimes you use Outlook to arrange a meeting with a bunch of people, and the last action you take is to organise a review or follow-up meeting a few days later. Wouldn’t it be handy if you could “clone” the existing meeting request to another date with small adjustments to the timing, location, and invitee list?

The trouble is, whilst the Copy command in Outlook allows you to create a duplicate event, this has limited use for all-day events, and doesn’t enable you to amend meeting details before it is saved to your calendar. Outlook provides handy Quick Action operations to let you create a new Task from a Message, or create a new meeting with preset Subject and Recipients, but nothing to help with creating new meetings based on an existing appointment.

The good news is that help is at hand! The good folk over at HowTo-Outlook have provided a guide to adding a Create new meeting based on this meeting button for all recent versions Outlook.

Their simple guide provides a short piece of VBA code that you can cut-and-paste into Outlook and link to a new “Clone meeting” button on your toolbar/ribbon. It took me about 2 minutes to get this in place, and it’s already saved more time than that.

Towards the end of their guide, HowTo-Outlook show how you can make modifications to the fields that are copied to the new appointment. I found that a number of key fields were missing from the original code, so here’s my modified block under With olApptCopy:

With olApptCopy
        .Subject = olAppt.Subject
        .Location = olAppt.Location
        .Body = olAppt.Body
        .Categories = olAppt.Categories
        .Importance = olAppt.Importance
        .Duration = olAppt.Duration
        .RequiredAttendees = olAppt.RequiredAttendees
        .OptionalAttendees = olAppt.OptionalAttendees
        .Resources = olAppt.Resources
        .ReminderSet = olAppt.ReminderSet
        .ReminderMinutesBeforeStart = olAppt.ReminderMinutesBeforeStart
        .ResponseRequested = olAppt.ResponseRequested
        .AllDayEvent = olAppt.AllDayEvent
End With

This will copy over you attendee lists, any resources needed, the meeting duration, importance flag, reminders, and whether a response from attendees is requested.

Why Aren’t All Recipes Like This?

Working in IT means that I’m pretty familiar with process diagrams and explaining technical terms in plain English. I also cook a fair bit and just recently it occurred to me that, despite being around for centuries, recipes are still written like Victorian science experiments.

Traditional recipes don’t make it easy to work out up front where or when you’re going to need each ingredient, when the busy points are and when you can let things cook on while you wash up or grab that glass of wine. You have to read the whole thing in detail before you can get a feel for how many steps there are. Each ingredient is duplicated – once in the ingredients list and again in the method. It’s not always clear when you are going to be preparing things in parallel (marinate one item while chopping another) or series (cook 1 minute then add an ingredient). These are things that process diagrams are highly effectively at communicating quickly and easily.

I tried re-writing a recipe as a process diagram, and found that it really was easy to work with. So why aren’t all recipes like this one?

Beef and Kale Recipe - Process Version

Beef and Kale Recipe – Process Version

Going Walking? Pack It All!

I’d managed to get three overnight bags, two children, the birthday presents, and the camp bed into the car ready to head down to a family weekend. As I reversed out of the drive the usual panic set in – I’d obviously forgotten something critical, just not sure whether it was underwear, toothbrushes, or the laptop (you’re never really off duty when you work in IT). Nope, I remembered packing them all. Great!

We must have made it a whole mile down the road before I remembered that the laptop battery was dead and I’d left the charger at home. Given the traffic at that time of day it was a 15 minute round trip to remedy the mistake.

Heading back our of our road, my eldest daughter sighed and said “Daddy, you should make a list so you don’t forget things.” Quite right. So I did. One list for when we go camping, and one for going walking. A few friends heard about my lists, but rather than giving me one of those “Aw, old age setting in” expression, they asked for a copy. I guess it gets us all in the end!

Anyway, here are my lists. I tend to adjust them a bit for each trip – with a pen rather than electronically.

Get the check lists here: