John August

Screenwriting Software

Taking notes

Episode - 86

Go to Archive

Apps, Film Industry, Formatting, QandA, Screenwriting Software, Scriptnotes, Transcribed, Treatments

Craig leads the discussion on how to survive a notes meeting. As screenwriters, our instinct is to defend, deny and debate — but these are almost always the wrong choice. By reframing the discussion about the movie rather than the script, you can often end up at a better place.

From there, John opens the listener mailbag so we can answer questions about cheating scene description and romantic obsession. Plus we talk about Slugline, Highland, Final Draft and the plethora of screenwriting apps available to screenwriters today.

LINKS:

* [Slugline](http://slugline.co/)
* [Highland](http://quoteunquoteapps.com/highland/)
* [Fade In](http://www.fadeinpro.com/)
* [Final Draft](http://www.finaldraft.com/)
* Screenwriting.io on [page numbering and other basic formatting](http://screenwriting.io/what-is-standard-screenplay-format/)
* Tweet your clams to [@johnaugust](https://twitter.com/johnaugust) and [@clmazin](https://twitter.com/clmazin) with #CutItOut
* [Scriptnotes, episode 52](http://johnaugust.com/2012/grammar-guns-butter) featuring Go Into The Story’s list of dialogue clams
* [Rentrack](http://www.rentrak.com/) and [BroadwayWorld](http://broadwayworld.com/)
* [The Boys in the Band](http://www.amazon.com/dp/B001CQONPE/?tag=johnaugustcom-20) on Amazon
* [Internet K-Hole](http://internetkhole.blogspot.com/2013/01/dead.html?zx=87aad0c98be70c6c) (Warning: NSFW!)
* [Sleep No More](http://sleepnomorenyc.com/) NYC
* [Slacker Radio](http://www.slacker.com/)
* How to [submit your question](http://johnaugust.com/ask-a-question)
* OUTRO: [Obsession](http://www.youtube.com/watch?v=o4wM9w79_YI) cover by TERMINATRYX

You can download the episode here: [AAC](http://traffic.libsyn.com/scriptnotes/scriptnotes_ep_86.m4a).

**UPDATE** 4-28-13: The transcript of this episode can be found [here](http://johnaugust.com/2013/scriptnotes-ep-86-taking-notes-transcript).

Final Draft Reader’s limited view

Apps, FDX Reader, Highland, Screenwriting Software

Late last week, Final Draft released a new version of [Final Draft Reader](https://itunes.apple.com/us/app/final-draft-reader/id497421221?mt=8), adding support for iPhones to their heretofore iPad-only app.

From a basic design standpoint, their iPhone implementation is almost identical to what we did with [FDX Reader](https://itunes.apple.com/us/app/fdx-reader/id437362569?mt=8), using a continuous scroll rather than page-flipping to accommodate the smaller screen. I won’t break out the old imitation-is-flattery bromide; it’s simply the right choice given the situation.

Unfortunately, you’re going to be scrolling a lot with Final Draft’s version, because they insist on using traditional Courier. It’s a mistake. You simply can’t fit very much on the screen using that font.

Compare [two screenshots](http://johnaugust.com/Assets/fd-v-fdx-72.jpg) from Frankenweenie:

iphone screenshots

Like FDX Reader, Final Draft Reader allows you to reduce the font size. By doing so, you can fit the same amount of Frankenweenie on the screen. But you probably wouldn’t like the [results](http://johnaugust.com/Assets/smaller-fd.jpg):

smaller final draft screenshot

Final Draft Reader isn’t trying to match printed pages like it does in portrait view on the iPad, so there’s simply no good argument for sticking with Courier for this “Reader View.” It’s just bad design.

Being an official product, the app provides “100% accurate Final Draft pagination, formatting and page breaking.” That’s like saying only Coca-Cola can provide pure Coke flavor, but fine.

Their app can do several things FDX Reader doesn’t even attempt, such as editing ScriptNotes and showing colored page revisions. You can link to your Dropbox account, but only for exporting files *from* the app, so it’s not particularly useful. That’s consistent with a lot of what I found: placeholders and possibilities rather than actual utility.

Final Draft Reader is now free. That makes sense; they want users to pay for the $50 Final Draft Writer app.

We’ll keep selling and supporting FDX Reader as an alternative, but as I wrote [back in February](http://johnaugust.com/2012/pricing-fdx-reader), we’re not actively developing it anymore. Our next projects include more ambitious efforts like [Highland](http://quoteunquoteapps.com/highland/).

Writing screenplays with Scrivener and iA Writer

Apps, First Person, Fountain, Highland, Screenwriting Software

A reader named Gerry wrote in to share his screenwriting workflow, which uses [Fountain](http://fountain.io) as a bridge between Scrivener, iA Writer, Dropbox and Highland.

—

first person[iA Writer](http://www.iawriter.com/) is my favorite application to write in because of its minimalist UI and Focus Mode. I just wish it had features similar to [Scrivener’s](http://www.literatureandlatte.com/scrivener.php) Binder and Compile. I love the flexibility of having one scene or one sequence per document and organizing them within Scrivener’s Binder — as was [described so well](http://prolost.com/blog/2010/6/17/the-state-of-screenwriting-software.html) by Stu Maschwitz on Prolost.

Fortunately, Fountain lets me leverage both iA Writer and Scrivener.

I write scenes in iA Writer using Fountain syntax, saving them as plain text files in a [Dropbox](http://dropbox.com) folder. I can then work with them using iA Writer on a Mac, iPad, or iPhone, which is handy.

iA Writer is perfect for scenes, while Scrivener is great for the bigger script.

Because Fountain files are plain text, Scrivener is happy to handle them. I use Scrivener’s “Sync > with External Folder…” command to build a binder for the script, which maintains a link to those original files.

scrivener screenshot

(I prefer working with a minimized Scrivener UI. I “borrowed” icons from the Storyist application to customize Scrivener’s Binder.)

Meanwhile, iA Writer still sees the individual files. If I edit them, those changes appear within Scrivener after the next “Sync > with External Folder…”

iawriter screenshot

Using Scrivener’s “Compile…” command, I can then export a group of Scene and Sequence documents as a single plain text Fountain file.

With [Highland](http://quoteunquoteapps.com/highland), I can then convert that Fountain file to PDF or Final Draft.

—

Gerry’s workflow is more complicated than many screenwriters would prefer, but I like that he’s using the tools he wants for each part of the process. Rather than being boxed in by one monolithic app, he’s taking the best of various apps.

With Fountain, we’ve worked hard to keep the format as agnostic as possible. Scrivener and iA Writer didn’t have to add support for Fountain, because they’ve always had it.

Some upcoming apps will do more with the format — using its built-in notes and sectioning, for example — but even the most basic text editors can do 90% of what you’d want.

For now, Highland helps complete the loop by letting you convert to and from Fountain easily. The free public beta is still going, so if you’re curious, by all means [try it out](http://quoteunquoteapps.com/highland).

Falling in love with plain text

Highland, Screenwriting Software, Tools

Stu Maschwitz explains how blogging led him to get over his need for as-you-type formatting and [embrace plain text](http://prolost.com/blog/2012/7/16/gradually-falling-in-love-with-plain-text.html):

> I’d often find myself battling that little WYSIWYG text window. I’d press Return after some quoted text and it would create another quoted paragraph. I’d press the “quote” button to un-quote the current paragraph, and an extra line would be inserted. I’d try to delete it and now there was no separation between the paragraphs. I’d press “Publish” and the extra line would be back.

> I’d eventually go into the post HTML and try to remove the offending line break, crossing my fingers that I wasn’t destroying something else in the process. After all this, I’d be afraid to touch the WYSIWYG editor again. A typo or broken link would have to be pretty important for me to risk touching this house of HTML cards I’d created.

For his blog, the solution was [Markdown](http://daringfireball.net/projects/markdown/). For screenwriting, the solution ultimately became [Fountain](http://fountain.io), our joint spec for writing screenplays in any old text editor.

Tools like Markdown and Fountain don’t replace dedicated apps, which can do sophisticated things that would otherwise be very difficult. But too often we’re trying to do too much too soon.

If you’re fighting to get Final Draft to recognize a parenthetical, you’re no longer writing. You’re formatting. You’re a poet picking fonts. You’re a novelist worrying about hyphenation.

Plain text keeps you from worrying about the wrong things at the wrong time.