A Long Weekend of Short Filmmaking at William & Mary: Pt. 2

Saturday morning at William & Mary began with Troy Davis giving Ashley and me a tour around the William & Mary's Swem Library Media Center. The Director of the Media Center, Troy was my host for the weekend and one of the primary organizers of the Media Center's Long Weekend of Short Filmmaking. The Media Center is several things in one -- an equipment training center, an equipment check-out center, a recording studio for music and podcasts. It's anything and everything that students want and Troy makes himself, and his assistants, available to students to teach them anything from iMovie to Logic Pro.

Troy has been the Director of the Media Center for a year and a half, and it's impressive what he's accomplished. On a technical level, he's helped secure some superb editing facilities (several Mac tower stations with Final Cut, Logic Pro, and the rest of the works, each in its own sound controlled environment). For a guy who describes himself as a "dabbler" when it comes to film, I was impressed with all the smart technology purchases he has been making, not to mention his ability to talk in depth about the subtle differences between various pieces of equipment they own.

Since there are, no doubt, places like this at universities across the country, the biggest accomplishment isn't the equipment and stations he's amassed -- it's the sense of community generates out from this media hub. A lot of that, no doubt, is due to Troy's vision for the Media Center as a place that is accessible and inviting (as opposed to exclusive and intimidating). The Media Center, in fact, is littered with Troy's self-desribed "propaganda" -- humorous, well-designed posters -- that invite students into the space and use the equipment.

After the tour, Troy and I recorded a podcast that covered making and teaching film. He had thought a lot about my work and had some great questions, which is really flattering. (The podcast will be posted at some point on Media Center site. I'll link to it when it's available.)

The podcast led into a "self-reliant filmmaking" workshop that I conducted with some of William & Mary's film students and faculty.

I began by discussing the work I do on this blog, including my reasons for starting it, and how it's transformed my own film practice. I then opened things up for discussion, which led to a wide-ranging conversation that covered everything from what video camera to purchase to some simple strategies for first-time documentarians. Ashley threw in some good advice during the conversation, to boot; I was happy she had joined me.

Our workshop group talked for nearly two hours, so Ashley and I had a quick break for lunch before I ran off to a screening of some of my own short films at the historic Kimball Theatre. The films looked good in this classy venue, I was happy with the turnout, and the questions the audience asked were, again, really good. (I even received some email from audience members after the screening thanking me for sharing my work.) There was a little reception in the theater lobby afterwards, and I enjoyed talking with some of the William & Mary faculty members that had come to the screening. That conversation led to a coffeehouse where Sharon Zuber, who teaches W&M's production courses, and I compared notes about how to teach film production.

We closed out the day by stopping by the premiere of the Cans Film Festival (pun intended), a student-organized screening of films produced at a variety of Virginia universities. (There weren't any entries from Virginia Tech -- maybe next year?) Ashley and I weren't able to stay for long -- I was beat and we had a long drive back in the morning. We did manage to catch one zombie flick before we left.

Before we left on Sunday morning, Troy treated us to breakfast at one of Williamsburg's many pancake houses. Ashley and I had seen a number of pancake houses on our drive in, and I suppose they reflect the fact that Williamsburg is a haven for retirees and a magnet for tourists (motto: "Where History Lives"). The three of us had one last movie-saturated conversation, and Troy told us about his next dream for the Media Center -- restoring an unused auditorium in the William & Mary library and making into a screening facility/microcinema.

As we drove out of town, past a few more pancake houses, I thought about a place like Wiliamsburg. Even with the occasional major production (like Malick's The New World) coming to town, it would still be surprising to see Williamsburg develop into the next Austin. Williamsburg's a town of 12,000 people, and a lot of the people are transient (whether they're tourists, college students, or retirees). That's a tough place to build a film culture. Of course these things don't only apply to Williamsburg. If this sounds like your town, too, well, so be it. It sounds like mine.

The thing is, something is happening in Williamsburg. Things like the Kimball Theatre, and the William & Mary Media Center are part of the puzzle. The "corner pieces" of that puzzle, though, are a dedicated group of people with vision, passion, and resourcefulness. That's the real lifeblood of regional filmmaking and film culture. Some places don't have this, or have enough of it. Luckily, for Williamsburg, it has Troy Davis, Sharon Zuber, Arthur Knight (coordinator of Film Studies at W&M), and a host of student filmmakers. Something tells me that their numbers will only continue to grow.

Loss of deck connectivity in Final Cut? Try reinstalling QuickTime

Normally I try to write less prosaic (or at least shorter) post titles, but hopefully this will help some Final Cut Pro or Final Cut Express users that are googling for a solution to deck connectivity problems. A few weeks ago a student came to my office nearly in tears because Final Cut Express, which she had on her iBook, wouldn't recognize her camcorder when she was trying to capture footage. In fact, most times, FCE would crash when she tried to capture footage.

We tried to isolate the problem:

Was it a connection problem? No, we tried firewire cables (including some known to work). The problem continued.

Was it a camera problem? No. We captured footage on my laptop without any issues.

Was it a computer problem? Probably not. She was able to capture footage on her computer using iMovie.

At this point we began the googling. After a while, we happened on the problem (QuickTime) and its solution (reinstalling QuickTime).

Here's Apple's article on the subject: Restoring a DV device connection in QuickTime 7.

It's worth noting that this tip also works for Final Cut Pro. And its a good reminder that a smart first place to search when encountering problems with Apple-manufactured software is Apple's own support site.

Software Update: Final Cut 5.1.3

Apple has just released an update to Final Cut Pro (5.1.3). Apple describes it as a maintenance release that "resolves performance and other issues." Specifically: Render File Capability - apparently, render files created on a PowerPCs and Intel-based Macs weren't playing nice

Keyboard Layout Issues - "adds several commands to the default keyboard that were missing"

Issues with Cross Dissolves in Nested Sequences - "resolves cases in which cross dissolves did not work as expected in nested sequences containing still images with adjusted motion parameters"

You can read more here.

Of course, as with any upgrade, you might wait and see how others are faring with the update before you upgrade yourself. The VersionTracker message board is one good place to look for this kind of feedback.

Also, if you move between different computers using the same project files make sure all the machines will be upgraded at the same time so that your files aren't rendered incompatible, as sometimes happens.

Finally, use extreme caution when upgrading software while in the midst of working on a project. I have seen nasty stuff happen to FCP projects when someone upgraded their system from, say, 4.5 to 5.0. I've even seen it happen with a "dot something" upgrade. Such a small incremental update like this (5.1.3) is probably okay. But I'm not going to guarantee it. Safety first: If things are working just dandy for you with 5.1.2, don't chance it. Finish that project, output it, archive it, and then do the upgrade.

Cool Tool: Gage-It

While at Home Depot the other day I ran across a nifty little all-in-one measurement tool called Gage-It. It allows you to measure screws and bolts; nuts; steel, brass & PVC pipe; wire size; and nails. It also has a couple of rulers (metric and standard) and a conversions table for weights and measurements. I feel like I'm always going to the hardware store trying to find a screw that's the right size for this or that thing around my house, plus it seemed like a useful thing to have with you on a film set, so I picked one up. The thing cost something like $1.99.

Gage-It

I can't even seem to find the manufacturer ("Armour Technologies, Inc.") online, much less the item itself. The only other mention I could find was at Toolmonger, from whom I grabbed the pic above. But if you're looking for one, try Home Depot. I ran across mine in the screws/nails aisle.

Finally, as an aside, writing this post made me realize that I've become so conditioned to finding products on the internet (and the internet has become so synonymous with shopping) that, when I run across something that can't be found for sale anywhere online, it seems... well, it seems weird. And by "weird" I mean conspiratorially weird, even creepy. It's like the thing doesn't exist, even though I have one right in my hands. Am I alone on this one?

Sonnet Tempo E4P Firmware Update

I realize this will have limited use for most readers, but I recently acquired a Sonnet Tempo E4P SATA card for a Mac Pro, and was having problems with it. Big problems. The computer wouldn't recognize the card, much less run the two Sonnet Fusion 500p drive enclosures I had connected). Searched around online, both on the Sonnet site and elsewhere (newsgroups, etc) for a solution. Couldn't find one. Finally, I called tech support. After 20 minutes on hold I spoke with someone. It went something like this:

TECH SUPPORT: You need to update the firmware of the card.

ME: Oh...ok. That's funny, the documentation doesn't say anything about that.

TECH SUPPORT: It should.

ME: Um.. nope.

TECH SUPPORT: Hang on.

(puts me on hold ... two minutes of elevator music later...)

TECH SUPPORT: Wow. You're right, it's not in the documentation. Uh oh.

By the embarrassment (and dread, knowing he'd be encountering a lot of calls like this) I sensed on the phone yesterday, I suspect that future versions of the documentation will have this detail added soon. Hopefully this post will help a few users until the nice folks at Sonnet can get that documentation fixed.

Users can find the Tempo E4P firmware update here.

Self-Reliant Film Store

I get a fair number of emails asking me to recommend this or that book, or asking what films constitute a "Self-Reliant Film canon" and so on. So I thought that I'd add a modest Amazon store so that I can simply point people towards books I recommend, movies I like (or want to see), and so on. You can access the store by clicking the link below and, after this post loses prominence, you can always access the store by clicking on the SRF Store in the menu bar at the top of the site, just under the banner.

Purchasing through the store will help offset the costs of server space, etc. so if you do purchase something, thanks a bunch!

Finally, if this feels crassly commercial, please note that the header of the SRF store says "Stuff to Buy or Borrow." Knowing what you need and don't need to buy are good principles of self-reliance. If you got some of these things from your local library or a friend I'm sure Thoreau and Emerson would be proud.

Click here to enter the SRF Store.

I'll be doing holiday stuff over the next week. When I return I'll be doing some posts related to a new film project of mine. Happy Thanksgiving!

Screenwriting Software

Lately I've been working on some rewrites of a short script, and I find myself dividing my time between two different screenwriting applications. I'm not sure if I'm transitioning from the old (Final Draft) to the new (Celtx), or if I'm just trying to choose between the lesser of two frustrating applications. This post is intended as a kind of sketch of what I've been encountering over the last few days in hopes that some readers might contribute some comments on how what they're choosing to use (and why). Final Draft I've been using Final Draft 6 since it was released years ago -- like '99 or 2000. For the most part, after several updates and bug fixes (version 6.0.6.0 anyone?) over the years, it's pretty stable. In the end, it does what it's supposed to -- it makes writing and rewriting scripts in "proper screenplay form" as simple as it is to type a regular text document in something like Microsoft Word. What more could you ask for? Well, a few things:

First, Final Draft has a copy protection scheme that is frustrating for the way I work. I support the rights of developers to profit off of their work, so I'm not opposed to copy protection. When I've paid for the program, though, it shouldn't interfere with my ability to do my work. Basically, Final Draft's copy protection allows for two "authorized" hard drives. The first problem with this is that it doesn't acknowledge the way many of us use computers. I, for one, have three different computers (one at the office, one at home, and one laptop). But I can only install FD on two of these. Even worse, when a drive crashes (an inevitability, really) I have to actually call Final Draft and explain that I'd like to reinstall their application on my computer. At times, with some of their tech support, I've had to lobby to them that I'm not pirating their software but there really has been a hardware malfunction.

Even worse is their technical support: You get 20 minutes free in the first 90 days of owning the program. After that it's $2.50/minute. This ranks Final Draft somewhere between my current cell phone company and the Philadelphia Parking Authority in the category of Customer Service.

Reports from other quarters that Final Draft 7 is a bugfest have kept me away from upgrading. My guess is that the reason for the bugs is that, having reached the limitations of what it can and should do in version 6, all the new, bloated features are interfering with the real reason many of us adopted the software in the beginning.

In sum, I've been grudgingly using FD6 with the suspicion that, sooner or later (because of computer or operating system upgrades), I'm either going to have to swallow hard and buy FD 7 or find a replacement.

Celtx Last weekend, then, while doing a polish of a rewrite, I made an earnest effort to make the switch to Celtx, the open source screenwriting/production application. I've written about Celtx twice before (here and here), and I've definitely been rooting for it because of the reasons listed above. In fact, after my last survey of the application, Celtx seemed ready for use.

Now, after a few days of working with it fairly rigorously, I feel like I've reversed my opinion of it again. Alas.

Among the bugs:

- I've had repeated problems with different document elements being mistakenly tagged. For example, some dialogue I've typed appears in all caps as if it's a character name. So I'll select that text and select "Dialog" [sic] to correct the problem. This fixes the selected text, but the text surrounding it -- e.g., the character speaking the dialogue is now also classified as dialog. Needless to say, this is distracting and slows down the creative process. Very frustrating.

- I've encountered odd cursor behavior. Sometimes, as I move the cursor around, it leaves a non-blinking cursor in a previous spot. Not only is this annoying, it makes you question the overall stability of the application.

- The "underline" feature still doesn't work. Not a deal breaker, I grant you, but it's a glaring bug when clicking on a menu icon does nothing.

These are elemental problems that make me inclined to continue using FD6 for the short term, at least. Beyond these basics, though, there are elements of Celtx that still make it less than ideal:

- I still dislike the obligatory introductory menu that appears each time you load the program. Especially annoying is the fact that I can't seem to erase the Celtx tutorial project from the menu even though I've deleted it from my hard drive. I'm sure there are people out there that like the menu screen, so perhaps the developers can make toggling it an option in the (under-developed) Preferences menu.

- File saving is confusing. Inside my Celtx project folders are numerous files, which is a little confusing. I want to be able to save a "Celtx" document (as I do with MS Word, or Photoshop, or any other normal application), drag it to my jump drive, and open it on another computer. Is that so wrong?

- For all of Celtx's features, you can't highlight script text in yellow (or any other color). This is an immensely useful feature in Final Draft. It allows me to draw attention to something in a draft (so I can return to it, to spotlight it for a collaborator, etc.)

- I'd like to see keystrokes in the text elements' drop down menu (e.g., "Dialogue Cmd-4").

- I want to have the option of breaking out of screenplay format. For example, if I want to type "The End" I should be able to simply center the text. (This feature would be useful, too, for the way I prefer to type out montage sequences.)

- Online sharing. As I've written in previous evaluations of Celtx, I'm not interested in sharing my work via their online servers. And I don't think PDF creation should be connected to registering with their online community. As a workaround I've simply used OS X's "Print to PDF" feature, and then used the ever-useful PDF Lab to marry my title page and script. It gets the job done, but they're needless extra steps.)

So, as of right now, Celtx feels like a case of software under-/over-development. I'd like to see the developers work out the bugs in the essential (that is, screenwriting) areas as it approaches Version 1.0, before pushing too far on the pre-production aspects of the program. The open source philosophy of the application, the general responsiveness of its developers and, admittedly, my frustrations with Final Draft have me rooting for it. Until then, I'll probably return to Final Draft 6 in hopes that Celtx will fulfill its promise soon. If it doesn't, I guess I'll be checking out Movie Magic Screenwriter, which I suspect is overpriced ($250), but works.

Until then, I've got some question for the writers out there: What are you using? Are you having the same problems? And what would you like to see?

Red Footage Posted

If you're following the development of the Red Camera (I am), you'll want to check out the footage they've posted on their recently overhauled site. Mike @ HDForIndies says that he thinks it's only 1K. And it's not terribly interesting -- some sunglasses, and steel grey at that. So what can we judge from this? Not resolution (if it's 1K) and not color or exposure range (because of the subject matter). In sum, very little. But, it's another step in the process of the design and hype of this camera -- an unusual mixture of transparency and secrecy. There are rumors that there's more footage soon to come. Hopefully that footage will be accompanied by technical specifications, not to mention some human subjects. The clip is a downloadable torrent, so you'll need a peer-to-peer application like Transmission.

Of course, if you've somehow only recently discovered filmmaking and/or the internet, you can read this earlier post to get caught up.

ADDED: Matt @ FresHDV catches you up on some of the other recent RED developments.

DIY Camera shoulder rest

Here is an Instructable for a DIY camcorder shoulder mount. The author is in Europe (Germany, maybe?), which means some of the tools and lingo in his how-to need some translation. I'm not sure the Home Depot or Lowe's carries the type of gutter holders that this guy is using, and I'm still trying to figure out what "Replacement sponge from a Plastic smoothener" [sic] is. But resourceful readers will figure out a solution in a jiffy, I'm sure.

By the way, the approximate cost was listed as 12 Euros (about $15). Compare with this one.

[Via Make]

Small Gauge Madness: Home Movie Day

August 12 is Home Movie Day. As part of the festivities, small-gauge film-related events will be held in 27 states and 6 countries this year. This is the first I've heard of it, but apparently Home Movie Day is in its fourth year. Here's some information from the website:

Home Movie Day was started in 2002 by a group of film archivists concerned about what would happen to all the home movies shot on film during the 20th century....

The Home Movie Day founders envisioned a worldwide celebration of these amateur films, during which people in cities and towns all over would get to meet local film archivists, find out about the long-term benefits of film versus video and digital media, and—most importantly—get to watch those old family films! Because they are local events, Home Movie Day screenings can focus on family and community histories in a meaningful way. They are also an education and outreach opportunity for local archivists, who can share information about proper storage and care for personal films, and how to make plans for their future.

Great stuff. If you happen to go to one of the events, post a comment and let us know how it went. My ladyfriend and I are hoping to attend the one in Richmond.

On a related note, if you've got a lot of 8mm or Super-8 movies that you need to have transferred to video, check back tomorrow.

Hello, Dolly

Yeah, yeah, even I groaned at the title to this post. But hey, it's no worse than the title of the article I'm linking to, is it? Studio Daily's, ahem, "Roll With It" article covers all the means of moving your camera that were announced at NAB this year. If you can move past the puns (sorry, another one!) you'll find some interesting stuff. From what I can tell by the photos, my favorite is the Scooter Shooter. It's an equipment cart that doubles as a dolly once you've unloaded it. Great for small crew shoots. The $2600 price tag seems a little much, but it's about $2000 less than what a Matthews doorway dolly willl set you back. The concept is a 10, though, and I'm sure enterprising DIYers out there could build this thing for about $200. If you do, let me know and I'll post (or link to) your findings.

In the meantime, if you want to move your camera like Murnau or Resnais, check out the dollies.

[Via DV Guru]

Shotgun Mics vs. Hypercardioid Mics

I was shopping online for microphones today -- reading reviews, checking prices, etc. One of the best things I ran across in my research was Ty Ford's helpful website. On it, there are a number of reviews and tutorials. One of the best videos on his site is a comparison of four different mics, which does a nice job of explaining the difference between shotgun and hypercardioid microphones.

The movie takes a little while to load, so be patient. And wear headphones. Without them, the nuances of the differences between microphones will be lost...and nuances are what this is all about.

Click here to watch it.