John August

John

New Wiki for discussing better screenwriting software

Geek Alert

While I intend to continue the discussion on this site about how to make better screenwriting software, interested readers might want to check out a new wiki on the topic, which an interested reader forwarded to me yesterday.

For those who’d never used a wiki (and I hadn’t), it’s essentially a series of interlinked web pages which anybody can edit. It’s chaotic and not especially pretty, but it may be a good place to share ideas about what you’d like to see in your dream screenwriting software.

**Update March 2011:** Dead links. Article retained for historical interest only.

Writing on the Coast Starlight from Los Angeles to Seattle

Projects, Tarzan

amtrakLast week, I took Amtrak’s [Coast Starlight](http://www.amtrak.com/trains/coaststarlight.html) train from Los Angeles to Seattle, which meant 36 hours on the rails. That’s a very long time to spend in linear motion, but it was worth it.

My goal was to get some quality, uninterrupted writing time for the oft-delayed Tarzan, and I got it. I wrote long-hand, as I usually do on first drafts, and faxed the pages back to Los Angeles once I got to Seattle. Once everything was typed up, I had 41 more pages finished, which is good for three day’s work.

I’d recommend the train for any writer looking for some good alone time. Some caveats:

1. American trains are much, much slower than their European counterparts. We averaged 35.6 miles per hour.
4. My train was 2.5 hours late getting to Seattle, which is apparently the norm. So don’t expect to make it somewhere at a specific time.
1. You absolutely need a sleeping car. I have no trouble flying coach, but beyond hour ten, you’ll be pulling your hair out if you don’t have a door you can shut.
2. The dining car seats parties of four, so they’ll put you with strangers. Everyone I ate with was friendly and talkative.
3. Bring a pillowcase. The Amtrak linens are scratchy.
5. Cell phones work almost everywhere, except parts of Northern California.

I flew back from Seattle, which was always my plan. As much as I enjoyed my Amtrak time, I don’t know if I could have taken another 36 hours of train so soon.

New Final Draft version 7.0 is…marginally better

Formatting, Geek Alert

finaldraftjpg
My screenwriting software of choice has long been [Final Draft](http://www.finaldraft.com), which is 90% great, 10% maddening and significantly better than any of the other programs I’ve tried — and believe me, I’ve tried a bunch. This past month, Final Draft came out with version 7.0, which was the first major update in a while.

On the plus side, the new version is stable. It hasn’t quit on me, and it hasn’t had the same [refusing-to-launch problem](http://johnaugust.com/2004/when-final-draft-wont-open-under-os-x) the last version had. It doesn’t choke on the previous version’s files, which is a problem I’ve encountered every previous integer-level upgrade.

One nice new feature is the ability to split a document window, so you can see two parts of the script at the same time. You can show one of the panels in scene-navigator view, or as index cards — which can now have two sides. On a big screen, keeping the left panel open to the scene navigator lets me click through to specific sections quickly.

Splitting the screen is helpful, but hardly revolutionary. Many Mac programs — including Microsoft Word — have had split windows for over a decade. Final Draft runs into familiar problems with this setup. If you make a selection in one panel that extends into the region shown in the other panel, the program freaks out. Caveat selector.

I never use Final Draft’s index cards. While in theory it would be great to reorganize your script just by moving some cards around, real life screenplays never work that way. Scenes aren’t Legos, and they can’t be flopped around willy-nilly. In my opinion, better choices for outlining are [Omni Outliner](http://www.omnigroup.com/applications/omnioutliner/) and [Pyramid](http://www.mindcad.com/). Each of these has free demo versions.

Final Draft 7 is apparently better at exporting .pdf files. That may be new for Windows, but if you’re using Mac OS X, I’d highly recommend using “Print…” and “Save to .pdf” instead. That way, you have all the options of the print dialog box, and you’re guaranteed to get just what the printer would.

There are other features I wish Final Draft had, such as XML export for the web, a clipping bin, and less-aggressive Smart Lists. But on the whole, the program works well for what I make my living doing. And for screenwriters lucky enough to have an honest-to-goodness movie on their hands, the production features alone are worth the price. Final Draft does a very solid job locking pages and tracking revisions, which makes sending out colored pages considerably easier than it has any right to be.

Should you buy Final Draft? Probably. Should you upgrade? That depends. If you’re happy with version 6, there’s really no pressing need. Version 7 isn’t bad, but it isn’t a huge improvement.