{"id":56406,"date":"2015-05-18T10:00:42","date_gmt":"2015-05-18T15:00:42","guid":{"rendered":"http:\/\/www.premiumbeat.com\/blog\/?p=56406"},"modified":"2015-05-18T10:44:47","modified_gmt":"2015-05-18T15:44:47","slug":"three-quick-tips-for-editing-in-premiere-pro","status":"publish","type":"post","link":"https:\/\/www.premiumbeat.com\/blog\/three-quick-tips-for-editing-in-premiere-pro\/","title":{"rendered":"Three Quick Tips for Editing in Premiere Pro"},"content":{"rendered":"

Problem solving leads to new skills. Here are three things I’ve learned recently while editing in Premiere Pro.<\/h2>\n

Every now and then, in the midst of a busy editing day, I’ll have to solve some tiny problem and, in the process, learn something new<\/strong> about the program I’m in. Recently,\u00a0I’ve learned these three things about working in Adobe Premiere Pro<\/strong>, which may not be new to you, but they were news to me. Hopefully, they’ll be useful to a few other people too.<\/p>\n

How to Move Audio Keyframes With Keyboard Shortcuts<\/h3>\n

\"Editing<\/p>\n

I love editing with a Wacom tablet<\/a>, and most of the time things run pretty smoothly, except for a few important occasions within Premiere Pro<\/strong>. The main problem is that doing anything that requires precision seems to never work quite right.<\/strong><\/p>\n

And, by the way, I never had these problems in FCP7, so it’s not the tablet! For example, I find clicking and dragging on numbers (such as the position controls in the Effects Control tab, which should act like sliders) pretty tricky. I’ll click and drag and let go<\/strong> and the number won’t be quite where I left it.<\/p>\n

Another example has to do with audio keyframes<\/strong>. When trying to reposition them in the timeline, they almost always either stick in a wrong position, or ping away when I release the pen tip. This is very frustrating, especially when you’re mixing in a hurry. Thankfully, it’s pretty simple (and probably faster) to adjust these keyframes on the fly with keyboard shortcuts<\/strong>.<\/p>\n

In the default keyboard mapping, simply select the keyframe and press [ to increase the volume, or ] to decrease.<\/strong> Personally I’ve mapped these to CMD+Up Arrow and CMD+Down Arrow<\/strong>. Then, when you’re playing through the sequence, you can adjust the keyframe level while listening along.<\/p>\n

One thing I have found, however, is that sometimes the meters (and\/or the playback volume) might not update until you playback through the sequence a second time.<\/strong> This is annoying.<\/p>\n

How to Find out Which Font Has Been Replaced in Premiere<\/h3>\n

\"Editing<\/p>\n

Inevitably you open up a client’s project on your computer and find that the font used in all the important text elements has been replaced by Premiere<\/strong>, because the real font is not installed on your computer. So how do you find out what the font was before Premiere replaced it?<\/p>\n

Well, the Title Designer isn’t any help at all, nor is the metadata of the text element itself. What you need to do is click on the tiny warning triangle in the very bottom right hand corner of the Premiere Pro interface<\/strong> (image above). It will open up the Events window\u00a0(image below) which will tell you what the original font was and what Premiere has replaced it with. Phew!<\/strong><\/p>\n

\"Missing<\/p>\n

Now all you have to do is source the font, install it, restart Premiere, and the text elements will be back to the way they should have been.<\/strong> The Events window is also a handy place to look if other things go wrong too.<\/p>\n

How to Copy Finder File Path to Import Window<\/h3>\n

This tip is for those times when you’ve navigated to some obscure folder, deeply routed in the file system of your client’s remote storage in the Mac OSX Finder, and you don’t want to have to do that journey all over again while importing files into Premiere. Simply drag the folder from Finder into the import window<\/strong> and it will open up the file path in a jiffy. If that wasn’t clear enough, just watch the extremely short video below to see what I mean.<\/p>\n