Learning Premiere Pro from a Final Cut Point of View

| By Trent Armstrong | Found in Video | 12 Comments

As of late, I’m attempting to make sense of what is going on with the world of professional (or even pro-sumer) editing software. I also want to best utilize all the editing and motion graphics tools at my disposal, so I have begun to take a serious look at Adobe’s Premiere Pro editing software.

I’ve been a Final Cut Editor since version 1.2. I have really enjoyed using FCP! I learned most of the advanced features and consider myself a pretty efficient Final Cut Pro editor. My aim is to take the things I’m learning in Premiere and compare them to my knowledge of FCP — differences, drawbacks, and positives.

I will be making posts about what I discover so you can determine if the route I’m taking is the one for you.  Actually, I’m not even sure this route is for ME! But I am doing the research and will let you know what I find.

THE REASON
Of course, the superficial reason for trying out Premiere Pro is obvious — the release of FCPX and the redesign of the interface. Apple is changing the editing paradigm with FCPX, and it’s a little unnerving. I’m not saying I won’t ever learn FCPX, but in the immediate future, it doesn’t seem like that is a good move for me.

The deeper reason for taking a hard look at Premiere Pro is its tight integration with After Effects and other members of the Adobe Suite. Much of my interest lies here so much of my research will center around Dynamic Link and the workflow between AE, Premiere Pro, and probably Soundbooth.

PROJECT AND SEQUENCE SETUP
It seems like the initial setup for each project is fairly similar. Final Cut Pro allows multiple projects to be open at once. Premiere Pro operates much like After Effects where you can have only one project open. That project can then have multiple timelines.

I have FCP set to always create new sequences as HD, whereas in Premiere Pro, it appears to be necessary to make that decision every time a new sequence is created instead of it the software doing so automatically.

Also, I usually work in either 1080p or 720p and set settings for 1080p in Premiere have a frame size of 1440 x 1080 with a pixel aspect of HD Anamorphic 1.333. I had to select Desktop as my Editing Mode to get access to the frame size so I could set it to 1920 x 1080 with Square Pixels (1.0).

Final Cut allows the editor to change the Sequence Settings after a sequence has been created.  It appears that Premiere Pro will not allow that.  The only way around it that I have discovered so far is to create a timeline with the new, correct settings and copy the edited clips into the new timeline.

ADDING CROSS DISSOLVES
If you haven’t committed the Add Default Transition hotkey to memory, you might not want to read any further. I actually got the nickname “Apple-T” (Add Default Transition) because of my interest in learning hotkeys. I’m a firm believer that one can be a far more efficient editor with hotkeys than mouse, trackball, or pen tablet.

In Final Cut Pro 7, the most common way to add a cross dissolve to an edit point is to select the edit point and press CMD+T or Apple-T on the keyboard. That involves mouse and keyboard. Another way is to navigate to the edit point using the arrow keys, press V on the keyboard to select the edit point, and THEN press CMD+T. That’s at least three steps.

In Premiere Pro, using Page Up and Page Down jumps between edit points on targeted tracks. Once the cursor is at the edit point, simply press CMD+D. Two steps!

SLUG
I am a firm believer that an editor should never dissolve a number of clips or graphics to black at the same time but should always place a slug above the clips and fade into the black instead.

The Viewer in FCP is where you find the dropdown menu that includes the Slug. In Premiere Pro, it’s under FILE> NEW> BLACK VIDEO …  This places an asset in your project called “Black Video.” You can use reuse this clip as necessary.

Thanks for taking the time to read this.  If you have any thoughts, tips, or questions, please leave them in the comments section of this post. See you next time!

Trent Armstrong is a Creative Producer for Igniter Media. Follow him on Twitter: @AETrent

  • Anonymous

    I use the V-arrow keys-Command T all of the time, so it’s great to hear there’s an equivalent in Premiere. Thanks for the tip!

  • Bob Pierce

    I have found that if I open a new project with the preset “Sony XDCAM EX (HQ) 1080p” then the Frame Size is actually 1920×1080 with square pixels. I’m using Premiere Pro CS3 and I’m quite happy with it. One very nice feature is that you can import an AfterEffects project as footage into a Premier project. Then, any changes made to the AE project later result in that footage being changed inside Premiere. And, when it comes time to render the Premiere project, the AfterEffects footage is rendered on the fly as needed – no need for a rendered intermediate file from AE. This is nice becaue that intermediate file would have taken up space on your hard drive, or if you used a lossy codec for the intermediate file there would have been a drop in quality. This way, there’s no quality loss and no wasted hard drive space.

  • Jesse Eells

    Thanks for the research. I’ve been using Premier for awhile and was actually wondering about the differences. Looking forward to what you all have to say

  • http://www.facebook.com/briancates Brian Christopher Cates

    Good post, Apple-T(knee). I’m going through Lynda’s migration series this week. It’s fantastic… but 6 hours long.

  • Marcus Rhoads

    Good post! I’m actually in the same position with switching to Premiere.
    About your sequence settings question…
    What works for me is to start a new project, set the save location, name it and hit “OK”
    Then, (the important step), click “cancel” when the new sequence dialog comes up.
    Import your footage and create a sequence with the exact same settings of your footage by dragging a clip to the “new item” button. It’s a square next to the trash icon.
    A new sequence will appear with the same name as the source footage.

    Another cool thing is that you can import any project into a new project. This helps for matching settings.
    I like Premiere so far, but a little bummed that I can’t get a Mercury engine video card because my system is too old.

  • Chris Reardon

    Great to see posts like this. Looking forward to all the new Echo Hub has to offer!

  • http://www.facebook.com/dave.greider Dave Greider

    I’m personally going with Avid from my FCP transition. I’m also a major AE user, but the majority of production companies I work with in LA are Avid. Premiere seems like a solid solution though. I just hope it picks up more in the mainstream market of TV/Film/Advertising. Until then, I’ll primarily be on Avid.

  • John

    Started with Premiere in early 2k’s. Switched to FCP in 2004 as Premiere would crash a lot. Recently hoped for more stability out of Premiere CS5, especially with all the FCPX noise, but I still find it way too buggy for my liking. FCP 7 is where I’ll stay until I feel secure about FCPX progress…

    The Premiere/AE dynamic linking is attractive, but for me, if I’m headed to AE, it’s probably because I’m doing some heavy lifting that I wouldn’t want slowing down my edit render timeline.

  • http://twitter.com/JAMJ7 Jamaal Jackson

    Thank you for this post, my creative Pastor asked me why i do not work in Premiere and i really did not have an answer other than i am proficient in FCP so hy switch over. I may have to look into it though one because i am not a fan of FCX and two because of the Adobe suite integration. I look forward to continued posts on your comparison.

  • http://echohub.com/posts/video/more-on-premiere-pro/ More on Premiere Pro | Echo Hub » Posts

    [...] If you missed Trent Armstong’s first post about learning Premiere Pro from the perspective of a Final Cut user, please click here. [...]

  • LarryB

    Why really switch now? My FCP 7 works just fine. I am so much of an Apple believer that I am expecting Apple to see the error of their ways and, in a few years, FCPX will work as good as 7 does now. So why not wait it out. Eventually 1.25 became the 7 we all love. What males you think X won’t grow out of this stupidity and blossom into something good? I am willing to wait and be happy with 7 for now.

  • http://glimpseandecho.wordpress.com/2012/01/12/from-final-cut-pro-to-premiere-pro-learning-to-adapt/ From Final Cut Pro to Premiere Pro: learning to adapt « Glimpse and Echo

    [...] Learning Premiere Pro from a Final Cut Point of View [...]