{"id":39080,"date":"2014-04-21T11:15:03","date_gmt":"2014-04-21T15:15:03","guid":{"rendered":"http:\/\/www.premiumbeat.com\/blog\/?p=39080"},"modified":"2014-04-21T11:15:31","modified_gmt":"2014-04-21T15:15:31","slug":"three-things-you-need-to-know-about-premiere-pro-cc","status":"publish","type":"post","link":"https:\/\/www.premiumbeat.com\/blog\/three-things-you-need-to-know-about-premiere-pro-cc\/","title":{"rendered":"Three Things You Need To Know About Premiere Pro CC"},"content":{"rendered":"

New to Premiere Pro? Know these file management and workflow tips to improve your editing.<\/h2>\n

\"Premiere<\/p>\n

As an editor who is still learning the ins-and-outs of Premiere Pro CC<\/strong> after 10 years with FCP 7, I’m constantly coming to terms with why Premiere Pro\u00a0does things the way it does.<\/strong><\/p>\n

I’m not saying either way is better (in comparison to any NLE) but what matters to me, is that I fully understand exactly what’s going on<\/strong>. To that end, here are three things I learned recently, that you might want to know too.<\/p>\n

Premiere Pro CC Generates Useful Junk<\/h2>\n

\"premiere<\/p>\n

One of the things that is especially helpful about Premiere Pro CC is the ability to throw just about anything on the timeline<\/strong> and it will just work. That ”just working” does require a decent amount of RAM to make it go, but it also requires a bit of work behind the scenes too.<\/p>\n

When you import your camera native files (say some .MTS files) Premiere will start to ‘conform’ those files getting them ready to play back<\/strong>. If you’ve ever dropped some files on the timeline only to discover they seem to have no sound, this is often because it is still creating the preview files.<\/p>\n

\"what<\/p>\n

It only has to do this process once because it creates a cache of all those conformed previews in a folder on your boot drive. This is very helpful while you’re working on a project, but after you’re done those files just sit in that cache folder, slowly swallowing up a huge amount of disk space.<\/strong><\/p>\n

The best way to deal with this situation is two fold. First of all it probably makes sense to move the media cache folder from it’s current location on your boot drive, to your main media storage drive. That way you can keep a closer eye on it, and also not forget all about it and wonder where your drive space is going. By default the Adobe media cache folder is here on a Mac:<\/p>\n

Users\/(Your user name)\/Library\/Application Support\/Adobe\/Common\/Media Cache Files<\/strong><\/p>\n

You can set the default location in the Adobe Premiere Pro CC Preferences under Media. <\/strong>In the second section ‘Media Cache Database’ – simply hit browse and point it to a new folder on your fastest media storage drive. It will ask you if you want to move the current cached files, or simply delete them and start over.<\/p>\n

You can also set Premiere to save the Media Cache files ‘next to originals when possible’ – which means that your camera native folders will start to fill up with these files instead (or wherever you are importing your media from). This might be preferable if you are working on lots of little projects, spread across many drives, or taking the drive to lots of different machines. If not, you’re probably best simply moving the media cache folder off your boot disk.<\/p>\n

\"changing<\/p>\n

Next, you’ll want to clean it out after you’ve finished a project to save space.<\/strong> If you need to come back to a project once you’ve deleted the media cache files, it will just re-create any missing files. To do so simply hit Clean. <\/strong>This will only delete any files not associated with any source media currently connected. If you want to delete everything<\/em> you can just navigate to the default location and delete the contents to the trash.<\/p>\n

How Premiere Pro CC Handles Audio Channels\u00a0<\/span><\/h2>\n