Keyboard Shortcuts for Film Editors

One of our customers, a professor at a film school, suggested this tip:

For those of you used to using industry standard editting software like Final Cut and Avid, you can map “j”, “k”, and “l” with modifier keys to back/pause/forward.  Since you need the j/k/l keys for actually inputting text during transcription, you’ll need to use modifier keys (Ctrl, Command, etc.).

On the Mac you would use the “Command” and “Option” keys to set up something like this:

• Command-j => Play Backwards at Custom Rate 1.x
• Command-Option-j => Play Backwards at Custom Rate 2.0x
• Command-k => Pause
• Command-l => Play at Custom Rate 1.x
• Command-Option-l => Play at Custom Rate 2.0x

In Windows you would use the “Ctrl” and “Shift” keys to set up something like this:

• Ctrl-j => Play Backwards at Custom Rate 1.x
• Ctrl-Shift-j => Play Backwards at Custom Rate 2.0x
• Ctrl-k => Pause
• Ctrl-l => Play at Custom Rate 1.x
• Ctrl-Shift-l => Play at Custom Rate 2.0x

You can obviously tweak these to suit your workflow.

Note that by setting Command-l/Ctrl-l to “Play at Custom Rate 1.x” you can toggle back and forth between the fast speed and the slow speed.  If you set it to “Play” instead, hitting Command-l/Ctrl-l would only continue playing at the current play rate.  So if you’re already at 2.x, the play rate won’t change.

An alternative approach would be to set Command-Option-l/Ctrl-Shift-l to “Change Play Rate” by 1.x.  Then every time you hit Command-Option-l/Ctrl-Shift-l the play rate would increase to 2.x, 3.x, etc..  And you can hit Command-l/Ctrl-l to get back to the 1.x rate.  This would more emulate the behavior of FCP.

For instructions on how to set up shortcuts: http://www.inqscribe.com/docs/keyboardshortcuts.html

Comments are turned off in this blog, but head on over to our Facebook page for to leave comments: http://www.facebook.com/InqScribe

Guest Blog: Using InqScribe with Final Cut Pro and multiple languages

InqScribe’s ability to export transcripts to Final Cut Pro has made it particularly useful for documentary filmmakers working in multiple languages.  In this latest guest blog, part of our ongoing series highlighting how folks use InqScribe, Carlos Sandoval, an award-winning filmmaker, talks about how they’re using it with their latest project.

Got an interesting story about how you’re using InqScribe? Please contact us at info@inquirium.net if you’d like to highlight your work.

The Arizona Project

We are currently working on a feature documentary tentatively titled THE ARIZONA PROJECT. The film takes on Arizona’s current struggle with illegal immigration and presents it from all sides of the issue: from the perspective of the recent immigrants, to that of native Arizonans who are seeing their communities change. Because we are dealing with material in both English and Spanish, InqScribe has been invaluable for our editorial and post production tasks.

InqScribe allows us to quickly and easily access our footage and to create time code specific documents that will reference said footage. This allows us to best isolate the material that will shape our story. We can create transcriptions of our interviews in English, and translations of those in Spanish. Even more importantly, we can create subtitles in InqScribe that quickly and easily get imported into Final Cut Pro saving us (literally) hours and hours of time. This versatility is instrumental for a project like ours.

Thank you for making such a great product and for helping to bridge the gap between Spanish and English speakers. I wish we’d have had InqScribe when we were working on our award-winning film, Farmingville.

Carlos Sandoval

Camino Bluff Productions, Inc.
752 West End Ave., 2F | New York, NY 10025
p. 212 666 3266 | f. 212 864 4313
mail@caminobluff.com | www.CaminoBluff.com

Guest Blog: How documentary filmmakers transcribe and subtitle with InqScribe

InqScribe has many different kinds of users. But the majority of our users can be categorized into three groups: university researchers, professional transcriptionists, and documentary filmmakers.

To highlight how our folks are using the tool, we would like to do an occasional feature where we invite our users to be guest bloggers.

Here’s our first guest blog from a pair of award-winning documentary filmmakers. We were particularly interested in how they might be using InqScribe as part of their translation and transcription workflow, so we asked them to elaborate:

—

DigAllMedia

By Dianne Griffin and Erica Jordan

Digall Media, a 501(c)(3) organization founded by Erica Jordan and Dianne Griffin is currently in production on their one-hour documentary Painted Nails – a Vietnamese immigrant story of exotic nail art, pampered clients, and the serious health risks that lurk beneath the brightly painted surface.

We’re excited about using Inquirium’s product InqScribe to transcribe dialogue and create English subtitles for our Vietnamese and Spanish speaking characters. We’re still fine-tuning the workflow of importing subtitles, generated with InqScribe, into Final Cut Pro. It took some time to figure out the importing and exporting specs, but it was worth trouble-shooting. We can now transcribe dialogue in InqScribe with timecode, export it as an XML file using a custom FCP XML template. When the XML file is imported into Final Cut, the subtitles (as text elements) magically appear on a new timeline. InqScribe’s support page offers to look at your files to help trouble-shoot subtitling issues. InqScribe works great with a foot pedal, saving valuable post-production time.

Filmmaking is hard enough; it’s great to find a product such as InqScribe to make it easier.

Please contact us at info@inquirum.net if you’re interested in highlighting your work.

Workaround for Final Cut Pro 7 Importing Bug

Update: this bug is fixed in the 2.1 beta. Get the beta here.

If you’re using Final Cut Pro 7 and importing InqScribe-generated FCP XML files, you’re probably pulling your hair out. As of FCP7, any imported subtitles beyond the two minute mark show up with a duration of only one frame.

The problem is twofold. First, InqScribe is setting incorrect values for the in and out points for each generated subtitle. In prior versions of FCP, these values were essentially ignored on import, because in and out points for a static subtitle don’t really mean that much. (The start and end points for the subtitle, which determine where the subtitle goes in the sequence, were and are correct.)

Unfortunately, FCP7 is interpreting those values differently, and any subtitle with an in point greater than the subtitle’s stated duration ends up with a frame length of 1. Since InqScribe was setting every subtitle’s duration to 3600 frames (because this value shouldn’t really matter: effective duration of the subtitle is based on the start and end values), most users will find that subtitles that start at the two minute mark or later are affected.

We’re working on a fix for the next beta release. In the meantime, there is a workaround.

Here’s an excerpt from an InqScribe-generated FCP XML file:

<generatoritem id="Text">
    <name>Text</name>
    <duration>3600</duration>
    <rate>
        <ntsc>TRUE</ntsc>
        <timebase>30</timebase>
    </rate>
    <in>7540</in>
    <out>7610</out>
    <start>7540</start>
    <end>7610</end>

Note that InqScribe sets the duration to 3600 (regardless of the actual duration, which is based on the start and end values). InqScribe also sets the in and out points to the start and end values. The problem is that in and out values should technically never be greater than the duration.

So the fix is to change every instance of in and out to this:

<in>100</in>
<out>3600</out>

With this change, in and out stay within duration’s range, and FCP7 won’t clip the resulting subtitle.

To make this change easily, use a tool that supports regular expressions to find all instances of the in and out tags. Here’s a solution that uses sed, which comes installed on OS X.

1. Export the FCP XML file from InqScribe as usual (let’s say it’s called export.xml).
2. In the Terminal, navigate to the directory containing export.xml, and issue this command (which is one long line, make sure to copy the whole thing):

sed -e 's_\(<in>\)[0-9]*\(</in>\)_\1100\2_g' -e 's_\(<out>\)[0-9]*\(</out>\)_\13600\2_g' < export.xml > export_fixed.xml

3. Import the resulting export_fixed.xml into FCP7.

If you want to dig into sed so you understand what that command is doing, here’s a solid sed tutorial. It’s a very powerful tool.

Exporting NTSC DF to Final Cut Pro

There’s a bug in InqScribe 2.0.5 that affects FCP XML exporting. Currently the bug only affects exports that use XML templates that are based on NTSC DF.

The bug is that InqScribe is counting the dropped frames when it converts from the timecode to a single frame count number. As a result, the converted time codes will drift farther and farther from where they should be, the later in the movie you go.

There is a workaround that you can use until we fix the problem.

Update: turns out the workaround didn’t work. Drat. But the good news is that we’ve fixed the underlying problem in InqScribe 2.1. A public beta can be found here.

Read the rest of this entry »