Language Selection

English French German Italian Portuguese Spanish

Intricate Tech Brings 'Madagascar' to Life

Filed under
Movies

The ability of animators to turn an imaginary world into reality for millions of movie-goers rests solidly on the shoulders of technological advances, said Jeffrey Katzenberg, the co-founder and CEO of the DreamWorks SKG studio.

At a recent media conference about "Madagascar," the latest animated movie from DreamWorks, which opens at theaters around the country on Friday, Katzenberg answered an eWEEK question about technological advances by saying, "If you can imagine it, then we can pretty much make it happen."

He pointed to how technology has revolutionized animated filmmaking since "Aladdin" was produced in the early 1990s, and how it now affects every aspect of the animation process.

As an example, he cited the fact that the color palette has expanded from four colors to 250 over the past 13 years, while the "Madagascar" landscape has 150,000 objects moving at once.
On the technical front, all of the technical work, production design, animation and rendering for "Madagascar" was done on a complex system of Hewlett-Packard hardware running Linux as well as its own proprietary operating system known as e-motion.

The movie has taken about four years to complete, which sounds like a long time, but when all of the stages and components are considered, it's not really long at all. Consider that every detail of every person, creature, element, plant and background has to be painstakingly coded and then stored in the huge database of the e-motion operating system.

Also, every movement made by the foliage, background, elements such water, and the characters, in this case all animals, had to appear realistic to the design of the movie, which has gone back and adopted the "stretch and squash" technique along with the not-quite-real approach of cartoons and animations of the past.

Every hair on every animal represents a line of computer code, with lead character Alex the Lion having 1.7 million hairs on his head. The design team also developed five different kinds of lemurs with 12 variations of hair type, or 60 possible combinations, for characters. This would have been impossible just a few years ago.

DreamWorks moved to the AMD Opteron processors during movie production, which was risky given the possibility of disruption, but this turned out not to be the case. "The transition to the AMD Opteron processors was made midway through production and was amazingly smooth," Gluckman said.

Asked what some of the main rendering challenges were, he said getting the diverse foliage and the fur of the lemurs to render was very problematic at first, using up way too much memory.

The solution? Create something that represented the volume of fur and the edge breakup that real fur would give, and that had shades like the fur itself, but which was not the actual fur. This solved the problem, which was helped by the fact that the AMD processors on the Proliant servers gave an immediate 35 percent increase in performance and speed.

The company's e-motion operating system, which has all been written internally and is proprietary software, is continually updated and expanded, both to plan for long-term needs as well as to meet the shorter-term technical needs of every movie.

When asked what they planned to do next, many of those who worked on Madagascar said, "Take a long vacation." But given that as one movie is completed another is already in development, there will not be much downtime.

Full Article.

More in Tux Machines

Security Leftovers

  • efail: Outdated Crypto Standards are to blame
    I have a lot of thoughts about the recently published efail vulnerability, so I thought I'd start to writeup some of them. I'd like to skip all the public outrage about the disclosure process for now, as I mainly wanted to get into the technical issues, explain what I think went wrong and how things can become more secure in the future. I read lots of wrong statements that "it's only the mail clients" and the underlying crypto standards are fine, so I'll start by explaining why I believe the OpenPGP and S/MIME standards are broken and why we still see these kinds of bugs in 2018. I plan to do a second writeup that will be titled "efail: HTML mails are to blame". I assume most will have heard of efail by now, but the quick version is this: By combining a weakness in cryptographic modes along with HTML emails a team of researchers was able to figure out a variety of ways in which mail clients can be tricked into exfiltrating the content of encrypted e-mails. Not all of the attack scenarios involve crypto, but those that do exploit a property of encryption modes that is called malleability. It means that under certain circumstances you can do controlled changes of the content of an encrypted message. [...] Properly using authenticated encryption modes can prevent a lot of problems. It's been a known issue in OpenPGP, but until know it wasn't pressing enough to fix it. The good news is that with minor modifications OpenPGP can still be used safely. And having a future OpenPGP standard with proper authenticated encryption is definitely possible. For S/MIME the situation is much more dire and it's probably best to just give up on it. It was never a good idea in the first place to have competing standards for e-mail encryption. For other crypto protocols there's a lesson to be learned as well: Stop using unauthenticated encryption modes. If anything efail should make that abundantly clear.
  • Comcast Leaked Customer Wi-Fi Logins in Plaintext, Change Your Passcode Now
    A Comcast Xfinity website was leaking Wi-Fi names and passwords, meaning now is a good time to change your Wi-Fi passcode. The site, intended to help new customers set up new routers, could easily be fooled into revealing the location of and password for any customer’s Wi-Fi network. A customer ID and a house or apartment number was all would-be attackers needed to get full access to your network, along with your full address.
  • Update Fedora Linux using terminal for latest software patches
  • Patch for New Spectre-Like CPU Bug Could Affect Your Performance
  • container_t versus svirt_lxc_net_t

today's howtos

Red Hat News

  • “Ultimate Private Cloud” Demo, Under The Hood!
    At the recent Red Hat Summit in San Francisco, and more recently the OpenStack Summit in Vancouver, the OpenStack engineering team worked on some interesting demos for the keynote talks. I’ve been directly involved with the deployment of Red Hat OpenShift Platform on bare metal using the Red Hat OpenStack Platform director deployment/management tool, integrated with openshift-ansible. I’ll give some details of this demo, the upstream TripleO features related to this work, and insight around the potential use-cases.
  • Discover the possibilities of hybrid cloud during a joint virtual event with Red Hat & Microsoft [Ed: [Ed: When Red Hat pus Microsoft executives at top positions inside Red Hat...]
  • Red Hat OpenStack Customer Survey 2018: containers, technical support top of mind
    In 2016, we surveyed our customer base on their use of OpenStack in production, getting a pulse-check on the top considerations, expectations, and benefits of a Red Hat OpenStack Platform deployment. With 2018 marking five years of Red Hat OpenStack Platform, we checked back in with our customers to see if their experiences or expectations of OpenStack have changed. Our survey found:
  • Red Hat CEO Jim Whitehurst On How He Plans To Win The Container Market
  • Juniper, Red Hat Tighten Integration to Fend Off VMware
    Juniper Networks and Red Hat have tightened their integration efforts in a move to help ease enterprise adoption of cloud-native platforms and bolster their own offerings against the likes of VMware and Cisco. The latest platform integration includes the Red Hat OpenStack Platform; Red Hat’s OpenShift Container Platform running as a platform-as-a-service (PaaS) on top of or next to the OpenStack platform depending on deployment architecture; and Juniper’s Contrail Enterprise Multi-Cloud platform running as the networking and security layer to unify those together. This integration is designed as a managed system to help deploy and run applications and services on any virtual machine (VM), container platform, and any cloud environment.
  • Red Hat OpenStack HCI Targets Telco Hybrid Cloud, 5G Deployments
    Red Hat today rolled out a hyperconverged infrastructure (HCI) platform based on OpenStack compute and Ceph storage. The new product targets service providers looking to deploy virtual network functions (VNFs) and 5G technologies on top of open source software. Launched at this week’s OpenStack Summit, the Red Hat Hyperconverged Infrastructure for Cloud combines Red Hat OpenStack Platform 13 and Red Hat Ceph Storage 3 into one product. Red Hat says it is the largest contributor to both open source projects.
  • Red Hat Hyperconverged Infrastructure for Cloud Bridges Datacenters and Edge Deployments
  • GSoC 2018: Week 1
    This time, I am working on improving the Fedora Community App with the Fedora project. It’s been a week since we started off our coding on may 14. The Fedora App is a central location for Fedora users and innovators to stay updated on The Fedora Project. News updates, social posts, Ask Fedora, as well as articles from Fedora Magazine are all held under this app.

Today in Techrights