Scanners
Tinker Tailor, Moneyball: Between the lines (Part 1)
Jim Emerson | 2012-01-10
I would never want to read a screenplay before seeing the movie based on it. As a critic, in fact, it would be a violation of my responsibilities (and ethics) to do that. The film has to be seen on its own, as a completed work; a critic shouldn't rummage through the drafts before experiencing the finished piece -- whether it's a movie or a painting or a symphony. I'm even ambivalent about reading certain books before seeing the movie versions, too, and for the same reason that I don't like to see trailers, particularly of films I'm likely to write about: I don't want to harbor preconceived ideas (even unconscious impressions) when I watch the picture. As we all know, it's hard enough to get a clean look at a movie after all the advertising and interviews and seasonal previews and reviews...
But if you want to gain some understanding of how movies are actually made (movies in general and any movie in particular) it's often enlightening to go back and take look at how the screenplay (or various drafts, re-writes, polishes) evolved into the movie that eventually wound up on the screen. Some filmmakers like Clint Eastwood often claim to simply shoot a script "as written" (though he and Dustin Lance Black did some re-working, including adding a voiceover, on the "J. Edgar" screenplay). But it can be fascinating to see how the writer(s), director(s) and editor(s) shape the material throughout the entire process -- and how moving (or removing) images and lines from one context and placing them in another changes their meaning. This is now easier to do than ever before, because so many screenplays are available online -- legitimately (For Your Consideration at studio sites) and otherwise.
May contain spoilers
ncG1vNJzZmivp6x7s7vGnqmempWnwW%2BvzqZmnJmjqXqiusNmmqudp2TAqrnOp2Smm5Kqv6%2Bx2A%3D%3D