Author Archives: Andrew

An Open Letter to Panasonic

I was recently invited to provide some feedback to Panasonic on the design of the GX8, and thoughts for its successor. I’ve decided to draft this in the form of an open letter, and also post it on my blog. Apologies to regular readers who may have seen much of this before – please feel free to move on…

It’s probably worth setting out my credentials here. I have been a fairly regular user and purchaser of Panasonic electronics since I bought my first Technics hi-fi back in about 1979. In 2012 I was looking for a smaller option than my large Canon cameras and lenses. I had a look at the Olympus OM-D series, but realised from a quick handling test that I much preferred the  Panasonic GH2. In use I found I liked not only the lightweight, tiny package, but was impressed by image quality which easily bettered that of the Canon 7D (using Capture One with both cameras). Since then things have moved on with two generations of Panasonic upgrades, and I currently have a GX8 as primary camera, with a GX7 as back-up, an infrared-adapted GF3, and a GF6 for which I have a third party underwater housing. In the meantime I have owned and sold both a GH2 and GH4, and I tried but didn’t get on with the GM5. In terms of lenses I have the two F2.8 zooms, the 100-300mm, the diminutive 45-175mm, the 3D lens and a couple of copies of the tiny 14-42mm power zoom. For balance I also have an Olympus 9-18mm zoom rounding out the wide end of the zoom range, and my compact cameras are from other manufacturers, a Sony RX100mk4 and a Canon S120.

I write this having used the GX8 as main camera on a recent photo tour of Bhutan. I think that makes me quite qualified to comment on the cameras’ capabilities.

Up front I’d like to record that my other comments notwithstanding, the GX8 is a great camera. It’s fast and produces great image quality. Its viewfinder is large and bright (although I have to acknowledge that the Fuji XT1 is even nicer). Handling is good, but not perfect, and the first area for potential improvement…

Ergonomics

Size-wise, the GX8 is pretty much perfect. I’m a European male of fairly average size, and "naked" the GX7 is just a bit too small for me. I’ve always used it with the bottom half of the "ever ready" case, which improves the fit to my hands no end. The GX8 is almost exactly the size of that combination. However it would be a mistake for the successor to grow again.

Beyond that, I have one major complaint about the GX8’s ergonomics, and a couple of minor ones.

The major complaint regards the dedicated exposure dial, which should go, for three separate reasons:

  1. It’s ergonomically clumsy compared with its predecessors. Like many users of better digital cameras, my usual approach is to select an appropriate base exposure mode (e.g. aperture-priority for static or slow-moving subjects) and primary setting (e.g. f/8), see what the camera’s auto-exposure does with it, and dial in exposure compensation to suit. Ideally I do this with the viewfinder to my eye, without moving the camera from the scene. The GX7 and GH4 have controls perfectly positioned to do this: the index finger can easily adjust the primary exposure control, and the thumb can easily adjust compensation via the rear dial. The right hand remains positioned ready to shoot at the decisive moment. The left hand supports the camera and works the lens, but the right remains in primary control of composition. On the GX8 you have to take the right hand off the primary controls and reach in towards your eye to fiddle with the compensation dial, during which time you can lose position, or even a shot. That has happened to me.
  2. It doesn’t work visually for older users. Users aged 50+ (the ones who buy a lot of expensive camera gear and take it on expensive trips) often have to fiddle with glasses to move between viewing stuff at a distance (e.g. a typical scene) and close up (e.g. buttons on cameras). In my own case the markings on the exposure dial are almost invisible glasses-on. For such users it’s a much better model just to have a continuous control, and feed back values through the EVF, just like you do for most other settings.
  3. It breaks the custom settings model. If you have a non-zero value set on this, that over-rides any value you may have programmed into custom settings. The custom settings should be able to control as much of the camera settings as possible.

A return to the GX7’s design would be much appreciated.

Some of the same concerns also apply to the focus mode control. Again, it breaks the custom settings model (so that, for example, I can have a custom mode for "high speed action" but then have to remember to manually set AFS/AFF, and turn it off afterwards). Again it requires focusing the eyes on the camera instead of the scene, which may mean fiddling with glasses for older users, although personally I find the graphics on it are large enough that’s not such a problem as with the exposure compensation. Worst however is that  it’s only half a control – you still have to set either AFS or AFF via a menu. My preference would be to replace it with a button or continuous dial which just cycles through all four focus modes. If not, please at least make the next version a four-position switch with AFS and AFF separate.

Generally I think it would make sense to have two clear, separate strategies for your two flagship cameras. The GH series have most functions on separate dedicated dials. Great for those who like that approach. The GX series should keep everything on buttons or continuous dials for those who prefer that approach. Please don’t confuse the two.

Finally, I find it too easy to accidentally press Fn7 when I’m picking up the camera. The positioning is OK, given its "DOF preview" role, but I wonder if it might be possible to give it more of a positive detent?

Electronics

The loss of the built-in flash compared with the GX7 and GH4 is an annoyance. Although I rarely use use one as I can usually rely on the high ISO capability of the new cameras, there are exceptions. In Bhutan I found myself at a cultural event where we were trying to shoot movement in very low light. Even at ISO 6400 and f/2.8  the results were unacceptable. I did have a small separate Metz flash but I couldn’t get it to work reliably. The results with the GX7’s on-camera flash might not have been ideal, but I would have got something. Please restore this in the GX9 if you can.

While the viewfinder is large and bright, it does seem to be more sensitive to white balance changes (or errors in auto white balance setting) than previous models. This means that you may see a bit of a red or brown cast on the live image in some cases, which doesn’t affect the captured RAW image but can be slightly off-putting, especially trying to use the GX8 and GX7 back to back with different lenses. If this is a deliberate change fine, but if it’s an unexpected side-effect of the viewfinder improvements it would be worth addressing.

Even though it packs a much bigger battery than the GX7 battery life is still only moderate. in Bhutan I used almost three per day on a couple of occasions, and that could have increased if we had done significant action shooting. The change in battery model is a slight inconvenience as all my other Panasonic cameras share the same model, but at least you can use the BLC12 charger for all down to the tiny battery in the GM5, which is good design.

Features

There are a number of features which are regularly requested by professional or "enthusiast" users of mid-high end cameras which I believe it would be relatively easy to implement in the GX8’s successor. Some might even be possible within firmware enhancements, although I’ve no idea how that would fit into the product life-cycle.

It’s important to understand that to deliver for the target market who really want to exploit and stretch these features, they have to be supported by the generation of full RAW files. JPEG-only implementations are at best a compromise which negate many of the fundamental capabilities of the camera in the hands of more expert users.

So here are my requests:

  1. Expose To The Right Metering. Although the latest sensors and RAW processing software offer much-improved highlight handling, an image is still effectively irrecoverable if there is substantial over-exposure of the highlights. With a difficult scene I tend to manually dial in exposure compensation until the highlights are just fully exposed, and then shoot. While advances such as the zebra pattern make this easier, why can’t I just tell the camera that this is my preferred metering mode and get it automated?
  2. Built-in HDR with RAW Support. The built-in HDR is JPEG-only with fixed settings, which is very limited. To add insult to injury the camera supports my preferred 2-stop exposure bracket in the “HDR”  mode but I can’t set it manually! Ideally the HDR mode would also save 3x RAW files, for later processing. If that’s not possible, please at least make it possible to set auto-bracketing with 3 images 2 stops apart, and set some EXIF data so that the images are tagged as a group.
  3. Automated Focus Bracketing. The new "Post Focus" mode gets close to this, especially in combination with the latest version of Helicon Focus, but being based on 4K video it effectively generates 8MP JPEG files, which don’t allow for any significant post-processing of the image, and produces an output significantly below the native resolution for stills. Now that you have created a "take an image autofocused at each point in turn" algorithm, please can we have a version with does a "focus sweep" but generates a series of related RAW files? It doesn’t matter that it would run a bit slower, and you could minimise the data set by only taking shots at distinct focal distances.
  4. Hyperfocal Auto-Focus. It would be great if I could set a focus mode along the lines of "cover all focus points if you can". Alternatively as the GX8’s EXIF data includes "hyperfocal length" it also ought to be possible to have an autofocus mode which sets automatically to this, and then maybe shows what’s in focus via focus peaking. I know I can do this manually, but an automated option would be very useful.
  5. Note Taking, Tagging and Content Enrichment. The camera has some annotation and tagging capabilities, but they are limited, and JPEG-only. At the very least these should work equally for RAW files. If you don’t want to modify the RAW file after capture (understandable), then why not write to a standard XMP file?. Most RAW processors will then read this information at the same time as the RAW, and write it into the EXIF data of the output files.
  6. Tripod Sensitivity. Although stabilisation mechanisms are getting progressively more tolerant, the manual still recommends you manually switch stabilisation off when the camera is on a tripod. Why can’t this be automated?

Platform

I’ve written at length about why camera manufacturers should stop thinking of their cameras as monolithic products, and start thinking of them as platforms for development, just as all mobile phones have become and Panasonic and Sony (to name just two) already treat their televisions. This would allow the wider development community to deliver the features in the previous section, and others, if Panasonic don’t want to do so themselves. To make this work, we’d need the following:

  1. A software development kit, API and "app store" or similar for the development and delivery of in-camera "apps". For example, it should be possible to develop an ETTR metering module, which the user can choose as an optional metering mode (instead of standard matrix metering). This would be activated in place of the standard metering routine, take in current exposure, and return required exposure settings and perhaps some correction metadata. Obviously the camera would have to check that the returned values are "safe" values, but in a mirrorless camera it should be very easy to check that the exposure settings are "reasonable" and revert to a default if not. Other add-ins could tap into events such as the completion of an exposure, or could activate functions such as setting focal distance. The API should either be development language-agnostic, or should support a well-known language such as Java, C++ or VB. That would also make it easier to develop an IDE (exploiting Visual Studio or Eclipse as a base), emulators and the like. There’s no reason why the camera needs an "open" operating system.
  2. An SDK for phone apps. This might be an even easier starting point, albeit with limitations. Currently Panasonic provide some extended functions (e.g. geotagging) via the companion "Image App", but this app is "closed", and if it doesn’t do you want, that’s an end of it. It should be relatively easy to open up this API, by providing libraries which other developers can access. My note taking concept could easily be delivered this way. The beauty of this approach is that it has few or no security issues for the camera, and the application management infrastructure is delivered by Google, Apple and Microsoft.
  3. An open way to share, extend and move metadata. The right solution is support for XMP companion files which can accompany the RAW file through the development process, being progressively enhanced by different tools, and relevant data will be permanently written to the output JPEG. This doesn’t have to be restricted to static, human-readable information. If, for example, the ETTR metering module can record the difference between its exposure and the one set by the default matrix method, then this can be used by the RAW processing to automatically "normalise" back to standard exposure during processing. XMP files have the great advantages that they are already an open standard, designed to be extensible and shared between multiple applications, and it’s pretty trivial to write code to manipulate them, so this route would be much better than opening up the proprietary EXIF metadata structures.
  4. A controllable camera. What I mean by this is that the features of the camera which might be within the scope of the new "apps" must be set via buttons, menus and "continuous" controls (e.g. wheels with no specific set positions), so that they can be over-ridden or adjusted by software. While I personally prefer the ergonomics of "soft" controls, in this instance they are also a solution which promotes flexibility, which is what we’re seeking to achieve here.

This doesn’t have to be done in one fell swoop, and it might not be 100% appropriate for every camera. However Panasonic could make a great start by opening up the "Image App" library, which wouldn’t require any immediate changes to the cameras at all.

Conclusion

This is deliberately wide-ranging, and I acknowledge that some of it may be a bit contentious. If there are good reasons why some of what I’ve proposed wouldn’t work, then let me know. I’m also aware that not everyone will want everything I’m suggesting, but I’m trying to establish the idea of a more flexible approach which supports many working styles. There might well also be some discussion on priorities. Let’s have it. Let me know what you think.

Posted in Photography | Leave a comment

Platform Flexibility – It’s Alive!

The last post, written largely back in November and published just before Christmas suggested that camera manufacturers should focus on opening up their products as development platforms, much as has happened with mobile phones. While I can’t yet report on this happening for cameras, I now have direct experience of exactly this approach in another consumer electronics area.

I decided to replace a large picture frame in my office with a electronic display, on which I could see a rolling presentation of my own images. This is not a new idea, but decreasing prices and improving specs brought into my budget the option of a 40"+ 4K TV, which on the experience of our main TV should be an excellent solution.

New Year’s Eve brought a trip to Richer Sounds in Guildford. As usual the staff were very helpful and we quickly narrowed down the options to equivalent models from Panasonic or Sony. The Panasonic option was essentially just a smaller version of our main TV, but the colours were slightly "off" and we preferred the picture quality of the Sony. The Panasonic’s slideshow application is OK, but limited, but the Sony’s built-app looked downright crude. It looked like a difficult choice, but then I realised that the Sony operating system is something called "AndroidTV" with Google Play support, and promised the option of a more open platform, maybe even development myself. Sold!

In practice, it’s exactly as I expected. The basic hardware is good, but the Sony’s default applications beyond the core TV are a bit crude. However a bit of browsing on Google Play revealed a couple of options, and I eventually settled on Kodi, a good open-source media player, which does about 90% of what I want for the slideshow. Getting it running was a bit fiddly, not least because a key picture-handling setting has to be set by uploading a small XML file rather than via the app’s UI, but after only a bit of juggling it’s now running well and doing most of what I want.

Beyond that, I can either develop an add-on for Kodi, or a native application for AndroidTV. However as the existing developer community has provided a 90% solution, I’m not in a great hurry.

I call that a result for platform vs product…

Posted in Agile & Architecture, Android, Code & Development, Photography, Thoughts on the World | Leave a comment

Do We Want Product Development, or Platform Flexibility?

There’s been a bit of noise recently in the photography blogosphere relating to how easy it is to make changes to camera software, and why, as a result, it feels like camera manufacturers are flat out not interested in the feature ideas of their professional and more capable enthusiast users. It probably started with this article by Ming Thein, and this rebuttal by Kirk Tuck, followed by this one  and this one by Andrew Molitor.

The problem is that my "colleagues" (I’m not quite sure what the correct collective term is here) are wrong. For different reasons. They are all thinking of the camera as a unitary product, and none of them (even Molitor, who claims to have some experience as a system architect) are thinking as they should, of the camera as a platform.

OK, one at a time, please…

There are a lot of good ideas in Ming Thein’s article. A lot of his suggestions to improve current mirrorless cameras are good ones with which I agree. The trouble is that he is trying to design "Ming Thein’s perfect camera", and I suspect that it wouldn’t be mine. For a start it would end up far too heavy, too expensive and with too many knobs!

Kirk Tuck gets, this, and his article is a sensible exploration of trade-offs and how one photographer’s ideal may be another’s nightmare. However he paints a picture of flat-lining development which is very concerning, because there are some significant deficiencies in current mainstream cameras which it would be great to address.

Andrew Molitor then picks up this strand, and tries to explain why all camera feature development is difficult, and prohibitively expensive, and why Expose to the Right (ETTR) is especially difficult. Set aside that referring to Michael Reichmann as "a pundit" is unkind and a considerable underestimation of that eminent photographer’s capabilities, there are several fallacies in Molitor’s articles. Firstly, it just would not be as difficult as claimed to implement ETTR metering, or any variant of it. It’s just another metering calculation. If you have a camera with some form of live histogram or overexposure warning, then you can already operate this semi-manually, tweaking down the exposure compensation until the level of clipping is what you want. If you can do it via a predictable process, then that enormously powerful computer you call a digital camera can easily be made to replicate the same quickly and efficiently. That’s what the metering system does. It’s even quite likely that the engineers have already done something similar, but hidden it. (Hint: if you have a scene mode called something like "candle-lit interior", you’re almost there…)

I suspect the calculations of grossed-up cost are also fallacious. If that were the case, in a market which manages US sales of only a few tens of thousands of mirrorless cameras per year (for example), we would never get any new features at all. The twin realities are that by combining multiple features into the normal streams of product or major release development, many of the extra costs are amortised, but we also know that the big Japanese electronics companies apply different accounting standards to development of their flagship products. If Molitor’s argument was correct, we would not see features in each new camera such as a scene mode for  "baby’s bottom on pink rug" (OK, I made that one up :)) or in-camera HDR, and things like that don’t seem to be a problem. I simply cannot believe that "baby’s bottom on pink rug" will generate millions of extra dollars revenue, compared with a "control highlight clipping" advanced metering mode, which would be widely celebrated by almost all equipment reviewers and advanced users.

So assuming that I’m right, and on-going feature development is both feasible and desirable, where does that leave us?

Ming Thein is not alone in expressing disappointment with the provision of improved features focused for the advanced photographer, and I agree with him that the slow progress is really very annoying. In my most recent review, I identified several relatively simple features which would be of significant value to the advanced photographer, and which could easily be implemented in the software of any good mirrorless camera without hardware changes, including:

  1. Expose to the right or other "automatically control highlight clipping" metering
  2. Optimisation for RAW Capture (e.g. histogram from RAW, not JPG)
  3. Proper RAW-based support for HDR, panoramas, focus stacking and other multishot techniques
  4. Focal distance read-out and hyperfocal focus
  5. Note taking and other content enrichment

All of these have been identified requirements/opportunities since the early era of digital photography. Many of them are successfully implemented in a few, perhaps more unusual models. For example the Phase One cameras implement a lot of the focus-related features, the Olympus OM-D E5-II does a form of image stacking for resolution enhancement, and Panasonic have just introduced a very clever implementation of focus bracketing in the GX8 based on a short 4K burst. However by and large the mainstream manufacturers have not made any significant progress towards them.  Even if Molitor’s analysis is correct, and this is all much more difficult than I expect (despite my strong software development experience) you would think that over time there would be at least some perhaps limited visible progress, but no. If the concepts were really "on the product backlog" (to use the iterative development term), then some would by now have "made the cut", but instead we get yet more features for registering babies’ faces…

My guess is that some combination of the following is going on:

  • The "advanced photographer" market is relatively small, and quite saturated. Camera manufacturers are therefore trying to make their mid-range products attractive to users who would previously have bought a cheaper device, and who may well consider just using a phone as an option. To do this, the device needs to offer lots of "ease of use" features.
  • Marketing and product management groups are focused on the output of "focus groups", which inevitably generate lowest-common denominator requirements which look a lot like current capabilities.
  • Manufacturers are fixated on a particular set of use cases and can’t conceive that anyone would use their products in a different way.

The trouble is that this leaves the more experienced photographers very frustrated. The answer is flexibility. By all means offer an in-camera, JPG-only HDR for the novice user, but don’t fob me off with it – offer me flexible RAW-based multishot support as well. Re-assignable buttons are a good step in the right direction, but they are not where flexibility begins and ends. The challenge, of course, is to find a way to provide this within fixed product cycles and limited budgets.

I think the answer lies with software architecture, and in particular how we view the digital camera. It’s time for us all, manufacturers and advanced users alike, to stop thinking of the camera as a "product", and start thinking of it as a "platform", for more open development. In this model the manufacturer still sells the hardware, complete with basic functionality. Others extend the platform, with "add-ins" or "apps", which exploit the hardware by providing new ways to drive and exploit its capabilities.

We’ve been here before. In the early noughties, mobile phone hardware had evolved beyond all recognition (my first mobile phone was a Vodafone prototype which filled one seat and the boot of my Golf GTI, and needed a six-foot whip antenna!) However, you bought your phone from Nokia, for example, and it did what it did. If you didn’t like the contact management functionality, you were stuck with it.

Then Microsoft, followed more visibly by Apple and eventually Google, broke this model, by delivering a platform, a device which made phone calls, sure, but which also supported a development ecosystem so that some people could develop "apps", and others could install and use those which met their needs. Contact management functionality is now limited only by the imagination of the developer community. Despite my criticism of some early attempts, the model is now pretty much universal, and I don’t think I could go back to a model where my phone was a locked-down, single-purpose device.

The digital camera needs to go the same way, and quickly before it is over-run by the phone coming at the same challenge from the other side. Camera manufacturers need to stop thinking about "what other features should we develop for the next camera", and instead direct themselves to two questions, one familiar and one not. The familiar one is, of course, "how can we make the hardware even better"? The unfamiliar one is "how can we open up this platform so that developers can exploit it, and deliver all that stuff the advanced users keep going on about"?

Ironically, for many manufacturers many of the concepts are in place, just not joined up. The big manufacturers all offer open lens mounts, so that anyone can develop lenses for their bodies. In the case of Panasonic, Olympus and the other micro-four thirds partners it’s even an open multi-party standard. Panasonic certainly now deliver "platform" televisions with the concept of third party apps. There’s a healthy community of "hackers" developing modified firmware for Canon and Panasonic cameras, albeit at arms length from and with a slightly ambivalent relationship to the manufacturers. I’m sure many of those would very much prefer to be working as partners, within an open development model.

So what should such a "platform for extensibility" look like? Assuming we have a high-end mirrorless camera (something broadly equivalent to a Panasonic GX8) to work with as base platform, here are some ideas:

  1. A software development kit, API and "app store" or similar for the development and delivery of in-camera "apps". For example, it should be possible to develop an ETTR metering module, which the user can choose as an optional metering mode (instead of standard matrix metering). This would be activated in place of the standard metering routine, take in current exposure, and return required exposure settings and perhaps some correction metadata. Obviously the manufacturer would have to make sure that any such module returned "safe" values, but in a mirrorless camera it should be very easy to check that the exposure settings are "reasonable" and revert to a default if not. Other add-ins could tap into events such as the completion of an exposure, or could activate functions such as setting focal distance. The API should either be development language-agnostic, or should support a well-known language such as Java, C++ or VB. That would also make it easier to develop an IDE (exploiting Visual Studio or Eclipse as a base), emulators and the like. There’s no reason why the camera needs an "open" operating system.
  2. An SDK for phone apps. This might be an even easier starting point, albeit with limitations. Currently manufacturers such as Panasonic provide some extended functions (e.g. geotagging) via a companion app for the user’s phone, but these apps are "closed", and if they don’t do what you want, that’s an end of it. It would be very easy for these manufacturers to open up this API, by providing libraries which other developers can access. My note taking concept could easily be delivered this way. The beauty of this approach is that it has few or no security issues for the camera, and the application management infrastructure is delivered by Google, Apple and Microsoft.
  3. An open way to share, extend and move metadata. Panasonic support some content enrichment, but in an absolutely nonsensical way, as those features only work for JPEG files. What Panasonic appear to be doing is writing to the JPEG EXIF data, but not even copying to the RAW files. The right solution is support for XMP companion files. These can then accompany the RAW file through the development process, being progressively enhanced by different tools, and relevant data will be permanently written to the output JPEG. This doesn’t have to be restricted to static, human-readable information. If, for example, the ETTR metering module can record the difference between its exposure and the one set by the default matrix method, then this can be used by the RAW processing to automatically "normalise" back to standard exposure during processing. XMP files have the great advantages that they are already an open standard, designed to be extensible and shared between multiple applications, and it’s pretty trivial to write code to manipulate them, so this route would be much better than opening up the proprietary EXIF metadata structures.
  4. A controllable camera. What I mean by this is that the features of the camera which might be within the scope of the new "apps" must be set via buttons, menus and "continuous" controls (e.g. wheels with no specific set positions), so that they can be over-ridden or adjusted by software. They must not be set by fixed manual switches, which may or may not be set where the software requires. The Nikon DF or the Fuji XT1 may suit the working style of some photographers – that’s fine – but they are unsuited to the more flexible software environment I’m envisaging. While I prefer the ergonomics of "soft" controls, in this instance they are also a solution which promotes flexibility, which is what we’re seeking to achieve here.

This doesn’t have to be done in one fell swoop, and it might not be achieved (or even appropriate) 100% for every camera. That’s fine. Panasonic, for example, could make a great start by opening up the "Image App" library, which wouldn’t require any immediate changes to the cameras at all.

So how about it?

Posted in Agile & Architecture, Code & Development, Photography, Thoughts on the World | Leave a comment

A Surprisingly Tricky Subject

Stitched panorama of stitched panorama at the enttrance to the Rinpung Dzong
Camera: Panasonic DMC-GX8 | Date: 13-11-2015 11:21 | Resolution: 1920 x 1440 | ISO: 1600 | Exp. bias: 0 EV | Exp. Time: 1/13s | Aperture: 5.6 | Focal Length: 12.0mm (~24.0mm) | Lens: LUMIX G VARIO 12-35/F2.8

This really shouldn’t difficult. The image above is from the entrance to the Rinpung Dzong, in Paro. It’s a series of pictures of Buddhist deities which have been painted on bits of cloth, glued to the wall, and joined at the seams. Yes, it’s a stitched panorama. So why was it so difficult to make a photographic stitched panorama of it?

I set the camera to appropriate manual settings (to make sure that exposure was constant), faced each panel in turn, and when no-one was in shot took a picture. I then developed the JPEGs with exactly the same settings in Capture One. There was good overlap between the images, and as by definition it’s a series of images with a visible seam it ought to be straightforward to stitch images back together.

There seem to be two main challenges. Firstly as far as I can see all automatic stitching software assumes that the camera is roughly static, whereas I was shooting in a long thin tunnel, and moved the camera to face each subject. This is a well-established shooting technique, but seems to have minimal software support. Second, despite the manual exposure the resultant images vary significantly in brightness, and it looks like the camera was doing some measure of adjustment for the tricky lighting.

In the end I "went manual", importing the pictures as four layers in PhotoShop Elements, hand tweaking their position and geometry using free transforms, and then using the technique of painting the layer masks to choose exactly which elements of each image are visible in the final shot. The result isn’t perfect, but probably "good enough". In the meantime I’ve bitten the bullet and invested in some new stitching software which is supposed to cater for "moving camera" combinations, and we’ll see if it can make a better attempt.

View featured image in Album
Posted in Bhutan Travel Blog, Photography, Travel | Leave a comment

Bhutan: What Technology Worked, and What Didn’t

"Willow Pattern" - view from the Dolchula Pass cafe, with the infrared Panasonic GF3
Camera: Panasonic DMC-GF3 | Date: 17-11-2015 10:24 | Resolution: 2612 x 3918 | ISO: 160 | Exp. bias: -33/100 EV | Exp. Time: 1/400s | Aperture: 6.3 | Focal Length: 14.0mm | Location: Dochu La Pass (3150m) | State/Province: Punakha | See map | Lens: LUMIX G VARIO PZ 14-42/F3.5-5.6

Bhutan isn’t especially demanding on equipment. If your style of photography is similar to mine you will need a wide range of focal lengths, from ultra-wide (for when there’s limited space in front of a large building) to long telephoto (for inspecting details of the landscape). Outside light is usually very powerful, but inside you will rapidly need some combination of high ISO, fast lenses and a tripod. If anything the greatest challenge is the relatively harsh, direct lighting during the day (when the temples and Dzongs are open), and you will need to watch for flare and the effects of polarisation.

Dust can be a bit of a challenge, especially on or near the roads. It does tend to get everywhere, even inside filter pouches for example, but a filter will protect your lens, and other kit will just need a careful dust down. My excellent Hoya high-transmission 58mm polarising filter picked up a small scratch, but that’s a small price for providing both its optical services and protecting the lenses.

Shot Counts

The scores are in, and the shot counts are as follows:

  • Panasonic GX8: Almost exactly 3,000 shots. Quite a lot of those are for "multi shot" images, including 3D for the first time this year
  • Panasonic GX7: About 100 shots, plus video of "culture night"
  • Sony RX100 mk IV: About 364 stills, plus quite a few short video clips

Overall the totals are very similar to Morocco, albeit with a different camera mix. It looks like I’ll have about the normal 50% discard count, and end up with around 100-200 images which I want to show people, which is fine.

Panasonic Cameras

The Panasonic cameras have worked well. The GX8 is fast and produces great image quality. Its viewfinder is large and bright (although I have to acknowledge that the Fuji XT1 is even nicer), but does seem to be more sensitive to white balance changes than previous models. This means that you may see a bit of a red or brown cast on the live image in some cases, which doesn’t affect the captured image but can be slightly off-putting. It wouldn’t surprise me if this attracts a firmware change at some point.

Handling of the GX8 is good, but the viewfinder and controls are just different enough from the GX7 that you can’t just leave a different lens on the older body and switch quickly back and forth between them.

Even though it packs a much bigger battery than the GX7 battery life is still only moderate. I never used more than 3 per day, but that could have increased if we had done significant action shooting, so my purchase of a total of 4 was probably justified.

Bags

The National Geographic Africa Medium Backpack is an excellent device for carrying equipment between locations. It meets the most miserly airline carry-on restrictions, but easily swallowed my 15“ laptop, tablet, 4 Panasonic bodies, 8 lenses including the 100-300mm, a small flash and various odds and ends.

Unfortunately it’s pretty bloody useless as a working bag on location. The only way to extract kit is to take it off completely and lay it flat on the ground, getting it and then you filthy, and the whole process is very fiddly. Luckily I had allowed for this and fitted one of my Lowepro Nova shoulder bags (the 180 AW) into my hold luggage. This has room for the main body and lenses, the infrared GF3 and bits & pieces with room over for a small water bottle.

Sony RX100 Mk IV

First impressions of the Sony RX100 mark IV are excellent. It is fast, with almost DSLR-like autofocus, and the image quality is superb – more or less a match for my Panasonic cameras at moderate ISOs. My camera has had a "baptism of fire" being used mainly to try and get grab shots from a moving bus, so maybe not exactly a fair test, but has delivered decent results albeit with some misses. Although the EVF is small, and does seem to need quite regular re-adjustment against my glasses, it is clear and perfectly usable in a way which wasn’t true of the Panasonic GM5 I tried.

The handling is a bit fiddly, but I wouldn’t subscribe to some of the complaints I have read in internet interviews. However it is far to easy to accidentally change shooting mode, and the other problem I have had is accidentally pressing the power button instead of the shutter, and switching the camera off at just the wrong moment. If you have the camera at arms length in a tricky shooting position, the feel of the two controls is just not different enough.

Battery life is limited, although no worse than other cameras with a similar sized battery (like the Canon S120). Sony’s insistence on in-camera charging is annoying, and I’ve now purchased a third party charger and spare batteries from Germany.

I tried carrying my camera just in my trouser pocket, where it fits well. However it rapidly picked up a number of small scratches on the rear screen. Nothing fundamental, but a real annoyance on a brand new, expensive little camera. This seems to be a vulnerability of Sony cameras, with one of the other members of the group suffering a similar problem with his A7. I’m hoping that I can fit a screen protector to restore the original appearance, and am now carrying the camera in a small cloth pouch which came with a Metz flashgun.

Other Notes

One other annoyance is that I changed my phone earlier this year from a Samsung Galaxy Note 2 to a Note 3. The older Notes had very good GPS, getting accurate fixes quickly in most conditions. The Note 3 has a useless GPS, taking time to get a good fix even at the top of a mountain under cloudless skies! As a result my GPS track has a couple of annoying gaps in it, and I’ve had to do a lot of manual work and fix it, which has never been necessary on previous trips.

At the same time, my Note 10.1" tablet seems to have suddenly lost most of its battery capacity, and is only good for about 4-5 hours, not long enough for some of the flights on this trip. I am seriously thinking of a shift in loyalties.

 

Overall a few annoyances, but I managed to travel quite light, and unlike some trips there were no major problems. That’s a refreshing change.

View featured image in Album
Posted in Bhutan Travel Blog, Photography, Travel | Leave a comment

Last Light

Last light over the Haa Valley, Bhutan
Camera: Panasonic DMC-GX8 | Date: 14-11-2015 17:04 | Resolution: 1920 x 1440 | ISO: 400 | Exp. bias: 0 EV | Exp. Time: 1/40s | Aperture: 5.6 | Focal Length: 12.0mm (~24.0mm) | Lens: LUMIX G VARIO 12-35/F2.8

Bhutan: What Worked and What Didn’t

Sorry it’s been quiet for a couple of weeks. Inevitably there’s catching up to do on the return from a trip, plus I’ve had a couple of practical challenges before I could start properly sorting out the photos from the trip. However things are working OK now.

As always at the end of these trips, I’ve prepared a couple of posts with general observations on the trip, in the hope that it may be of assistance to someone planning a similar visit. To keep things manageable, this post focuses on the trip as a whole, and the following post focuses on photography and equipment matters. There will be a final post reflecting on my observations of Bhutan, the country and people.

 

On a positive note, the people everywhere were friendly, welcoming and most were happy to pose for the camera, without expectation of more than a "thank you". In reality most away from direct tourist contact have limited English, although that will change, but they all understand basic pleasantries well enough.

Bhutan is not an expensive location once you’re there and the $250 per day has been paid to the tour operator. My additional costs (mainly tips, T-shirts and beer) probably came to not much more than £200. Western money goes a long way in a country with a 1p note! There are plenty of stalls and shops selling handicrafts, but they understand the value of a "no thank you", and there are no street hawkers or other more annoying channels. There’s no need to haggle, and transactions are very straightforward with no nasty catches, but you do need to be aware of prices which can vary substantially between locations (beer varying between about £1 and £3, for example).

Travel in Bhutan is slow. 20kph is a very good speed in a bus, 15kph is a more sensible basis for estimating. One suspects that the current over-ambitious programme of simultaneously trying to widen almost all the roads is doomed to failure, or at least to very late delivery, so things will probably get worse before they improve.

In hindsight, the trip to Bumthang cost us two long days of uncomfortable travel for not much benefit, and I think most participants on our trip will be advising Light and Land to omit if from future itineraries. If your itinerary includes statements like "a full day of travel", question whether that is the best use of time and endurance, or whether further exploration of the nearer areas will be of more benefit.

Be wary of overcrowding on the transport. The standard tour buses are not terribly comfortable, and have a lower real capacity in practice than you might expect. They have a typical nominal seating capacity of 16-17 plus the driver and guide, but 4 seats are over the wheel arches with zero legroom, the back seat bounces so much that it suits only the hardiest, and there’s zero internal baggage space (suitcases are typically transported between hotels in an independent vehicle). Assume a maximum of 12 usable seats for longer journeys, in addition to the driver and guide.

Food is essentially Indo-Chinese buffets, mainly vegetarian with some chicken, although in the east you might also get a pork or beef dish. (I wrote most of this post at Doha airport, and I have never seen so many people queueing for a hamburger, in a Muslim country!… :))

The primary calorie source is uniformly boiled rice, although there is usually a secondary form such as potatoes, pasta or bread. Those catering more directly for tourists try and keep the main dishes fairly bland, with the chilli and garlic in separate dishes, but you can be caught out. One of the nastiest surprises of the trip for me was something called "cauliflower cheese", but about the strength and flavour of industrial defoliant!

The information I received about the weather was, essentially, lies. We had wonderful weather, dipping to around freezing most nights but between high teens and high twenties once the sun came up every day. We felt a couple of drops of rain once, and the mornings in Punakha started with a bit of mist, but otherwise we had zero precipitation. I had to carry a long-sleeved top or jacket for religious observation at the temples and Dzongs, but otherwise I could have operated entirely in T-shirts on all but two days. The waterproof, weatherproof tops, trousers, gloves etc. were completely unused.

Were we unusually lucky? It’s difficult to say, as this was the first time in Bhutan for all westerners in our party. However the fact that every other rooftop is covered with drying chillies, and the winter firewood is stacked in the open suggests that the Bhutanese are not expecting storms either.

This was my second trip (and the first for seven years) with Phil Malpas and Clive Minnitt of Light and Land. They continue to be great tour leaders: sensitive to the needs of their clients, well organised, and great fun to be with. As usual Light and Land partnered with a local tour provider (essential in Bhutan). Etho Metho provided a very good, supportive and knowledgeable guide in Yeshi, and I continue to be amazed by the accuracy and endurance of Chorten’s driving. Overall, a highly effective team.

So as a trip it worked well. Next: technology!

View featured image in Album
Posted in Bhutan Travel Blog, Photography, Travel | Leave a comment

The World’s Worst Panorama – 2015

The Light and Land Bhutan 2015 Tour Group
Resolution: 13758 x 1657

It’s become a bit of a tradition that on the last night of these trips I try and take a panoramic picture of the group, usually under lighting, compositional and alcohol level challenges which would try a saint!

I’m quite pleased with this year’s which was taken around a long, thin table with the Sony RX100.

Therefore, I proudly present the Light and Land 2015 Bhutan tour group. From left to right: Chorten (driver), Yishi (guide), Roger (Australian, but we won’t hold that against him), Annie, Charlotte (German, and the bus’s volunteer stewardess), John (AKA “Lord Blandford” 🙂 ), Liam (from Ireland), Yours Truly, Greg (another Aussie), Julia, Peter, Jeanette, Davina, Phil Malpas (co-leader) and Clive Minnitt (co-leader).

View featured image in Album
Posted in Bhutan Travel Blog, Travel | Leave a comment

Return to Kathmandu

Monkey on the Golden Shrine, Kathmandu
Camera: Panasonic DMC-GX8 | Date: 25-11-2015 15:08 | Resolution: 4856 x 3237 | ISO: 200 | Exp. bias: 0 EV | Exp. Time: 1/500s | Aperture: 6.3 | Focal Length: 45.0mm | Lens: LUMIX G VARIO PZ 45-175/F4.0-5.6

We have an early start to our return journey, bidding farewell to Bhutan in the dark. The flight back to Kathmandu is eventless, except for a slight argument about which mountain is Everest! Between somewhat poorer viewing conditions, an unfamiliar angle and a slightly ambiguous announcement by the captain we’re not sure which is which. I’m glad I got my shot on the way out.

In contrast to the rugby scrum of arrival at the start of the trip, we have Kathmandu airport almost to ourselves and formalities are discharged very quickly. The calm before the storm.

Kathmandu is a real shock to the system after the calm and emptiness of Bhutan. It’s a manic, buzzing place, and that’s in current depressed conditions. Not only are they are trying to recover from the earthquakes in April and May, they are also battling a blockade on the Indian border which is starving them of fuel and really depressing the economy. We see several long queues for petrol, and they have taken to riding on the roofs of buses, because there isn’t enough fuel to run all the normal services. There’s a pall of smoke over the city because they’ve had to start burning wood for heating and cooking after not normally doing so for years. The issue is an internal wrangle over the new constitution, which the Indian-facing group in the south think reduces their power, but it’s killing the country’s economy, blocking large amounts of foreign aid targeted at the earthquake victims, and could easily lead the Nepali government into alliance with China, extending that country’s influence south of the Himalayan backbone. None of this is good…

After a gentle morning in our hotel, we take a short guided tour after lunch. The tour takes in the holy area at the top of the hill where the main shrines are, but which is now also heavily populated with people trying to sell you handicrafts (think Montmarte, but times about 5). We then visit the squares in the centre of town where various old temple and palace buildings were very badly damaged in the earthquake.

Just a couple of months ago I read in National Geographic about the Nepali Hindu tradition of the "Kumari". Essentially this sect select a pretty young girl of about 6 and present her as a living deity, until the point where she enters puberty when she retires and another one takes over. We reach the House of the Kumari at the right time and are treated to a short view of regal-looking young lady looking down from an upstairs window. The NG article explained how it’s regarded as a great honour and selection is quite competitive, but the girls sometimes find it hard going returning to normal life in their teens. It’s a bit of a weird practice, but it was interesting to see something I’d only just read about.

Even in the current conditions Kathmandu is a noisy, manic and dusty place, and I’m not sure how I would cope at peak activity. I’m glad that having come here we’ve seen a bit of the city, but I wouldn’t want to spend much time here or hurry back.

To settle my knees at the end of the day I run myself a bath. The only slight problem is that what is otherwise a very posh hotel has distinctly yellow tap-water. Oh well – I’m not going to drink it!

View featured image in Album
Posted in Bhutan Travel Blog, Travel | Leave a comment

Oh Well…

Self-explanatory
Camera: Panasonic DMC-GX8 | Date: 24-11-2015 09:56 | Resolution: 5085 x 3390 | ISO: 400 | Exp. bias: -66/100 EV | Exp. Time: 1/125s | Aperture: 9.0 | Focal Length: 23.0mm | Lens: LUMIX G VARIO 12-35/F2.8

You’d think that with tens of thousands of pounds worth of equipment, umpteen years of experience and an undying dedication to their art, 12 other photographers could take a nice picture of me. However, this was the handicraft of a passing Australian hiker who wasn’t even sure which button to press on my camera. Oh well…

View featured image in Album
Posted in Bhutan Travel Blog, Photography, Travel | Leave a comment

To The Tiger’s Nest

Paro Taktsang - The Tiger's Nest
Camera: Panasonic DMC-GX8 | Date: 24-11-2015 10:13 | Resolution: 4076 x 4076 | ISO: 400 | Exp. bias: -66/100 EV | Exp. Time: 1/160s | Aperture: 9.0 | Focal Length: 12.0mm | Lens: LUMIX G VARIO 12-35/F2.8

Well I did it! This is Paro Taktsang, otherwise known as the Tiger’s Nest, a monastery founded in the 15th Century which sits on a cliff edge over 1000m above the floor of the Paro Valley. Apart from the obvious visual attractions, this particularly appealed to me as it’s one of the main inspirations for Ra’s Al Ghul’s lair in Batman Begins. I’ve stood where that was filmed (in Iceland, about 150′ above sea level and about 100 yards from the car park :)), and wanted to visit the "real thing".

The story is that the monk Padmasmabhava changed one of his concubines (yes, I know…) into a tigress and flew up to the top of the cliff, and after they had each meditated for three months they started building the first temple. All I can say is that a flying tigress would probably be easier…

The walk up to the Tiger’s Nest is hard work, but really worth it. Horses take you up about 400m, where there’s a convenient cafe at a viewpoint. You then have to walk up another 500m to the top viewpoint, down steps carved into the cliffside about 200m, across a tiny bridge and up the same again on the other side to reach the monastery. Going back is the reverse, so there’s another 200m ascent before you reach the high point for the last time. Think of doing Snowdon one and a half times, but starting at twice the height of Ben Nevis!

My knees hold up reasonably well, and afterwards, by the time I’ve walked all the way down (no help from the horses in that direction), our guides have organised another excellent al fresco meal under the pine trees. Very pleasant.

In the afternoon the only thing we’re good for is a bit of shopping in Paro town centre, and another visit to it’s nice little coffee and cake shop. The "last supper" is uproarious, and emphasises what a great group this has been. Up early in the morning for the flight back to Kathmandu.

View featured image in Album
Posted in Bhutan Travel Blog, Travel | Leave a comment

The Return to Paro

Long exposure of river below Paro, Bhutan
Camera: Panasonic DMC-GX8 | Date: 23-11-2015 16:03 | Resolution: 5094 x 3820 | ISO: 100 | Exp. bias: -33/100 EV | Exp. Time: 0.7692308s | Aperture: 13.0 | Focal Length: 16.0mm | Lens: LUMIX G VARIO 12-35/F2.8

Another fairly early start. I’m feeling a bit wobbly, as are some of the others, but we put this down to maybe a bit more beer than ideal last night, as a form of anaesthetic after the long drive.

We have another stop at the Drochula Pass, which is definitely one of my favourite locations of the trip. This time is in bright sunshine, and we were able to include Bhutan’s highest mountains into our compositions, rather than the swirling mists of the outward stop.

I’ve been a bit challenged on food today. Breakfast was a couple of pancakes with honey, and then lunch in Thimpu was a bit of a disappointment – very spicy and nothing I could eat apart from some more bread-like stuff (green…). Dinner at the Tiger’s Nest Resort is a bit more edible, even if the main protein is Tofu! The upside is my trousers are feeling quite loose, so hopefully the trip has had the right effect on  my weight!

We do the horse ride and hike to the Tiger’s Nest in the morning. Fingers crossed.

View featured image in Album
Posted in Bhutan Travel Blog, Travel | Leave a comment

Just So You Understand What I’m On About

Road conditions, Bhutan
Camera: SONY DSC-RX100M4 | Date: 22-11-2015 12:36 | Resolution: 3648 x 4864 | ISO: 125 | Exp. bias: 0 EV | Exp. Time: 1/320s | Aperture: 5.6 | Focal Length: 8.8mm

Typical roadside shot. Note the vehicle coming the other way… I’m full of admiration for our driver, Chorten, who has managed long drives in very difficult conditions, safely, accurately and as smoothly as the roads and vehicle allow!

View featured image in Album
Posted in Bhutan Travel Blog, Travel | Leave a comment