Guest Blog: A Final Cut Pro workflow for editing in another languagePosted on May 7th, 2012 No comments
Finding the right workflow for a project can be a challenge, especially when you have multiple languages, multiple tools, and multiple collaborators in the mix. In our latest guest blog, Chad Braham, an editor and Director of Media Production at WORDonCancer.org describes in very helpful detail how they’ve developed a translation workflow that starts from Final Cut Pro and ends back in Final Cut Pro with a full resolution subtitled version that enables him to edit the film in a language that he doesn’t speak.
Got an interesting story about how you’re using InqScribe? Please contact us at firstname.lastname@example.org if you’d like to highlight your work.
by Chad Braham, Editor, Director of Media Production, WORDonCancer.org
WORDonCancer.org is a 501(c)3 non-profit organization based in Indianapolis, IN, that aims to educate and raise awareness about women’s cancer.
This summer, our organization is working on a documentary short film about a cervical cancer prevention program in the Peten region of Guatemala, entitled, “No More <http://nomorethemovie.com/>. Due to the location of where the film was shot, a large portion of the footage needs to be translated and subtitled (from Spanish to English) for the final piece.
Much of this translation is currently being done by a small group of volunteers, most of whom have little to no subtitling/transcription experience. Because of this, we needed a solution that was easy to learn and use, was available on multiple platforms (PC and Mac) and could work within our Final Cut Pro 7 video editing workflow.
As you probably already know, Inqscribe <http://inqscribe.com/> does all the above and more. As the editor of this film, I must say that I don’t speak much spanish, so it was critical that our translation workflow start and end with Final Cut Pro. With Inqscribe I can edit spanish speaking interviews, in Final Cut Pro, with subtitles, and find sound bites and edit points as if I were editing an english speaking interview. Our typical workflow is as follows:
1. Export a clip of spanish speaking footage from Final Cut Pro as a small reference video file with a timecode window burned in. In an attempt to keep the physical file size small (and the duration short for our volunteers) we usually keep the file to around 7 minutes long (a 320×180 Quicktime file at Photo-JPEG with “Medium” compression seem to play-back better then “.mp4″ files on slower PC machines).
2. Upload the file to our FTP site or Google Drive (depending on the volunteer’s preferences) and notify the volunteer with an email that also includes a few notes about the file (who the person speaking is, why we chose to talk to them, etc.)
3. Volunteer transcribes in Inqscribe and breaks up the transcription into phrases with timecode for subtitling exports.
4. The volunteer then emails over just the “.inqscr” file, that the video editor opens in his copy of InqScribe, makes a few adjustments to ensure it adheres to basic subtitling best practices (amount of text per subtitle, etc.), and then exports out an XML from InqScribe for Final Cut Pro import.
5. The XML export is then imported into Final Cut Pro and sync’d to the full-rez version of the translated clip. This is really the beauty of translating and transcribing with Inqscribe, the translation is already broken into full-resolution subtitling text “slides” in FCP and can be edited further without any quality loss to the video or text.
One of the biggest challenges of producing any documentary, is organizing the massive amounts of footage and material, into a compelling story. This is especially complicated when a good portion of the material you are working with is in a foreign language. Luckly, there is a software like InqScribe that is so easy, anyone can use it.
You can learn about this film at the film’s website www.nomorethemovie.com.Feature, Subtitles, Workflow documentary film, export, FCP, film, Final Cut Pro, import, language, transcribe, translation, Workflow, xml