{"id":886,"date":"2014-05-22T18:48:09","date_gmt":"2014-05-22T22:48:09","guid":{"rendered":"http:\/\/blogs.inquirium.net\/inqscribe\/?p=886"},"modified":"2014-05-22T18:48:09","modified_gmt":"2014-05-22T22:48:09","slug":"guest-blog-a-filmmaker-uses-inqscribe-for-translations-and-subtitles","status":"publish","type":"post","link":"https:\/\/blogs.inquirium.net\/inqscribe\/2014\/05\/22\/guest-blog-a-filmmaker-uses-inqscribe-for-translations-and-subtitles\/","title":{"rendered":"Guest blog: A Filmmaker Uses InqScribe for Translations and Subtitles"},"content":{"rendered":"

InqScribe is popular among filmmakers for a variety of reasons. In our latest guest blog, Scott Squire shares his workflow to translate and create subtitles for his documentary.<\/em><\/p>\n

by Scott Squire, Independent Producer & InqScribe user<\/strong><\/p>\n

Our movie, The Girl Who Knew Too Much<\/em> is a feature documentary about women\u2019s empowerment, the complexities of globalization\u00a0and the crisis of mental health support in Nepal.\u00a0We shot our movie over seven years on six different cameras, with varying degrees of asset management rigor. We ended up with nearly 200 hours of footage to be logged and\/or translated and subtitled. This project taught us the value of having solid workflows\u2014from managing footage in the field through the process of translation. We cannot stress the importance of having a process (that works with every camera!) before you shoot a single frame.<\/p>\n

\"\"
Our translators at work<\/figcaption><\/figure>\n

Our workflow includes the use of InqScribe<\/strong> and Final Cut Pro<\/strong> to produce translations and final subtitles for our movie. Critical to our process is having a clear folder\/file structure that essentially depicts our workflow. I will refer to the folder\/filenames used on our project, but obviously these would change based on your own project details.<\/p>\n

\"\"
Folder structure to organize our workflow<\/figcaption><\/figure>\n

Set up<\/h3>\n

We make sure that the top-level directory is accessible from all of our workstations. Our workflow begins with our editor placing callouts for the media that needs translating in the folder called In1. Fiona Highlighted Documents<\/strong>. Sometimes these are snippets from a clip, sometimes a whole reel. She reads our transcripts and highlights them, and then sends us scans of the highlighted pages as PDFs. (Unfortunately, on this project, we didn\u2019t have InqScribe at the start, which means our original transcripts were in a variety of formats.)<\/p>\n

Review the translation and verify timecode in InqScribe<\/h3>\n

We assemble all of the relevant translated files and then create an InqScribe document for each clip<\/strong>. Our workflow involves moving the InqScribe transcripts through a series of reviews by native speakers who verify the accuracy of the translation and the placement of timecodes. Timecode references should be at least at 10-second intervals (we recommend every 4-5 seconds). Be careful with InqScribe\u2019s sensitive timecode selection so that you don\u2019t timecodes out of order. And be sure to have opening AND closing timecodes in InqScribe or else your subtitles will run too long.<\/strong><\/p>\n

Export XML file from InqScribe to Final Cut Pro<\/h3>\n

Once the translation is complete and the timecodes are reviewed, we use InqScribe to export an XML file to be used in Final Cut Pro<\/strong>. It\u2019s good to keep your XML template easy to access because you\u2019ll be using it a lot. We keep ours at the top-level folder of our shared directory: \/Master Wrapping Subtitle Template v1.3 (use this one).xml.<\/strong>
\n<\/em><\/p>\n

Instructions for creating a custom FCP 7 XML export template can be found in InqScribe\u2019s Knowledge Base.<\/a><\/em><\/p>\n

Very important is the naming of files. InqScribe will show the default name as \u201cexport.xml.\u201d Click the \u201cChoose\u201d button to select a destination to save the file. Navigate to \/Out2. Subtitle XMLs for Final Cut Pro > Interview XMLs from InqScribe<\/strong>. The name of the XML needs to match the file it came from. The best way to do this is to navigate to the original InqScribe file, select and copy the name (all but the \u201c.inqscr\u201d extension) and paste this into the pane of the export dialog. Double check your naming and destination\u2014this is a big pain if you get it wrong. CONSISTENCY and ACCURACY in naming and filing are CRITICAL.<\/p>\n

If you\u2019re lucky, when you click \u201cExport,\u201d the export window will just close and your shiny new XML file will turn up in the proper place. If InqScribe alerts you to a non-consecutive timecode you will need to go back and correct where needed. The error will only tell you approximately where to start fixing first. Cancel out and go back to check all of the timecodes where the error message is indicated.<\/p>\n

Import XML files to Final Cut Pro (FCP)<\/h3>\n

In Final Cut Pro, you will create a project (Subtitle_Master_Project<\/strong>) and import the first InqScribe XML file in the scene you just created. When you import the InqScribe XML, it will come into FCP as a sequence with the generic name that matches your text generator template (Master Wrapping Subtitle Template\u2026<\/strong>). You must change this back to the name of the original file. As before, navigate back to the file and copy and paste the name in the FCP browser to replace the template name.<\/p>\n

Drag the newly imported sequence into the timeline. It will contain only a subtitle track. Next, import the associated master footage or locate the clip and drag it into the FCP browser window. When the media clip has been imported, be sure it\u2019s in the right folder inside the browser. Drag the clip into the timeline so that you have both footage (video and audio) AND a subtitle track above the video. These should be the same length, but there may be gaps in the transcription file. If the closing timecode was correctly input in the InqScribe file, the endpoint will match the end point of the media.<\/p>\n

If you\u2019ve done your job in InqScribe, the clip lengths should all match up and you\u2019ll have a subtitled sequence! You can now export the sequence from Final Cut Pro as a XML to send to your editor.<\/p>\n

\n

\"\" About the author
\n<\/strong><\/p>\n

Scott Squire is a filmmaker who, along with his wife Amy Benson, is the producer of The Girl Who Knew Too Much<\/em><\/a>.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"InqScribe is popular among filmmakers for a variety of reasons. In our latest guest blog, Scott Squire shares…\n","protected":false},"author":8,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,5,7,9,11,13],"tags":[69,109,111,114,116,117,193],"_links":{"self":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts\/886"}],"collection":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/comments?post=886"}],"version-history":[{"count":0,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/posts\/886\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/media?parent=886"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/categories?post=886"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.inquirium.net\/inqscribe\/wp-json\/wp\/v2\/tags?post=886"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}