Friday, February 01, 2013

The Writing Week (Vol. 6) part 257 - Reading with Fresh Eyes

The draft is done! Sci-fi spec, draft two, complete and out to my writing partner as of Monday night. And then, to kick off my edit phase, I something I've never thought to take the time to do before. I decided to read the script.

Say what? Yeah, I know what you're thinking. Of course, I read the script after I finish it. I check for typos and grammatical errors and redundant dialogue. But I don't really read it for content. Not really. Sure, I look to see if I can make any cuts or streamline and dialogue, but it struck me that when I revise a draft, I don't really look at the content, just the format. My edits become more minor than they should be. I'll tweak a line here or there or shorten a sentence of dialogue or description so as to cut a hanging line on the script and shorten it, but the trade-off is that I subconsciously commit to what I've written. I fail to read the thing from the point of view of someone who is unfamiliar with the script (or as close to that as I can get) and therefore don't look for story problems. I became most aware of this during my rewrites this go-around, when I read some dialogue from draft one and thought, "This is HORRIBLE." Same for certain beats. They just didn't make sense. How could I willingly submit that to my partner?

This time, however, I decided to put the pen away as much as possible and just read the script in one sitting. No looking for edits. No streamlining line by line. Just read it for the feel and flow of the story, and do the particular edits later. Sure, I found a few glaring things - missing period at the end of a sentence or a missing line of dialogue - that I flagged as I read, but I would have picked up on those if it wasn't my own material anyway. And you know what happened?

I liked the script. I mean, I really liked it. To be honest, I think it's some of the best writing I've done in a very long time. Very little seemed gratuitous. All the beats that needed to be there were. The characters had arcs and motivations. And Act One was the tightest, most refined that I have produced in a long time. Granted, I found some things that should go, but on the whole, I was incredibly pleased. I'm not trying to make the argument that this is because I did the read-through without edits - the two really aren't connected beyond the fact that I would likely not have seen this had I gone straight to line by line edits - but the product results were hard to ignore. I'm really jazzed by this draft, and I think my partner is, too.

Even if the draft was unsuccessful, or even just less successful, I truly feel that sitting down and simply reading the script before really editing it was the way to go. I absolutely plan to do that with every project I have going forward. It just doesn't make sense to me not to, and I can't believe I hadn't adopted that practice sooner. Getting mired in the nitty-gritty of an editing process is great, but it's important not to miss the forest for the trees. I was super guilty of that in the past. Plus, it's always fun to read a script, no?

Monday, January 28, 2013

The Writing Week (Vol. 6) part 256 - Thoughts on Structure

It's been nearly a month since I began the second draft of my sci-fi collaboration, and I have high hopes of finishing it tonight. Of course, I'll still have to to a word-by-word read-through of the whole thing, but that's neither here nor there. It'll be wonderful to have a hard copy of the script to work off of, and I can already say, without having gone through and read it again, that it's crazy the difference a draft can make.

Already, when I go back and reread draft one (I'm working off a copy of that draft, editing as I go along, so I'm getting intimately reacquainted with the first pass), I find myself thinking what utter crap some of it was. Structurally, it was fairly sound, though a lot of it proved more dependent on coincidence than I would have liked. And there were certain reveals that I withheld until the end of act two, which my partner felt were much stronger as midpoint surprises. In the rewrite, I came to see his point and shuffled a lot of important information around - to the betterment of the script. The dialogue has been streamlined and improved upon; the characters are much more three-dimensional and now have actual arcs, and the world in which we've set the story is infinitely more detailed and unique. All in all, it's a huge improvement.

Part of the rewrite process has gotten me thinking about story much more. This particular one is now much stronger, and perhaps just because I'm in the middle of it now, but I've been more attuned to story in general. Take, for example, Django Unchained, which I saw yesterday. I'm not the world's biggest Tarantino fan in general, and I'd been semi-hesitant to see Django. My viewing experience pretty much validated my initial expectations.


SPOILERS FOR THOSE WHO HAVEN'T SEEN DJANGO YET


Still with me? As you know, Django is a long movie. And a violent one. And you know what? I didn't feel as though either was fully justified. Primarily, that's because the ending - to me - came 20 minutes before the credits rolled. After Candie is killed - this is the antagonist, we're talking about... sort of... well, one of them - there are at least four dozen deaths yet to come. Django has technically secured his wife's freedom, but it's cost him his own, as well as his friend's life. Candie drops, and his untold number of minions storm the house, ala Scarface, for a shootout that will literally paint the walls red.

But I didn't care. The bad guy was dead. Those who were left to catch bullets were the anonymous faces of extras we'd met briefly, or only in passing. Yet, their deaths and shootout with Django took so much screentime, as a point in which I'd already been sitting for well over two hours. It was time to call it a day. Shootout over, we still have to meet a couple Australian slavers, see their three deaths, and then watch Candie Land get blown to smithereens - after another five deaths in the foyer. I didn't care about a single one of them. Sam Jackson's character was interesting, but at that point, I had already watched Django take out: a trio of brothers he had a personal vendetta against, Big Daddy and his pre-Klansmen, and Candie. How many antagonists are we dealing with? How many should I care about? I cared about Candie. I was please when he got his comeuppance. The others - excess screen time that I didn't need.

My first draft of the sci-fi spec came in at a whopping 130 pages. I'm happy to report that this draft will top out at 116, maximum. I've trimmed the fat, made sure that each scene, character, and line of dialogue is warranted, and I have made the story move as smoothly and quickly as I can. No, I'm no Tarantino and don't have the cinematic license he does. I'm content with that and, for now, simply want to make sure that my story is as strong as it can be. 

Tuesday, January 15, 2013

Logline Central - The General Staff

Logline Central is an irregular segment that takes a deeper look at loglines of scripts or projects that have just been purchased, as listed on DoneDealPro.

This week, I want to take a look at a featured logline, not because it sounds like it will lead to a particularly good movie, but because it's one hell of an interesting acquisition.

Title: The General Staff 
Logline: Set in 1979, "cowardly" U.S. diplomats are treated with kindness and eventually delivered to safety by their Iranian hosts. 
Writer: Ataollah Salmanian 
Prod. Co: Arts Bureau  
More: Ataollah Salmanian will direct. The film is being produced by the Iranian government in response to "Argo."

A government-funded response to another nation's fictionalized account of a thirty-year old event. Wow. I wonder how often that has happened before (and plead ignorant on the history of such occurrences). 

What are the implications of the film? (Note that I care very little about the actual content in this case; it is very clearly propaganda, which isn't how I interpreted Argo, but perhaps that bears a closer look.) Is the tone anti-American? Will it portray a wildly different version of the 1979 events, depicting Americans as the antagonists? I reserve no judgment on that, or on whether or not "we" were "bad guys" in that case. Politically, what does the film mean?

Am I ignorant of Argo's implications? I wasn't aware it was a statement that required or even prompted a response. Certainly not of this variety. And, perhaps more importantly, what does the Arts Bureau seek to gain by making such a picture? From a business point of view, the hypothetical Hollywood mogul in our Logline Central posts can question whether this film would ever be picked up for distribution, receive awards consideration, or otherwise make its investment back. On a more intellectual, less financially-driven level, I'd ask - who will see the film? It strikes me that it is made for Iranian audiences to address perceived gross misrepresentations and inaccuracies in an American movie. But will it ever reach beyond the country's borders?

I can't deny that there's a small part of me, a jocular, albeit maybe fractionally optimistic part, that wonders if The General Staff is indicative of something larger, a new paradigm in international relations. Could this be the new way countries wage war? Not a cold war, but a Celluloid War. Propaganda films replace guns, and theaters replace battlefields. We address our disagreements not through bloodshed, but with esoterically re-written histories. Sure, Iran's history in this case would vary greatly from the way we in the States perceive it, but doesn't it already? Dialogue between nations would crumble if every response is delivered in the time it takes to absorb a film and develop and produce a feature film in response, but the body count would drop considerably. And, frankly, can anyone claim that the dialogue that exists now is really any stronger? Maybe the fight of the films is the new way we should go in modern warfare. It would certainly be more civilized.

Or maybe that's just another far fetched, out of touch with reality film idea. 

Monday, January 14, 2013

The Writing Week (Vol. 6) part 255 - The Power of Story

We write because we need to tell a story the whole way through. This is different than needing to tell a story, for why do we spin a tale if not to arrive at its conclusion? More than wanting to let our readers and listeners and viewers know how the story ends, we write because we, too, can't bear the thought of not knowing the resolution. 

Twice a day, I board the N or Q train from Astoria, Queens to Midtown, Manhattan, and back again for work. My commute lasts about twenty minutes, barring any technical difficulties, passenger problems, or general New York City subway nonsense. For the most part, I try to spend that time with my nose in a book, feet out from beneath other strap hangers, and my being as far as humanly possibly from whoever has decided that the three-minute trip beneath the East River is the best and only time they can unleash hack after cough after sneeze into the confined metal car. Sometimes, though, despite my best efforts at ignoring everything and everyone around me, my ear will pick up on snippets of dialogue, and I can't help but listen and wonder... what happens next?

"I gave Julie a call last night, asked if she wanted to hang out."
"Oh yeah," said the passenger's friend, "what'd she say?"
"She said she was watching TV and doing chores, but did I want to go over. So I brought some beer and we chilled for a bit."
"Nice, dude, did anything happen?"

"This is Times Square, 42nd Street. Stand clear of the closing doors, please." The conductor has a nasty tendency of interrupting stories, just as I begin to get invested in them.

I don't know who Julie is. I don't know her relationship to either of the men talking about her. Are they all friends? Are they dating? Is Julie his sister? Is she his ex wife? Or his mistress? What could Julie possibly have to do with them, and what on Earth happened when he went over?! Did they hook up? Did she put him to work on the chores? I hope he didn't do anything to Julie, and I hope they had a nice time. But how will I ever know? And why do I care? Maybe nothing came of it. Maybe Julie is the passenger's friend. Maybe the next words to come out of the passenger's mouth were, "We had two beers and called it a night an hour later and were each in bed by 9." Conclusion. The end. But, damn it, I want to know if that's the case.

That is the power of story. 

Give me an introduction and a sense of who the characters are, and I'll want to follow them, even if it's just for two minutes on the subway. Even if it winds up being nothing, a boring tale about a mundane night. Yet don't withhold the ending from me. Don't unknowingly rope me in and dangle the promise of a resolution that I never get to hear. That's just cruel. 

I tell stories because I want to share something - an experience, an idea, a fable - with you. But here's the secret; I also tell them, because I can't abide by not knowing what happens in the end once the beginning has popped into my head. I simply can't. I must know, and you must let me tell you. I'll go mad otherwise. It's why we often watch a terrible movie start to finish, though we know twenty minutes in that it's garbage - there's a fundamental, human curiosity that none of us can shake. Sure, there are exceptions, but when someone says something that they think is not only worth sharing, but also entertaining, dramatic, or stirring, we can't help but listen in to see if it moves us, as well. 

Is Julie's plight an earth-shattering, transformative one? Probably not; it's probably an insignificant tale about a minor, forgettable experience worth telling only in the time it takes to go the two stops from 49th Street to 34th. But just on the off chance it is something more, something worth hearing, shouldn't I listen in? You've unknowingly captivated me, and when we stop at 42nd Street half-way into your yarn, wouldn't you prefer I stay to hear the pay-off? 

I get off the train, despite wanting to know more, because that is my stop. But maybe, just maybe next time, I'll ride to 34th, because that is the power of story. 

Thursday, January 10, 2013

2013 Oscar Nominees Announced

You've seen some or all of them. Or none of them. You loved, hated, or felt indifferent toward them. You've sung their praises, or have no clue what all the hype is about. Well, for better or worse, whether you agree with the choices or not, here they are, folks - the 2013 Oscar Nominations!

BEST PICTURE
Amour
Argo
Beasts of the Southern Wild
Django Unchained
Les Miserables
Life of Pi
Lincoln
Silver Linings Playbook
Zero Dark Thirty

BEST ORIGINAL SCREENPLAY
Amour
Django Unchained
Flight
Moonrise Kingdom
Zero Dark Thirty

BEST ADAPTED SCREENPLAY
Argo
Beasts of the Southern Wild
Life of Pi
Lincoln
Silver Linings Playbook

You can read all of the nominations here.

What are your predictions, favorites, and snubs?

The Oscar telecast will be Sunday, February 24, starting at 7pm EST. 

Thursday, January 03, 2013

The Writing Week (Vol. 6) part 254 - A New Year, A New Outline

Happy New Year! Off, it's been a while since my last post. I guess the end of 2012 saw me veer off schedule with these "weekly" updates. No more - I am trying to get back on track! At the very least, though The Writing Weeks might have fallen off track, I'm happy to report that my writing itself did not.

Where to start? The end of December was actually pretty exciting/interesting. For one, we decided to do another push with the post-Apocalyptic spec. As far as I know, we got a couple reads over the holidays, which ideally I'll have some updates on by the end of next week. One of the people reading is actually a manager, which will be interesting. (If you've been reading, you know I have reps in LA already, but I got the requisite go-ahead to send, so we'll see what happens.) He is someone I was in touch with years ago when I was fresh out of school. My material wasn't ready at that point, especially the script that he read then, and I recognize that now. Naturally, I had high hopes, and he responded generously, but we didn't wind up working together. Looking back on that script, that's no surprise to me at all. I'll be the first to admit that screenplay was not ready for industry attention. Perhaps the second time will be the charm. I certainly like to think I've grown much stronger as a writer in the ensuing years.

The sci-fi collaboration hit a bit of a bump at the end of the year. A (very) similar project was announced at a major studio. Well, perhaps that needs some qualification. A studio picked up the rights to some material that is strikingly similar. I won't speculate as to why it might be eerily akin to ours, as it's not really my place, but it was - to say the least - a shock. My writing partner and the producer who paired us agree that our best plan is just to push forward and produce a polished screenplay before the other project comes to fruition. We have too much invested to stop, and neither my partner nor I want to. I have no way of knowing what the outcome will be, other than to tell you that the immediate result was a fire lit right under my butt.

Sitting above the flames, I cranked out a revised outline for the project in question over the holiday week. The second half of the script remained largely the same, structurally. In fact, much of the script did, but I made a lot of adjustments earlier on, since we decided to skew toward a slightly younger audience and wanted to emphasize the science elements, rather than the action ones. My writing partner and I already had another hour discussion on the new outline, emphasizing the big points we want to hit that weren't called out in the outline, which are mostly emotional. End result: I started revising last night and am aiming for the draft to be done by the end of the month (knock on wood). 

How is your 2013 starting?

Wednesday, December 19, 2012

The Writing Week (Vol. 5) part 253 - The Elephant Graveyard

I like to think that I'm far from alone in having what I call an elephant graveyard of scripts. You know what I'm talking about; years ago, you had a great idea for a new spec, and you flew through draft one, and then... stopped. Or you wrote that draft, and while letting it settle, you decided to jump onto something new. And then never jumped back. Or you were in a rut, so you decided to just write something - anything - and got out of your rut successfully, leaving a draft of something you were lukewarm about in your wake. The end result of all those efforts (and others)? First drafts. Lots of them. Sitting on your hard drive or in your desk drawer with nothing to do but take up space. 

However, that's not quite true, is it? With any luck, even projects that we abandon entirely after typing THE END for the first and last time on them teach us something. My theory is that a piece of writing should never be a total waste. Even if the lesson learned is that that specific type of script or genre isn't your cup of tea, then it's been valuable. But what of all the other scripts that you have a draft of, which you like the concept of, but that you haven't touched in years? What becomes of them?

I've come to realize that, for me personally, the desired answer to this is, "something." The sci-fi project I'm collaborating on, which just saw a very upsetting similar project announced, is still in the works. The holiday week will hopefully bring forth a necessarily strong draft two from me that I can give my partner in early January. Of course, I also have other ideas that I want to work on when that is done. And, somewhere, the post-apocalyptic spec is still floating in the Hollywood ether. But let's go back to that elephant graveyard, shall we?

I don't quite know how many first drafts (or second drafts) or projects sit on my computer. Off the top of my head, I can easily count seven projects that I took from initial idea to at least one full draft (not including the three mentioned above). I'm probably forgetting some. I also have at least as many that I developed to some degree outlines, partial drafts, etc. Beyond that, there's a slew of two dozen or so loglines I came up with for completely different concepts. Bottom line: there's a lot of material there. Of the seven I did a draft of, there is not one I refuse to work on again. In fact, I still feel excited by most of them. At the very least, I would be willing to commit to getting them more industry ready.

I don't know what my next project will be. I have one idea in particular that I am really stoked to work on, but I don't know nearly enough about it yet to begin writing. As I keep thinking about what to do next, I can't help but mentally revisiting some of these other ideas. More than that I like any of them better than the other projects I'm tossing around, I dislike the notion that I poured myself into these works once, and then abandoned them. I try to make it a rule that I will only write things I would want to see, and I would still want to see all seven of those. So why not revisit them? If nothing else, I am farther along in their development for the sheer fact that they each have a full script to work off. Is there any reason not to try to bring one of them to fruition?

Do you have an elephant graveyard of scripts? Does it grow each year, or do you try to cull the proverbial skeletal herd?