Industry of Change: Linux Storms Hollywood
Before the summer of 2001, Linux supporters often pointed to any of a number of single-company deployments as a measure of success for the fledgling operating system. There was Burlington Northern, which committed in February 1999 to deploy Linux in 250 US stores. That was followed by Japan's Lawson, which struck a deal with IBM to supply that convenience store retailer with 15,000 IBM Linux-based eServers running on Red Hat software. Ford announced a plan where they would deploy 33,000 Linux desktops. These were big wins for the open-source faithful. But they were corporate waves in a sea of change. What Linux needed was a tidal wave--an industry-wide migration--to signal that the penguin had come of age.
Enter the visual effects industry, the collection of studios that produce special effects, or VFX in industry parlance, for movies and animated tales like Toy Story and Shrek. This is an industry ripe for change, an industry struggling to shake the bondage of single-vendor solutions and high-priced specialized hardware. It's also an industry that tested the waters of Windows and found it flowing in the wrong direction.
This isn't a story about one or two studios adopting Linux as servers in their renderfarms, those back rooms full of servers used to produce the individual sets of frames used in a movie. We're talking about the entire industry--from Rhythm & Hues to Pixar, from Digital Domain to DreamWorks. DreamWorks-PDI had over 2,000 Linux-based CPUs on-line by the summer of 2001. Their summer blockbuster Shrek was rendered on 1,000+ mostly Linux machines (see GFX: "DreamWorks Feature Linux and Animation", August 2001 issue of LJ). Pixar has only deployed 15 stations in production and 25 in software development, but VP of Technology Darwin Peachey says the studio is on the verge of a major purchase and deployment of desktops to replace their current SGI desktops. Even Industrial Light & Magic is considering a major switch to the penguin OS.
And this isn't the infrastructure saying they will support Linux, like IBM or Compaq or HP announcing they will support the OS--it's the end users demanding it from suppliers of applications and hardware. Back in June 2001, Ray Feeney, technology committee chair of the Visual Effects Society said, "For the high-end part of movie making, 80-90% will be Linux-based inside of 18 months. Everything is going Linux." This sort of mass migration has never happened before in the Linux world. The tidal wave is here.
Understanding how this wave was formed requires some understanding of the industry itself. Effects studios talk about movie production as pipelines, the set of processes required to create effects and integrate them into a movie. A pipeline has two distinct sides to it: the graphic workstation and the renderfarm. The latter is like any other room full of servers, crunching away on any given problem. In this case, the problem is producing the 3-D imagery from models fed to the farm by the many artists working for the studio. The artists work on the other end of the pipeline, on the graphic workstations.
The first ripple in this tidal surge came with the use of Linux by Digital Domain to render frames for the movie Titanic. Involved in this film was well-known Linux graphics guru Daryll Strauss, who covered this story for Linux Journal back in February 1998. At the time, Daryll used a room full of Alpha-based Linux systems networked together to render some of the water scenes used in the movie. In this early stage, Linux still was used in its traditional role as a back-end server. The front-end graphics workstations were still primarily the domain of SGI IRIX systems.
In 1999, SideFX software ported their very popular (and very expensive) high-end 3-D modeling and animation package, Houdini, to Linux. Linux Journal again covered the story, this time in an interview I did with SideFX's Director of Research and Development, Paul Salvini. Houdini is an artist's tool used to create the models that renderfarms crunch on. At the time that Houdini was ported, Linux still had graphic-related limitations, such as a lack of support for hardware-accelerated OpenGL (a de facto industry standard for doing 3-D applications and games). This created a chicken-and-egg problem, according to Salvini. Doing a product like this for Linux required hardware acceleration to make it really viable, but hardware acceleration often requires applications in order to warrant drivers to be written." Drivers from video card makers weren't being written because there were no applications that needed them, and applications weren't being written because no drivers were available. SideFX sidestepped the issue by using software-accelerated OpenGL, a slower and problematic alternative that didn't require special video card drivers. Still, it was enough to entice the VFX industry toward Linux. It also provided motivation to graphics card vendors to provide both assistance to XFree86 and to begin work on their own proprietary drivers.
|September 2015 Issue of Linux Journal: HOW-TOs||Sep 01, 2015|
|September 2015 Video Preview||Sep 01, 2015|
|Using tshark to Watch and Inspect Network Traffic||Aug 31, 2015|
|Where's That Pesky Hidden Word?||Aug 28, 2015|
|A Project to Guarantee Better Security for Open-Source Projects||Aug 27, 2015|
|Concerning Containers' Connections: on Docker Networking||Aug 26, 2015|
- Optimization in GCC
- Using tshark to Watch and Inspect Network Traffic
- September 2015 Issue of Linux Journal: HOW-TOs
- Problems with Ubuntu's Software Center and How Canonical Plans to Fix Them
- Concerning Containers' Connections: on Docker Networking
- A Project to Guarantee Better Security for Open-Source Projects
- Firefox Security Exploit Targets Linux Users and Web Developers
- Where's That Pesky Hidden Word?
- My Network Go-Bag
- Doing Astronomy with Python