{"id":14686,"date":"2013-05-15T09:58:24","date_gmt":"2013-05-15T14:58:24","guid":{"rendered":"http:\/\/mediastorm.com\/blog\/?p=14686"},"modified":"2013-05-15T09:58:24","modified_gmt":"2013-05-15T14:58:24","slug":"mediastorm-guide-to-creating-subtitles-in-premiere-pro-2","status":"publish","type":"post","link":"https:\/\/www.mediastorm.com\/blog\/2013\/05\/15\/mediastorm-guide-to-creating-subtitles-in-premiere-pro-2\/","title":{"rendered":"MediaStorm Guide to Creating Subtitles in Premiere Pro"},"content":{"rendered":"

This article is part of a new series of posts<\/a> with tips and tricks from our producers’ experience working with Adobe Premiere Pro<\/a>\"\" after years of working in Final Cut Pro. To read more about why we made the switch, check out this post<\/a>. <\/em><\/p>\n

Today’s post was written by MediaStorm producer Eric Maierson<\/a>.<\/p>\n

\n

There\u2019s a critical difference between the title tool in Final Cut Pro and Adobe Premiere Pro. In FCP, one could slice a title that\u2019s already in the timeline, open it in the Viewer window, then change the contents so that you now had two distinct titles.<\/p>\n

This does not work in Premiere Pro.<\/p>\n

In Premiere Pro each title is a distinct instance. So, if you splice a title in the timeline then change its content, you will also change the content of the first title as well. Both titles will say the same thing.<\/strong><\/p>\n

The only way around this is to create a new title instance for every subtitle. It\u2019s a cumbersome process and one that we wish Adobe would change.<\/p>\n

Setting Up a Title Template<\/h2>\n

In the Project window create a new bin (Command – \/)<\/strong>. Name it Subtitles<\/strong>.<\/p>\n

Open the title tool (Command-T)<\/strong>.<\/p>\n

In the New Title<\/strong> window, name the title temp<\/strong>. The title size will default to your current sequence size.<\/p>\n

\"\"<\/a> \"\"<\/p>\n

When the title tool opens, press T<\/strong> for the Type Tool<\/strong>, then click inside the rectangle. Use 38pt Arial<\/strong>, then type a short phrase<\/strong>. If you plan to use drop shadow, and you should, add it here as well. (Tim McLaughlin<\/a> will follow up this post with a more detailed look at the functionality of the Title Tool.)<\/p>\n

Next, click the Selection<\/strong> tool (arrow icon)<\/strong> and move the title so that it rests on top of the title-safe line.<\/p>\n

\"\"<\/a> \"\"<\/p>\n

Use the Horizontal Center<\/strong> tool to align the title in the middle of the screen.<\/p>\n

\"\"<\/a>\"\"<\/p>\n

Close the title tool.<\/p>\n

Drag<\/strong> the title from Project<\/strong> window to your Timeline<\/strong>.<\/p>\n

To create a new<\/strong> title, simply click the New Title Based on Current Style<\/strong> button at the top right of the Title tool.<\/p>\n

\"\"<\/a> \"\"<\/p>\n

XML<\/h2>\n

At MediaStorm we no longer use burned-in timecode. We use XML to generate titles in our player<\/a>.<\/p>\n

If you plan to use XML with your subtitles for any reason, say to copy from one computer to another, the following steps are crucial:<\/p>\n

Each time you paste a phrase from your transcript into a subtitle, you must also rename the subtitle instance with the exact same phrase.<\/strong><\/p>\n

If the contents of the subtitle is \u201cI went home\u201d the name of the subtitle instance must also be \u201cI went home\u201d; the names must match identically. That\u2019s because XML in Premiere Pro reads the name of the title, not its contents.<\/strong><\/p>\n

\"\"<\/a> \"\"<\/p>\n

Here too, we wish Adobe would change this behavior so that XML functioned as it does in Final Cut Pro 7, reading the content of the subtitle, not the name of the title file \u2013 the opposite of how it works now.<\/p>\n

It\u2019s obviously more expedient to avoid this extra step.<\/p>\n

Subtitle Styles<\/h2>\n

Font Size – 38<\/p>\n

Font – Arial<\/p>\n

Drop Shadow – Standard effect, change opacity to 90%<\/p>\n

Fades<\/h2>\n

If narrative is more than 15 frames from the end or beginning of a cut, set subtitle to start 10 frames before the start or end of narrative, then place 8 frame fade on subtitle.<\/p>\n

\n

To learn more about how our producers are using Adobe Premiere Pro<\/a> see our other blog posts on the topic<\/a>. Also, follow our producers’ twitter feed @PrProShortcuts<\/a> for Premiere shortcuts.<\/p>\n

To learn more about our production style, you can purchase a copy of our Post-production Workflow<\/a>. Readers who purchase our current Final Cut Pro and Aperture workflow automatically receive the Premiere workflow when it is released.<\/p>\n

MediaStorm offers several online and in-person training opportunities at mediastorm.com\/train<\/a>.<\/p>\n

Have you made a recent switch in your editing software? Let us know about it in the comments below.<\/p>\n","protected":false},"excerpt":{"rendered":"

This article is part of a new series of posts with tips and tricks from our producers’ experience working with Adobe Premiere Pro after years of working in Final Cut Pro. To read more about why we made the switch, check out this post. Today’s post was written by MediaStorm producer Eric Maierson. There\u2019s a […]<\/p>\n","protected":false},"author":9,"featured_media":14687,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,748],"tags":[1231,927],"class_list":["post-14686","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-editing","category-tutorials","tag-adobe-premiere-pro","tag-subtitles","entry","has-media"],"_links":{"self":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/posts\/14686","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/comments?post=14686"}],"version-history":[{"count":0,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/posts\/14686\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/media\/14687"}],"wp:attachment":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/media?parent=14686"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/categories?post=14686"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/tags?post=14686"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}