A digital B&W epiphany

_8047882 copy

With the previous article on HDR, the zone system and dynamic range as background, I can now explain exactly what my B&W discovery was: it’s mostly to do with the highlights, but only in certain areas. And to make things more confusing, creating a natural-looking – perhaps even filmic image – required me to take processing steps that were both highly counterintuitive, but also go against everything else I’ve done and used successfully in the past. Read on if you dare; I can’t promise enlightenment, but I can certainly try for insight.

[Read more...]

Demystifying HDR, the zone system, and dynamic range

_8042033 copy
My eyes, my eyes! I had to work quite hard to make this as a) I don’t own any of those filter programs and b) I don’t do this kind of hyper toned, overlapping HDR. The actual, final version of this image is at the end of the article.

HDR/ High Dynamic Range photography is perhaps one of the greatest blessings and curses of the digital age of imaging. On one hand, we have retina-searing rubbish that’s put out by people who for some odd reason celebrate the unnaturalness of the images, encouraged by the companies who make the filters that make doing this kind of thing too easy – and on the other hand, there are a lot of HDR images out there that you probably wouldn’t have pegged as being anything other than natural. There is, of course, a way to do it right, and a way to do it wrong. I use HDR techniques in almost all of my images – I live in the tropics, remember, and noon contrast can exceed 16 stops from deep shadows to extreme highlights – we simply have no choice if you want to produce a natural-looking scene.

[Read more...]

To process or not to process?

_RX100_DSC2614b composite copy Ginza dusk.

This is the photographer’s analog of the classic fisherman’s dilemma: fish or cut bait?

I’ve always, for as long as I can remember being serious about photography, shot RAW and done some form of processing afterwards. The more potential the file had, the more processing; conversely, I’d also spend time trying to save files that probably weren’t compositionally worthwhile. And as much as I hate to admit it, in the early days, trying to hide photographic mistakes behind punchy processing. In effect, the processing was taking center stage instead of the image. One of the hardest things to do is create a strong, but natural looking image – both from a perspective and processing standpoint; in order for it to stand out well from reality, the light, subject and composition all have to be exceptional. The image has to tell a story – but that’s another topic I covered here and here.

Note: all images in this article are a half-and-half composite of Sony RX100 shots; the SOOC JPEGs are on the left half (especially obvious for the B&W images) and the processed RAW files on the right. The RAWs were converted to DNG first then run through my usual workflow; CS5.5 doesn’t natively support the RX100. Where the finished file was cropped to a different aspect ratio, I’ve followed the finished file. Some noise reduction was one on the high ISO files. As usual, go by what I say and not what you see – there’s web compression involved in the mix, and you aren’t looking at the original files on a calibrated monitor.

_RX100_DSC2614 crop
And a 100% crop of the above – a huge difference here, but aside from tonal density – not much in it at web sizes, is there?

For argument’s sake, I’m going to assume that you’re able to see, compose and execute the image you see at a particular scene when pressing the shutter. For the purposes of this discussion, I’m going to exclude conceptual and commercial work – there is simply no way you can achieve some frames in a single look, and it’s impossible to have a perfectly dust-free product in others – even if you can get the lighting perfect. We’re talking about creative, personal and documentary work only. The reality is that a lot of photojournalists and reports never leave the JPEG – and some even SRGB JPEG – realm as it is. There are many reasons for this; speed and throughput being the first, the display medium being the second – there’s no point in supplying a beautiful file that uses all 16 bits of the Prophoto gamut if it’s going to be printed on a halftone CMYK process on newsprint. It’s a waste of time. (That of course doesn’t mean you can’t shoot both a JPEG and a RAW and deal with the latter if you find yourself up for a Pulitzer.)

_RX100_DSC2172b composite copy
Giant chef. Either rendition works, frankly – I don’t mind the overall tonality of the SOOC image, even if it’s lacking the pop of the actual scene.

A recent email exchange with a hobbyist photographer friend has spurred me on to think about this topic a bit more. The question: is Photoshop really necessary? Shouldn’t a good image be able to stand on its own? Yes, but don’t good ingredients taste better when skilfully prepared and cooked? (The Japanese may disagree with the cooking part; I can’t blame them.)

To answer this, we need to backtrack a bit. In the early days of digital, JPEGs were simply not an option because cameras lacked the required processing power. Raw output was something that was simply a direct data dump off the sensor itself; the data stored (perhaps lightly compressed to save space) for later processing. JPEG file quality was simply, unusable compared to the standards of the day: film. It didn’t have the tonal subtlety, the dynamic range, the detail; to make things worse, there was an inherently blocky “digital-ness” to it that made images feel, well, unnatural. RAW processing was a way to partially get around that and reduce the gap – we could alter the conversion/ output algorithm to create an image whose shadow and highlight response more closely matched that of film. It was also a way to overcome some of the limitations of early sensors; notably color response, chroma noise and tonal accuracy.

_RX100_DSC2103b composite copy
Imperial Palace East Garden, Tokyo. The SOOC image is too green – the needles definitely didn’t look like that after a warm summer and heading into November.

_RX100_DSC2103 copy
100% crop. There’s quite a lot more detail and tonal subtlety in the processed image.

Postprocessing my raw files was a habit I acquired since shooting with a DSLR in 2004, and I haven’t shaken since. I don’t discount JPEG-only cameras, but I’d definitely take the availability of a RAW file into consideration when buying one. And I certainly don’t feel like an image quality evaluation is fair or exhaustive until I’ve run some RAWs through my normal workflow. However, recent experiences with first the Sony RX100 and more recently, the Fuji XF1, have made me revaluate this: in fact, the XF1 has such good JPEGs and such crappy RAW files (perhaps ACR is also to blame here) that I don’t think I’d ever shoot RAW on this camera; but I will still postprocess the JPEGs. However, this is not a RAW vs JPEG debate; it’s something a bit more fundamental: for non-critical applications, is it still worth spending time processing or not?

_RX100_DSC2046b composite copy
What happened here is perspective correction – nope, you can’t do this in-camera. Not much to fix with tonality, though.

Yes, the processed RAW files clearly look better at the 100% level, but you’d have to make a 120cm wide print to really see that. And for practical viewing purposes, the only difference was in the overall tonality (and sometimes not even then) of the image, which could easily be fixed by altered JPEG output settings. Downsizing hides all manner of dirty pixel-level flaws. Could it be that I’d been creating some unnecessary work for myself for some time, and hadn’t realized it? It was the same case with the JPEGs from the Nikon D600 I was testing around the same time; they looked great at typical display sizes, but started to fall apart at the pixel level. (Before you worry that I might have gone all Hipstagram on you, note that I’m always open to finding new ways to balance image quality and throughput – and that includes shooting Ilford PAN F in my F2T and then ‘scanning’ the negatives with a D800E. I’m just saying.)

Suppose you weren’t super-anal about image quality, though. Suppose you didn’t pixel-peep, or print large. Suppose you shared your images online or at most made 8×12″ prints. Remember the points of sufficiency; if your display medium is going to be that severely limited, then the reality is you might not see much of a difference if you set your camera up correctly. The strength of the image and its contents is of course going to make more of a difference; the camera is just a tool and medium.

_RX100_DSC1961b composite copy
Facebook break from shopping. Near zero difference in tonality, just a bit of shadow recovery and perspective correction. Again, the SOOC JPEG would be fine for 99% of uses.

The basic reason for shooting RAW and postprocessing is that there is no one-size-fits-all for camera settings; therefore it’s impossible to have these baked in to the JPEG development algorithms of a camera. Fair enough; however, these algorithms have been getting increasingly clever over time as processing power increases. (A lot of RAW files aren’t even composed of truly RAW data anymore, but that’s another topic altogether.) To push perfection with every frame, there’s no way around RAW and postprocessing, end of discussion. You simply cannot have a camera that’s smart enough to recognize when some parts of an image need to be dodged and burned; the day that happens, I think I’ll retire as a photographer.

There are cases where the format-imposed limitations can actually force you to make stronger images – spot metering for subject or highlights can result in more powerful compositions and fewer distractions, especially when you have very contrasty lighting. Alex Majoli’s early work with the Olympus compacts is a good example of this. I frequently use this technique to strengthen the mood of an image, regardless of what camera I’m using.

_RX100_DSC2062b composite copy
Port of Tokyo. The AWB got this one horribly wrong; it could have been the window I was shooting through that threw things off.

_RX100_DSC2062 crop
100% crop. Not as much extra detail as you would have thought.

Once again: pick the right tool for the job, and that includes your file formats. I think what might be useful is a set of guidelines as to when each method is useful; even for a person who can run through their entire RAW workflow for a file (excluding heavy duty retouching) in about 30 seconds, I’m considering moving to JPEG for some things. Firstly, I don’t need perfect files for everything; social/ personal/ family documentary etc. is one such thing. Secondly, I’ve been spending more and more time processing files as my workload increases and camera resolution gets higher; I simply don’t want to spend any more time in front of a computer than I have to. I’d rather be out shooting and meeting people. (An obvious solution would be to shoot less, but this somewhat defeats the point of being as photographer. And yes, I’m trying film again at the moment, too.) Client and professional work will always remain shot RAW of course – there’s no point in going to the nth degree to ensure pre-capture image quality with the best lenses and supports then throwing most of your tonal space away with a JPEG. And you never know what post-capture manipulations you might need to do later on.

The biggest downside of shooting JPEG is that your settings are pretty much baked unless you’re willing to change settings on the fly from scene to scene. (Some cameras offer bracketing for this, too.) In real terms, you have to make a conscious choice at the time of shooting whether you wan high key portrait color or low key B&W. On top of that, you have to deal with limited dynamic and tonal range, and that you have to get your exposure as close to perfect as possible in-camera. This is very different from shooting RAW with the aim to post-process afterwards; in this case, you always expose to the right (and even clip highlights slightly) to maximize tonal range in the low-noise highlight and midtone portions of the image. My RAW files look flat and a bit too bright; this is normal because matching exposure to the desired tonal map is a critical portion of the processing flow.

_RX100_DSC1931b composite copy
The camera got this one spot on – all I did was straighten out the perspectives a bit, and sharpen.

It’s important to note that you need to spend some time figuring out what the best JPEG settings are for your camera and shooting style; the rest of this article is meaningless if you’re shooting with the wrong settings. And regardless of whether you JPEG or not, I would always shoot RAW+JPEG – you never know when you might need the file later. Storage is cheap; do-overs are often impossible.

When it might be best to use a straight-out-of-camera JPEG (or film + minilab):

  • When file quality is secondary; anything intended for facebook or social email, for example. These distribution methods compress the hell out of the images, strip color information, and then to make things worse, viewing is almost always on a non-calibrated device. You can spend all the time in the world tweaking, but it’s going to look like crap if the display can’t make the required color.
  • In very high throughput situations, like sport or news or reportage. And dare I say it, wedding factories.
  • I’m cringing as I write this, but if you camera has a style preset you particularly like (and are okay adopting as your own style) then go right ahead…so far, I haven’t seen anything that fits the bill personally.
  • When you don’t have the time. If I go away for a week, I’ll shoot an average of 1,000-1,500 images a day; of this, perhaps 100 will be saved to review on a computer later; I’ll throw away another half, but the problem is now I’m stuck with 350 images to process. At say 1 min per image, that’s around six hours. A lot of what I shoot is documentary/ observation/ personal, and these don’t need processing. I am now being even more critical with my editing, but it’s still a lot of time to carve out when you don’t have any spare to begin with.
  • If you enjoy photography but don’t want to deal with the hidden back end that comes with it – the computers, the storage, ensuring you have enough power to run photoshop and that your converters are up to date…the list is endless.
  • What you see is pretty much what you get: if you’re learning, it’s much easier to see the effect of exposure or setting changes. With RAW, you have to use experience to visualize what you can get. This is probably the most common stumbling block I see amongst my students who are just starting to discover the power of Photoshop.
  • If your camera puts out lousy RAW files but amazing JPEGs – the XF1 is a great example of this.

_RX100_DSC2392bw composite copy
I’ve never used SOOC B&W before, though I doubt it would have been able to retain the slight tonal variation in the man’s trousers. I had to do quite a bit of dodging and burning to bring that out.

And in favor of RAW + Photoshop (or self-developed and printed film):

  • No question: when image quality is the first priority.
  • When you want to do something that can’t be done in camera; compositing, for instance.
  • When you don’t have many images to process
  • When you have no choice – either the JPEGs are crappy, or there are no JPEGs at all…
  • When you have to do perspective correction (and don’t have a tilt-shift lens).
  • In extreme lighting situations that can’t be handled out of camera.
  • When you need to make tonal/ exposure changes to part of the image only, and not the whole image; this is where dodging and burning comes in.
  • If you’re a control freak…

But wait, there’s a middle ground:

  • You can shoot RAW but batch process; I think Aperture and Lightroom are a good example of these halfway houses. The problem I see is that you’re spending nearly as much time as a full-blown individual Photoshop workover, but without the same control or output quality. And this somewhat defeats the point. That said, I do keep presets for various things – usually to do with color calibration for flash work or for certain types of lighting or cameras, or high ISO situations.
  • The other option is to have the camera output a very neutral JPEG and postprocess that; you can skip the RAW conversion step (although it is possible to open JPEGs in ACR and have the same adjustments, but not the same latitude of course). This actually frees up quite a bit of time; that minute can get down to 15 seconds or less if you have a fast computer – dodge and burn, curves, color correct, sharpen, save. And it does of course help that the files are much smaller, too. This is actually not a bad option – whenever I review a camera without RAW support, this is the method I use – but if you start to do any extreme tonal manipulations to the files, it will become obvious, especially at the pixel level.

_RX100_DSC1925b composite copy
Standing nap. Yes, it’s two files. Look carefully.

_RX100_DSC1925 crop
100% Crop. More noise, a smidge more detail, and slightly smoother tones; not a lot in it. And that’s with me looking at the full size files on my calibrated monitor, not the web crop; there’s even less difference here.

My currently preferred JPEG settings

Important note: currently, I’m using my JPEGs as preview images either for quick client contact sheets after a job. When shooting RAW-only, the JPEG settings apply to the preview image but not the RAW file - so I generally try to make them as close as possible to be representative of the tonal range I can get of the RAW file, i.e. flat and not saturated, but sharp. If I was shooting JPEG only, I’d run similar settings with the anticipation of doing some light processing work on them afterwards – the halfway house.

  • My current style is neutral and natural; I look for or create light first and foremost (though the latter doesn’t apply here; if I’m creating light, I’m also shooting RAW to maximize image quality). I want to retain a decent amount of the tonal range; however there’s no way to control the output curve for most cameras, which results in large dynamic range images appearing very flat. This means contrast is set to the lowest option, or close to it – depending on the camera.
  • It’s very easy to have individual color channels blow; thus reduce your saturation a notch or two.
  • Sharpening is a mixed bag; some cameras do this well, some don’t. But I don’t use zero sharpening, as a lot of the time this setting does actually affect the in-camera RAW conversion and the amount of detail extracted. It also helps you to determine if critical focus was achieved – I’ll usually run somewhere between neutral/ default and maximum.
  • White balance is on auto, but I will override it where necessary to avoid blown highlights.
  • Maximum quality and size, of course – with an extra RAW file saved, too.

There are still many reasons to shoot RAW – and even exclusively RAW – but I can’t help but feel those are eroding slightly; and for the vast majority of users – even serious hobbyists – it might not be necessary all the time. Admittedly, my main reason for revisiting this topic is in the interests of curiosity and efficiency; I don’t think there’s as much of an image quality penalty as there used to be, especially for smaller output sizes. I haven’t decided just how much SOOC JPEG I’m going to use at this point – edited JPEGs are probably as far as I’m going to go – but you can be assured that I won’t use it at all until I feel that I’m getting the image quality I want. And in any case, I can still apply my normal workflow to the JPEGs – the tradeoff is significantly shorter processing time against a bit less latitude. Moral of the story: get it right out of camera; if it’s not there, you’re not going to be able to add it in afterwards. MT

____________

Visit our Teaching Store to up your photographic game – including Photoshop Workflow DVDs and customized Email School of Photography; or go mobile with the Photography Compendium for iPad. You can also get your gear from B&H and Amazon. Prices are the same as normal, however a small portion of your purchase value is referred back to me. Thanks!

Don’t forget to like us on Facebook and join the reader Flickr group!

appstorebadge

Images and content copyright Ming Thein | mingthein.com 2012 onwards. All rights reserved

Some thoughts on reprocessing and revisiting images

Reprocessing
The difference of seven years of Photoshop skill: 2012 (left) vs 2005 (right). Mandarin duck; Nikon D2H, Tokina AF 80-200/2.8

From day one, I was told by every serious photographer two things: one, don’t delete anything because opportunities never come twice, but storage is cheap; two, shoot raw, and keep your raw files somewhere in an archive. Or at very least, keep your original jpegs if your camera doesn’t do raw.

I only recently started doing the former: I keep all of the raw files from a commercial shoot, and then send a contact sheet off to the client to let them pick the ones they want retouched – usually between 10 and 50%, per whatever the commercial agreement was. The rest stay in the archive in case they come back later and want to license additional images, or I need to composite in bits during the retouching. For my personal work, I cull ruthlessly – the rationale and the methodology was previously covered in this article.

_DSC8648b copy
Venice, 2004. Nikon D70, 24-120VR

One of the more popular justifications given for being the image-hoarding equivalent of a packrat is that you might want to go back and reprocess your files later once technology or your technique improves, so you can get more out of the original image. This makes sense from a logical point of view, but from a practical standpoint, if you’ve improved that much as a photographer it’s probably because you’re out there shooting new stuff and refining both the shooting and processing portions of your technique. In short: I’ve never gone back and reprocessed anything. Well, there might have been a couple of exceptions when an image was licensed to a client and adjusted for print or to the client’s taste, but nothing more than that. I honestly don’t have time to reprocess my personal work.

_DSC8648-2012 copy
Venice, 2012

However, I suppose we could all find time to do things if we thought they were important enough. And this brings me to the biggest argument against reprocessing images: your artistic vision for that particular image, or what you saw in that particular scene, will never be stronger than at the time of shooting. It just fades gradually as time passes; this is just a consequence of the way the human brain works: we forget things over time. And unless you suddenly look at an image again later and find something that bothers you hugely, you’re probably just going to go with whatever you thought was best at the time.

_MT39141bw copy
Courchevel cloud, 2005. D2H, Sigma 70-300/4-5.6 APO

However, in the interests of academic curiosity, I’m going to do some reprocessing for this article. I don’t know how it’s going to turn out: I’m writing this philosophical portion of the article before doing the work. Frankly even finding shots that meet my compositional standards is tough, because I (hope, at any rate) have moved on significantly in my photographic abilities since these images were shot. There’s no point in reprocessing something from last month, because I don’t think you’ll see any difference in the before and after – one’s style changes slowly, like a tree growing. But one’s style is also defined by the way you shoot, and there are things I do routinely now – for instance, cinematic, very shallow DOF in low light – which I couldn’t physically have done back then, because the equipment didn’t exist.

_MT39141-2012 copy
Courchevel cloud, 2012.

The archives have been raided, and yielded a number of images. In some cases I’ve had to use the original JPEGs as a starting point because I didn’t have raw files; this is obvious in the lack of file quality and noise. There’s not a lot I can do about that, unfortunately; 8 compressed bits of tonal information can never be made into 16 complete ones. You’ll also see in some places I disagreed with my original processing choice of B&W vs color, and even the final crop – I guess as one’s style and eye evolves, we see different things in the same image. The eagle-eyed of you will also notice small corrections to composition via distortion, cropping or stretching; I normally do these things today, but I’m sure I wasn’t doing any of it at the time. Similarly, dust/ speck cloning was something I never bothered with. I’ve picked a wide range of subjects, too. I’m going to post the final state I arrived at back at the time – usually a mildly edited jpeg – and the reprocessed, 2012-version. I would highly encourage all of my readers to share their thoughts on which they prefer, and why; let the comments section be a forum for discussion. I’ve also provided some thoughts below on each individual image.

_M227904bw copy
Nikko station, 2007. Nikon D200, 17-55/2.8

_M227904-2012 copy
Nikko station, 2012. There’s a lot of empty space in the top portion of this image, especially the overexposed window at top left; it threatens to imbalance the composition – hence switching to a 16:9 crop. The original colors in the scene were delicate and tonally interesting, so I opted to rebalance for true color instead of do another monochrome conversion.

_DSC8280b copy
Piazza San Marco, Venice, 2004. Nikon D70, 24-120VR

_DSC8280-2012 copy
Piazza San Marco, Venice, 2012. This is one of the very early images from my DSLR career; up til this point I’d been using a super zoom compact. If I’d known any better, I’d have used a different exposure time to retain more suggestion of people in the scene, or better yet, stacked many exposures. And f10 isn’t exactly the optimal aperture on the first-generation 24-120VR. Aside from the obvious color fix – this is much closer to the reality I remember than the original processing – verticals, horizontals and tonal maps have also been tweaked. I don’t think the composition is particularly fantastic, but gimme a break, I just started at this point, okay? :)

_M227348 copy
Kinkakuji, Kyoto, 2007. Nikon D200, 17-55/2.8

_M227348-2012 copy
Kinkakuji, Kyoto, 2012. You’ll notice there isn’t a lot of difference between the two; this was from a later period in my photographic career where my processing was both more refined, and I was shooting RAW (with all of the associated available adjustments) to hand. I didn’t change the composition, though I’m not 100% happy about the positioning of some of the edge elements in the frame; the majority of the change was to sort out the dayglo colors, and the horribly inaccurate foliage. It was a particularly hot summer that year; the image was shot in August, and the trees were looking a little dry and wilted – I think this is much closer to the reality I remember at that point.

_M215519 copy
Scarlet Ibis, 2007. Nikon D200, AI 500/4 P

_M215519-2012 copy
Scarlet Ibis, 2012. Not a lot of change; I punched up the color a little, because these birds are pretty darn striking in person. I don’t remember the color of the swamp, so I left it much as-is. Again: a late 2007 image.

_MT39064 copy
La Tania sunset, France. Nikon D2H, Sigma 70-300/4-5.6 APO

_MT39064-2012 copy
La Tania sunset, France. WHOA! You’re probably wondering what happened here – of all the images, this is the one which is the most different from the original. Aside from the obvious change in crop, I’ve now got the shadow recovery tool at my disposal, and better yet, an intimate familiarity with it. The problem I faced at the time was the sunset was a) both not very punchy and b) the native dynamic range of the scene was already quite challenging, meaning that making the highlight portion punchier would have sacrificed tonal detail in the shadows. At the time, I had no clue how to unblock it. I don’t remember the exact color of the the scene, but I suspect it was probably somewhere between the two images. Which one do you prefer?

_DSC8121bw copy
Venice, 2004. Nikon D70, 24-120VR

_DSC8121-2012 copy
Venice, 2012. At the time, I was influenced heavily by a number of ‘classical’ monochrome shots I’d seen in magazines; as a result, this street scene was instantly converted. What I failed to notice in the original – until now, fortunately I still have the original color jpeg – is that the light spillage from the shop windows at left actually give the image an interesting structure that’s lost in black and white because of the similarity of luminance values between the warm-lit stone and the regular stone. I’ve attempted to bring this back, however the limited dynamic range of the jpeg has led to less smooth tonal transitions than I’d be able to achieve with a raw file. Actually, working this ‘vintage’ jpeg reminded me a lot of dealing with iPhone files – imperfect color, blocked shadows, blown highlights, and a decidedly averse reaction to resizing.

_DSC8066b copy
Canal reflections, 2004. Nikon D70, 24-120VR

_DSC8066-2012 copy
Canal reflections, 2005. To me, reflections are juxtapositions. Our minds invert them subconsciously anyway, otherwise we would recognize them as the mirror images of their own selves; I usually take this further by treating the image as the real subject, and the subject as the abstraction – what’s the difference anyway, since all images are subjective and facsimiles of the real thing? Aside from that obvious flip, the verticals have been corrected, and the tonality smoothened out – especially in the water, so it looks more like liquid and less like a block of color.

_MT73080 copy.jpg
Mandarin duck, 2005. Nikon D2H, Tokina AF 80-200/2.8. For some odd reason Flickr won’t let me re-upload a modern duplicate of this image with the right border and matching image size, so I apologize. However, the original image remains the same.

_MT73080-2012 copy
Mandarin duck, 2012. Improved color accuracy and worked on micro contrast a little.

With all of the reworked versions, I’m not sure I can say that I 100% prefer the 2012 version over the originals – photography is very much the sum of the parts, and the interaction between the original framing and the processing is very much a large component of that. The processing methodology I currently use doesn’t really fit the vision I had back then, and vice versa. Score one for the argument against do-overs: you really can’t fix it in post; you can enhance an image, but not fix something that’s fundamentally wrong with the composition or lighting. Here’s another interesting idea for a future article – reprocessing somebody else’s raw files. Might provide an interesting insight into how much difference Photoshop really makes…MT

____________

Visit our Teaching Store to up your photographic game – including Photoshop Workflow DVDs and customized Email School of Photography; or go mobile with the Photography Compendium for iPad. You can also get your gear from B&H and Amazon. Prices are the same as normal, however a small portion of your purchase value is referred back to me. Thanks!

Don’t forget to like us on Facebook and join the reader Flickr group!

appstorebadge

Images and content copyright Ming Thein | mingthein.com 2012 onwards. All rights reserved

Follow

Get every new post delivered to your Inbox.

Join 27,227 other followers

%d bloggers like this: