A Birthday For Pixar’s RenderMan Software

Pixar is celebrating 25 years of making movies using RenderMan software, but the technology dates back much further.

1 min read
A Birthday For Pixar’s RenderMan Software

RenderMan, the set of computer graphics tools behind much of today’s computer animation, is celebrating a birthday this year. RenderMan changed the animated movie industry, because it makes it far easier for computers to produce realistic images, not just boxes and angles. Evidence of its impact? The folks that produced 19 of the last 21 movies that won the Academy Award for Visual Effects used RenderMan technology.

Pixar is counting RenderMan’s age as 25; indeed, that’s when Pixar launched it as a product. But the lead architect on the design of the product, Pat Hanahan, wasn’t starting from scratch. The technology that made RenderMan work really dates back to 1973 when Ed Catmull, a student at the University of Utah, came up with the Z-buffer, the first algorithm that keeps track of the depth of every pixel on the screen. Z-buffer makes it possible for computers to generate complex images, and is now built into computers and video game machines. “I get zip for that,” Catmull told me when I interviewed him in 2001, “because at that time patenting wasn’t part of our thought processes.”

Catmull, now president of Walt Disney Animation Studios and Pixar Animation, isn’t the only computer scientist to contribute to RenderMan's DNA. When the Academy of Motion Picture Arts and Sciences Honored the technology with an Oscar in 2001, it recognized three: Catmull, Loren Carpenter (now chief scientist at Pixar) and Rob Cook (now retired). I described their individual paths to developing computer graphics technology that came together in RenderMan in IEEE Spectrum’s April 2001 article “And the Oscar Goes To…” (The trio did indeed get an Oscar for RenderMan. It was the very first Oscar ever given to developers of software.)

Follow me on Twitter @TeklaPerry

Image: Pixar


Correction made 10/7/13.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less