August 8, 2013
Someone asked us the other day whether it was safe to make a commercial production with Magic Lantern software running on a Canon EOS 5D mk III. There are several answers to this, and it’s by no means certain that any of them are “yes”. In order to understand why, it’s a good idea to look at this question in the light of two completely different scenarios
First of all I want to say that I’m a huge admirer of the work that Magic Lantern does. None of what follows is a criticism of them or their work. It is more a reflection of what it means to use a product in a professional context, and how to asses the risk of using software that does not have the same history of testing as professional equipment from a large Japanese manufacturer.
Design and Production
First, let’s look at how a major Japanese manufacturer designs and makes a product.
When a new camera comes to market from one of the major players, it’s rarely the result of a back-of-an-envelope idea. What’s more likely is that the product has been in planning for more than a year, and that it’s based on a perceived gap in the marketplace. It will be developed in a way that minimises the need for additional tools and technology, while still giving the new device a competitive advantage.
It’s a complex process, that’s well tuned. And it’s also why you don’t often get big surprises from big companies – but what you do get is a product that is generally delivered on time, and which is absolutely rock solid. Which is what you want if your business and your reputation depend on it.
Most of all, these products are tested to within an inch of their lives. There’s almost no chance of something slipping out with a serious bug. In fact, this happens so rarely, that when it does, it’s big news. Even though modern cameras are largely software-defined devices, buying a camera from a big Japanese manufacturer is as close as you can get these days to buying a “thing” in the old fashioned sense.
Reliability of Magic Lantern
Now, let’s look at it from the Magic Lantern angle (and this isn’t just about ML: its about anyone who “hacks” into a product to gain functionality).
First of all, let’s get rid of the idea that because the ML software is running on Canon’s hardware it must be reliable, because the moment you install a single byte of “alien” code on a third-party’s product, all the testing is completely invalidated. In a sense software like ML’s would be treated by the original manufacturer as one giant bug.
You can expect absolutely no support from Canon if you’re running other people’s software, and no sympathy either. And you can understand why: not only do Canon not have any control over any foreign software installed on their cameras, but this represents a disruptive attack on their business model as well. Remember how we said that each new product is planned and fitted into the optimum place in the manufacturer’s product hierarchy? Well, running software that means a camera costing a few thousand dollars can challenge another one in your range that costs five times as much is a situation that’s not likely to be welcomed with open arms.