John August

Software

The Unnecessary General

QandA, Screenwriting Software, Software

questionmarkIn Final Draft, what do you use the “General” element for? The manual describes its function negatively, saying only that it’s for whatever doesn’t fit into the other elements. Personally, I haven’t found a use for it yet and was wondering what the pros use it for.

— Richard Budd

As far as I know, nothin’. I bitch about Final Draft a lot, but one good thing it can do is create new styles (er, elements) for unanticipated needs. I created one called “singing” for dialogue that is part of a song (11pt Verdana italic). So why would I need to re-appropriate “General?”

Perhaps if I were writing a treatment, or some sort of other non-screenplay document, and didn’t feel like putting everything in “Action.” It’s conceivable, I guess. I recently had to write an extended outline for Shazam!, but I used [Pages](http://www.apple.com/iwork/pages/) for its footnoting ability. The only advantage I could see to using Final Draft for an outline is its frustrating-but-consistent revision marks.

If any readers have a better explanation for the existence of “General,” I’d love to hear it.

Title page trouble with Final Draft .pdfs

How-To, Rant, Screenwriting Software, Software

Reader Josh C wrote in with one solution to a problem that’s been frustrating me for months. When you want to save a script as a .pdf, Final Draft won’t always include the title page. It’s frustratingly inconsistent. The obvious workaround is to save the title page as a separate file, which is what I’ve often done. But then you end up emailing two documents, increasing the confusion on the other end.

Josh was using Final Draft version 6.0.6.0. It turns out, the issue is whether the “Title Page…” window is open or closed.

1. Save your screenplay as normal (as a .fdr)

2. With your saved screenplay still open, go to Document > Title Page. A new, blank Title Page opens.

3. Fill in the blanks, then just CLOSE THE TITLE PAGE. This is the part that I got hung up on forever. If you leave the title page open, then try to save as a PDF, it won’t work. The Title page WON’T attach itself to the PDF if the Title Page is still open when you try to Save as. Just close the Title Page. It saves automatically to your screenplay.

4. With your screenplay still open, go to File > Save As — then select Adobe Acrobat Document (*pdf) – or whatever your computer says. Save the new PDF file somewhere and open it up. The Title Page should be attached at the top of the screenplay where it should be 🙂

In my tests with 7.1.3, the .pdf will also include the title page even if that window is still openHowever, if you haven’t closed or saved the title page, it won’t be updated until you do. — provided you have a [certain checkbox checked](http://oslo.instantservice.com/iskb/SearchAnswer.cfm?NodeID=181153) in “Preferences.”

checkboxYes, I’ll admit that I didn’t read the manual with version 7 of Final Draft. But this is a pretty questionable place to put this checkbox. After all, sometimes you’ll want to include the title page, sometimes you won’t. Does it really make sense to have this be an application-wide preference, housed in a panel that has nothing to do with printing, saving or the specific document you’re working on? It’s pretty much the last place I’d think to look for it.

What’s more, at least on the Mac, Final Draft is using the built-in .pdf facility of OS X. It’s basically just printing to a file.You can test this by choosing a two-page layout in the Print dialog box. The next time you choose to Save as PDF, you’ll get facing pages. Since it seems to be using the standard print architecture, you’d think that choosing the “Print Title Page” option in the Print dialog box would have some effect. It doesn’t. And that’s why it’s frustrating.On the Mac, you always have the option of using the “Save as PDF” function built into the Print dialog box. But I’ve never had any luck getting that to include a title page. My guess is that Final Draft treats the title page as a separate document. When you print to a traditional printer, you’ll notice a one-page progress dialog flash for a second. I think Final Draft is kicking out the title page as a distinct job. It never incorporates it into the “real” script.

Whenever I complain about Final Draft, I get a nice note from the developers asking me to help out with the next version, and a few emails from companies working on competing applications. So let me make it clear where I stand. Despite its annoyances, I end up using Final Draft because what it gets right generally outweighs what it gets wrong. There’s certainly some inertia on my part, but given a better alternative, I’d switch in a heartbeat. The shipping versions of Screenwriter, Montage and Celtx aren’t better, particularly when it comes to revisions.

I’m hoping the upcoming Screenwriter 6 gives Final Draft some real competition, because that’s what’s lacking. When we were cutting The Nines, I realized that editing software has benefitted tremendously from the battle between Avid and Apple, with new features, better interfaces, and dramatically lower prices. I started out a Final Cut Pro man, while my editor was firmly Avid. We had the luxury of both being right. Both systems are terrific, and I think that’s largely because of the competition.

I heart WriteRoom

Projects, Rave, Software, Sundance, The Nines

For the past few weeks, I’ve been working on the production notes for The Nines. The document will end up being about 20 pages, detailing the backstory of how the movie got made, from inspiration through editing, along with everyone’s bios. It’s part of the press kit for the film, helping the journalists at Sundance remember who the hell was in the movie they saw three days ago.

Ultimately, we’ll end up formatting the notes in Word or Pages, but for raw text I lean heavily on TextMate, which is what I use for all of the writing for the site. It’s unbelievably powerful, if occasionally maddening.To wit: If you use command-z “Undo” to fix something you shouldn’t have deleted, TextMate will replace it one letter at a time, undoing each backspace rather than the whole chunk. Apparently, the software creator feels strongly that this is the logically correct behavior, and while I disagree, I fully respect his decision to say, “because that’s how I want it!” I have TextMate set to automagically generate a lot of the formating markup, and the tag-wrapping feature can’t be beat. But on a lark, I decided to try a new application for writing the production notes: WriteRoom.

It’s deliberately, refreshingly bare-bones and retro. When you open a window, it takes over your entire screen, including the menu bar. All you see is the words, complete with a blinking cursor. Perhaps nostalgic for my years writing on an old Atari, I’ve chosen a dark blue background with almost-white 18 pt. Courier. Give me a kneeling chair and a dot-matrix printer and I’m in junior high again.

Other writing applications are picking up this full-screen meme — honestly, it’s hard to figure out why it took so long. Apple’s Pro apps (Final Cut Pro, Aperture) have had no qualms grabbing every available pixel of real estate, although they don’t completely banish the common interface elements. (Except for Shake, which also requires a blood sacrifice to Ba’al.)

The big-screen treatment is the digital equivalent of closing the kitchen door when company comes over: Never mind the mess in the sink, let’s have a nice dinner.

WriteRoom 2.0 is in beta, but there’s nothing spectacularly different or better than plain old 1.0. Either version is worth checking out.

As for the inevitable question: Could I write a script with it?

Yes, no, maybe.

I’ve actually had conversations with two gurus of web markup about creating a simplified screenplay markup that could be imported into “real” screenwriting applications like Final Draft. WriteRoom and its ilk support tabs and external scripts, so it’s conceivable to build a system like ollieman’s screenwriting with TextMate bundle.

But for now, I have an actual paid rewrite to be doing, and it’s a Final Draft job. Sigh.

Final Draft updated

Software

Final Draft, the screenwriting application I use most despite profound reservations, has been upgraded to 7.1.3. I haven’t gotten it to crash, so that’s something.

My assistant Chad had never used the Tools>Reformat command, which despite its clunky interface is a huge timesaver when importing text from other places.Including other Final Draft scripts. Too often, Final Draft will retain the margin and font information after a copy-and-paste, so it’s up to you to remind it that you really do want the dialogue lined up. Basically, it steps through your script paragraph by paragraph, waiting for you to press a key indicating which type of element — action, dialogue, parenthetical — that paragraph should be. If the formating is okay, ‘N’ will leave it alone and jump you to the next block. ‘P’ moves you back.

Make friends with Command-R.

One aspect of Final Draft I’ve long neglected is its ability to do multiple panes. I’ve never found splitting the window all that helpful, but with today’s giant monitors, I could see myself doing it more. One often needs to refer back to other parts of a script while writing a scene. Multiple panes make that marginally easier.

One annoyance is that Final Draft won’t let you see the two panels in different views. If I could see the “real” script on the right and the expanded script notes on the left, that would be helpful. But Final Draft can’t do that. The exceptions are Scene Navigator and Index Cards. Scene Navigator is almost worthless without the split screen. Index cards you either dig or you don’t. (I don’t.)