Posts Tagged ‘Michael Bay’
Blackhat and the logic of director love
I know what I’m doing.
—Crockett in Miami Vice
Back in January, it occurred to me, almost at random, that I wanted to see Blackhat. As regular readers know, I don’t see a lot of movies these days, but the prospect of a new Michael Mann film—his first in six years—was just enticing enough to make me consider ducking out for a few hours while my in-laws were watching my daughter. At that point, Blackhat was already a notorious flop, and it had been slowly dying in theaters for a couple of weeks, but I still thought that I might be able to catch an afternoon screening. When I did a search for showtimes, though, I found that there weren’t any, and soon thereafter, I learned that Blackhat had suffered one of the greatest third-weekend theater drops in history, just behind the likes of Meet Dave and Jonah Hex. What does this mean? Before a film is released, it’s booked into a certain number of screens nationwide, and that number is contractually fixed for the first two weeks. On the third weekend, theater owners and distributors are free to yank the underperformers. A huge drop in screens simply means that nobody, anywhere, wanted to see this movie. And while I’m used to the idea that my tastes run a little weird, it struck me as significant that the first film in months that tempted me to pay for a ticket had been met with total indifference from everybody else in America.
Having finally caught up with Blackhat on video, I can see why. Basically, if you’re excited by the idea of a particular kind of Michael Mann movie, you’ll like it; if you want to see literally anything else, you won’t. For my own part, I ate it up, mostly because my expectations, for once, had been perfectly calibrated. It’s a mess, but a glorious one: a rich slice of the familiar Mann universe, soaked in neon, rendered in nearly translucent digital video, laden with jargon, punctuated by brutal and confusing violence, and populated with smart men and mostly useless women. The locations, not surprisingly, are fantastic, especially at night: Hong Kong, Los Angeles, Jakarta, Malaysia. (I was reminded of a great reader comment on The A.V. Club about the look of Miami Vice: “It was like someone built a set of Miami and then only filmed the back of it.”) There’s a lot of plot and some nifty ideas, much of it rendered so elliptically as to be all but incomprehensible. And I kind of adored it, enough to the point where I want to see it again. I can’t say it “works,” except in isolated stretches, but I admire its attempt to take the least cinematic material imaginable—with one scene after another code unspooling across computer screens—and stage it like a grungy version of Skyfall. And the fact that no other director alive could have made it, or even conceived of it, makes it more memorable than any number of conventionally tidy movies.
Years ago, in my review of Transformers: Dark of the Moon, I said: “[Michael] Bay is like one of those strange extinct animals that got caught in an evolutionary arms race until they became all horns, claws, or teeth…Bay is nothing but a massive eye.” Mann has undergone a similar refinement of purpose, but instead of huge, crystalline images, he’s obsessed by textures—visual, aural, and narrative. Digital video, with its ability to render portions of the frame in startling clarity while reducing the rest to a grainy smear, is his ideal format, and it mirrors his increasingly oblique style of storytelling. Instead of giving us a fully realized character or subplot, Mann is content to hint at it, or to lay it out in shorthand, as if he’d simply shot his notes to himself without bothering to develop them further. At the same time, he’ll devote endless amounts of energy to rendering the material at the edges: he’ll become fascinated by an extra’s face, a pattern of light on a wet surface, the arcana of specialized masculine trades. Blackhat is driven by the assumption that we’re interested in the same things that Mann is, and that we’re willing to sketch in the rest for ourselves. If the characters, for the most part, feel like placeholders, it’s mostly because he trusts us to fill in the blanks. (Hence the treatment of the veteran actor Holt McCallany, who plays a U.S. Marshal who somehow feels like an essential part of the cast despite having about five lines of dialogue.)
But there’s also a sense in which my admiration for Mann’s talents allows me to see his flaws as virtues, almost to the point of dangerous indulgence. The romance between Chris Hemsworth’s hacker and the “networking engineer” played by Tang Wei is so schematic that it plays almost as a commentary on itself: we’ve seen enough love stories in movies, it implies, that we can be satisfied by the barest outline of one. It’s as if Mann took the index cards from his corkboard and, instead of writing them, merely flung them in the general direction of the actors. The result is consistent with what I expect, and I enjoyed it on that level. Yet it doesn’t excuse how wasted Tang Wei is here, or how quickly she’s reduced to arm candy, there to be pulled by the hand as she and Hemsworth escape from bad guys on the subway. Mann has been making movies for a long time—Thief, his masterful debut, was released more than three decades ago—and he’s purified his obsessions with men at work to the point of poetry. (There are times when his surname seems as loaded with significance as Matt Damon’s in Interstellar.) But he’s never been much good with women, and this is harder to excuse. I love Mann, flaws and all, and his ability to stick to a difficult, uncompromising vision while somehow convincing studios that he’s making movies for the mainstream. But the resounding commercial failure of Blackhat might mark an end to this. So perhaps it’s time for even his biggest fans to applaud what he’s done, then pause, step back, and ask how much of it is virtue and how much is vice.
Show me the monster
Over the weekend, I finally caught up with the recent remake of Godzilla. I’d wanted to see this movie for a long time, and although I was aware that a lot of viewers had found it disappointing—especially with regard to Godzilla’s own limited screen time—I was looking forward to watching a big, effects-driven blockbuster that followed what I’ve called one of the cardinal rules of suspense. You don’t show the monster. You let the viewer’s imagination do the work. It’s what Spielberg did in Jaws and Ridley Scott did in Alien. I know all this, and I believe in it. Yet after Godzilla was over, my first reaction was, well, that I wished I’d seen more of the monster. Part of me feels a little guilty even for typing this. Director Gareth Edwards and his production team are obviously harking back to Spielberg, and there’s no question that this approach is preferable to the nonstop pummeling of the senses we get from the likes of Michael Bay. But if we look back at what what Roger Ebert wrote in his review of Roland Emmerich’s own Godzilla remake, we start to realize that the truth is a little more complicated: “Steven Spielberg opened Jurassic Park by giving us a good, long look at the dinosaurs in full sunlight, and our imaginations leapt up. Godzilla hops out of sight like a camera-shy kangaroo.”
So which is it? Would Spielberg want us to show the monster or not? Or to put to put it another way, why does an approach that works for Jaws leave us so dissatisfied with Godzilla? For one thing, there’s the fact that while Jaws leaves its shark offscreen for most of the movie, it spends the intervening time developing a trio of engaging protagonists we’d happily follow on an ordinary fishing trip, while Godzilla kills off its most interesting character before the halfway mark. A director like Spielberg also knows that every delay demands a corresponding payoff: most of the flying saucers in Close Encounters stay out of sight, but when we see the mothership at last, it still has the power to delight the imagination almost forty years later. Godzilla never affords us that kind of cathartic moment, which even a movie like Peter Jackson’s King King offers almost to a fault. More subtly, it’s worth pointing out that most of the films that first come to mind when we think of the power of suggestion, like Jaws or Alien, were forced in that direction out of technical limitations. Not showing the monster is only one of a series of ingenious decisions and workarounds imposed by real constraints, and it’s no surprise if the result is more compelling than a movie that doesn’t need to sweat as hard.
But I think the real explanation is even simpler. In Jaws, it makes sense to leave the shark off screen: for the most part, we’re seeing events from the perspective of men on shore or on the boat, fighting an unseen foe, and as long as we stick to their point of view—which makes for good dramatic logic—we won’t see more than a dorsal fin or underwater shadow. The same holds for Alien, which pits its crew against a single murderous creature in a labyrinth of darkness, and even Close Encounters, where the flying objects, by definition, are elusive enough to remain unidentified. But Godzilla is hard to miss. He’s 350 feet tall. This is a creature defined by its overwhelming physical presence, and to keep him out of sight, we need to artificially depart from the perspective of those on the ground. We cut away from the main action or cheat the lighting and the camera angles, so instead of seeing things through a character’s eyes, we enforce a kind of alienation from what the human beings in the story are experiencing. (Having already been entertained but underwhelmed by Pacific Rim, I’m starting to think that any story about two or more really big monsters might be inherently undramatic: there isn’t enough room for action on a human scale when the plot turns on a fistfight between creatures the size of skyscrapers.)
In other words, Godzilla understands the “rule” that it shouldn’t show the monster, but it forgets why that rule has meaning in the first place. Watching it, I felt much the same way I did when I saw Ti West’s The House of the Devil. In that movie, we’re repeatedly shown the heroine moving past dark doorways, and each time she does, our heart rate accelerates—but time and again, nothing happens. And after an hour of establishing the layout of its terrifying house, when the horror finally does come, the film commits the ultimate crime: it cuts away to a room we’ve never seen. Maybe it knows, rightly, that dread is more effective than terror, but it forgets an even more basic rule: if you’re going to tease us with all those shots of a doorway, sooner or later, something has to come out of that door. Godzilla makes much the same mistake, which is only a reminder of the difference between approaching a genre from the outside, even from the standpoint of a loving fan, and figuring out its logic from within, as Spielberg did. Rules, to the extent they exist, are there for a reason, and it can be dangerous, especially for smart storytellers, to honor those conventions with great technical skill while failing to articulate while they’re there in the first place. And as Godzilla proves, you can be a careful, perceptive, and talented director, but still miss the monster in the room.
The limitations of technique
Recently, as I prepare to make the last round of cuts and revisions to my third novel, I’ve been reading one of my favorite books, Charles Koppelman’s Behind the Seen. The book’s rather cumbersome subtitle is How Walter Murch Edited Cold Mountain Using Apple’s Final Cut Pro and What This Means for Cinema, and while this may not sound like a page-turner to most people, it’s one of the five or six best books on film I know. As I’ve made clear before, Walter Murch—the man whom David Thomson describes as “the scholar, gentleman, and superb craftsman of modern film,” and whom Lawrence Weschler calls, more simply, “the smartest man in America”—is one of my heroes, and for those who are interested in narrative and technical craft of any kind, this book is a treasure trove. Yet here’s the thing: I don’t much care for Cold Mountain itself. I watched it dutifully when I first read the book, and although I’ve since revisited Koppelman’s account of Murch’s editing process countless times, nothing of the actual movie has lingered in my memory. I was startled last night, for instance, to realize that Philip Seymour Hoffman plays an important supporting character: his performance, like the rest of the movie, has simply melted away.
This paradox grows all the stronger when we examine the rest of Murch’s filmography. The English Patient, as I’ve said elsewhere, is an intelligent movie of impressive texture and skill, and Murch deserved the two Oscars he won for it. But as with Cold Mountain, I can barely remember anything about it, with only a handful of images left behind even after two viewings. I couldn’t get more than halfway through Hemingway & Gellhorn, despite being fascinated by Murch’s account of his work on it at last year’s Chicago Humanities Festival. Murch has worked as a sound designer on many great movies, above all Apocalypse Now, but when it comes to his primary work as an editor, his only unqualified masterpiece remains The Conversation. (As strange as it sounds, of all the movies that he’s edited, the one I enjoy the most is probably The Godfather Part III.) I have no doubt that Murch approached all these projects with the same care, diligence, and ingenuity that shines through all of his published work and interviews, but in movie after movie, that last extra piece of inspiration, the one that might have given a film a permanent place in my imagination, just isn’t there.
Part of this may be due to the inherent limitations of an editor’s role, since even the most inventive and resourceful editor is ultimately constrained by the material at hand and the quality of his collaborators. But I prefer to think of it, in a larger sense, as a warning about the limits of technique. Movies, for the most part, are technically wonderful, and they’ve been advancing along all the dimensions of craft—cinematography, sound, art direction—since the invention of the medium. Progress in art is never linear, but with respect to craft, progress is continuous and ongoing, with each generation adding to its predecessor’s bag of tricks, and as a result, movies look and sound better now than they ever have before. Moreover, nearly without exception, professionals in film are good at their jobs. Even the directors we love to hate, like Michael Bay, arrived at their position after a fierce process of natural selection, and in the end, only the most tremendously talented and driven artists survive. (Bay, alas, has one of the greatest eyes in movies.) Not everyone can be as articulate or intelligent as Murch, but for the most part, movies these days, on a technical level, are the product of loving craftsmanship.
So why are most movies so bad? It has nothing to do with technique, and everything to do with the factors that even the greatest craftsmen can’t entirely control. When you look at a student project from any of our major film schools, the technical aspects—the lighting, the camerawork, even the acting—are generally excellent. It’s the stories that aren’t very good. For all the tricks that storytellers have accumulated and shared over a century of making movies, decent scripts are either tantalizingly elusive or destroyed along the way by the hands of studio executives—which is one role in the movie business where talent does not tend to rise to the top. And the proof is everywhere, from John Carter on down. If there’s one movie artist who rivals Murch for his intelligence, good advice, and willingness to discuss aspects of his craft, it’s screenwriter William Goldman, who hasn’t written a movie since Dreamcatcher. Technique only gets you so far; the rest is a mystery. And even Murch understands this. On the wall of his editing studio, we’re told, hangs a brass “B.” Koppelman explains what it means: “Work hard to get the best grade you can—in this world, a B is all that is humanly attainable…Getting an A? That depends on good timing and the whims of the gods.”
What makes a great action scene?
For most of this week, anyone passing by my house would have seen a bright rectangular glow in the living room window, as the new Blu-ray of Mission: Impossible—Ghost Protocol played in a nonstop loop. While it doesn’t have the same visceral power as it did in IMAX, this is still a fun, expertly assembled action movie, the perfect sort of thing to have playing in the background while I’m working on other projects. Even after seeing it three or four times, however, I still have to drop everything and watch whenever the big scene in the Burj Khalifa comes up. I may not get as dizzy as I did when I first saw it, but even on the small screen, it’s still wonderfully exciting—and all the more terrifying when you know how it was actually filmed. (Incidentally, as much as I hate this sort of corporate extortion, it’s worth shelling out the extra money for the Best Buy exclusive edition, which contains some great bonus features that aren’t included in the version available on Amazon.)
In fact, I’d say that the Burj Khalifa climb in Ghost Protocol is my favorite action sequence of the past five years, on a short list that includes the Guggenheim shootout in The International and the opening chase scene in Drive. At first glance, these three scenes might not seem to have much in common—one is a death-defying ballet staged one hundred and thirty stories above the ground; one is lunatic, extended gunplay; and the last is the car chase as chess game—but they’re all executed with something of the same spirit, and it’s worth drilling down to figure out why they affect us so deeply. There’s something hugely pleasurable about these scenes that goes beyond their immediate impact, and which sets them apart, in my mind, even from such landmark sequences as the hallway fight in Inception, which I love, but find somewhat less interesting from a writer’s point of view. Because what the three scenes I’ve mentioned have in common is that they were all written first.
Here’s what I mean. Many action scenes, particularly car chases, come off as assemblages of second unit footage that have been pieced together in the editing room, and as a result, there’s something monotonous about the relentless similarity of action—just see any Michael Bay movie for an example. The action sequences in these three films, by contrast, were conceived on the printed page. They have a clear beginning, middle, and end. They make memorable use of their locations. They have small setups, payoffs, and surprises along the way, as when Ethan Hunt throws away his malfunctioning glove and finds it adhering to the side of the building a few stories later. Each is centered on the personality of the characters involved—indeed, each scene unfolds as a sequence of logical choices, which is something you’ll never hear said of Transformers. And these are all things that can only be planned at the screenplay stage.
And while this may seem obvious, it’s worth remembering in light of a movie like The Hunger Games, which has its good points, but to my eyes, despite the strength of its material, doesn’t know how to plan and carry out action. Instead, it relies on editing and camerawork to create the illusion of momentum, when all of this should have been laid out in the script. (Note that none of the three films I’ve mentioned ever use anything resembling a shakycam.) Full credit, then, to writers Eric Singer, Hossein Amini, and the platoon that worked on Ghost Protocol for giving us action scenes we’ll remember, which is something that ought to be celebrated. Because it appeals so shamelessly to our reptile brain, the ability to write a great action scene may never get the respect it deserves, but like any other narrative skill, it benefits from intelligence, ingenuity, and clarity of thought—and all of the editing tricks in the world won’t make up for their absence.
Transformers: Death of the Author
Never has a city been more lovingly destroyed on camera than Chicago in Transformers: Dark of the Moon. By the time the movie reaches its crowning orgy of destruction, my wife and I had been staring at the screen for close to ninety minutes, along with an enthusiastic crowd in the IMAX theater at Navy Pier. My wife had seen much of the movie being shot on Michigan Avenue, just up the street from her office at the Tribune Tower, and I think it was with a sort of grim amusement, or satisfaction, that she watched her own building crumble to pieces as an alien robot spacecraft crashed into its beautiful gothic buttresses. It’s an image that merits barely five seconds in the movie’s final hour, which devastates most of downtown Chicago in gorgeous, even sensual detail, but it still struck me as a pivotal moment in our personal experience of the movies. (And hasn’t the Tribune already suffered enough?)
Like its immediate predecessor, Transformers 3 is generally pretty lousy. (I actually liked the first one, which had the advantage of comparative novelty, as well as a genuinely nimble comic performance by Shia LaBeouf that both director and star have struggled to recreate ever since.) As a story, it’s ridiculous; as a perfunctory attempt at a coherent narrative, it’s vaguely insulting. It’s also staggeringly beautiful. For the first ten minutes, in particular, the IMAX screen becomes a transparent window onto the universe, delivering the kind of transcendent experience, with its view of millions of miles, that even Avatar couldn’t fully provide. And even after its nonstop visual and auditory assault has taken its toll on your senses, it still gives new meaning to the phrase “all the money is there on the screen.” Here, it feels like the cash used to render just one jaw-dropping frame could have been used to pay down much of the national debt.
As I watched Dark of the Moon, or rather was pummeled into submission by it, I had the nagging feeling that Armond White’s notoriously glowing review of Revenge of the Fallen deserved some kind of reappraisal. At the time, White was dismissed, not without reason, as a troll, for issuing such pronouncements as “In the history of motion pictures, Bay has created the best canted angles—ever.” And yet I don’t think he was trolling, or even entirely wrong: it’s just that he was one movie too early. Michael Bay’s genius, and I use this word deliberately, is visible in every shot of Dark of the Moon, but it’s weirdly overdeveloped in just one direction. Bay is like one of those strange extinct animals that got caught in an evolutionary arms race until they became all horns, claws, or teeth. While a director like Christopher Nolan continues to develop along every parameter of storytelling, Bay is nothing but a massive eye: cold, brilliant, and indifferent to story or feeling. And it’s pointless to deny his talents, as ridiculously squandered as they might be.
So what exactly am I saying here? To steal a phrase from Roger Ebert’s review of The Life Aquatic, I can’t recommend Transformers: Dark of the Moon, but I would not for one second discourage you from seeing it—provided that you shell out fifteen dollars or more for the real experience in IMAX 3-D, which Bay has lovingly bullied the nation’s projectionists into properly presenting. (On video, I suspect that you might have the same reaction that my wife and I did when we rented Revenge of the Fallen: within forty minutes, both of us had our laptops out.) It’s an objectively terrible movie that, subjectively, I can’t get out of my head. As an author, I’m horrified by it: it’s a reminder of how useless, or disposable, writers can be. I won’t go as far as to say that it’s a vision of my own obsolescence, or that I believe that the robots are our future. But at this point in history, the burden is on writers to demonstrate that we’re necessary. And the momentum isn’t on our side.