{"id":12313,"date":"2012-10-23T11:29:18","date_gmt":"2012-10-23T16:29:18","guid":{"rendered":"http:\/\/mediastorm.com\/blog\/?p=12313"},"modified":"2013-12-10T16:33:10","modified_gmt":"2013-12-10T21:33:10","slug":"adobe-premiere-its-damn-good","status":"publish","type":"post","link":"https:\/\/www.mediastorm.com\/blog\/2012\/10\/23\/adobe-premiere-its-damn-good\/","title":{"rendered":"Adobe Premiere, It’s Damn Good"},"content":{"rendered":"

Editor’s note: After seven years working with Apple’s Final Cut Pro, we have decided to begin using the Adobe Production Suite<\/a>\"\". We were early adopters of FCP 7 and considered making the switch to FCP X. In the end, we felt more comfortable with Adobe’s product than Apple’s FCP X. We know that many people in the industry are struggling with the same decision, so our producers have agreed to share their reasoning for the switch. <\/p>\n

Today’s post from Tim McLaughlin<\/a> tells about his experiences editing in FCP X and creating MediaStorm’s first project in Adobe Premiere Pro. Eric Maierson posted yesterday<\/a> explaining the overarching reasoning for the switch. <\/p>\n

These two posts are just the beginning. Our producers will continue to share their experiences with you on our blog<\/a>. Also, they’ll be posting Premiere shortcuts on a new twitter feed @PrProShortcuts<\/a>. And stay tuned for the release of a new Post-production Workflow for Premiere that will be bundled in with the current FCP 7 and FCP X workflows. Purchase a copy of our Post-production Workflow<\/a> today and you’ll automatically receive the Premiere workflow when it is released.<\/em><\/p>\n

\n

Not long ago, I was an incorrigible advocate for Final Cut Pro X. <\/p>\n

In many ways I still am. <\/p>\n

Organizing assets in FCP X is an absolute pleasure. When fellow producer Eric Maierson and I sat down to create the FCP X Post-production Workflow<\/a>, we found that organization was dramatically faster in X than it was in FCP 7. <\/p>\n

I like many of the new quick keys, which have a logical layout and are intuitive to use.<\/p>\n

And as trivial as it sounds, FCP X is a pleasure to look at. It\u2019s beautifully designed. <\/p>\n

\"\"<\/a>
FCP X has a beautifully designed interface. <\/figcaption><\/figure>\n

But the more I worked with it, the more I felt a nagging sense of uncertainty. <\/p>\n

Here\u2019s the thing. The timeline is my canvas. It\u2019s my idea pad. I\u2019m sketching out solutions to problems and playing around with elements of a story. I want it to be as simple as drawing and erasing two-dimensional objects on a page. It should be as easy as a blank piece of paper and a pencil. The more complicated the sketchbook, the less time I have to think about the story I\u2019m telling. <\/p>\n

Editing in Apple\u2019s magnetic timeline, for me, has yet to feel simple and intuitive. That’s because I have to consciously think about where my assets go and how—depending on where they\u2019re placed—they will behave. Because of this, I often have to think two or three steps down the road, and I never feel fully settled that once I place an asset, or time a clip, that it will remain in position. There are ways to mitigate this with the place tool and gap clips, but having to consciously think about those things slowed the creative process for me. <\/p>\n

Apple says the magnetic timeline makes mundane tasks like closing gaps easier and avoids traditional pitfalls like clip collisions. While I think Apple is right to try to make easier the inefficiencies of modern NLEs, I never, in all my years of editing, thought that closing gaps or clip collisions were major issues. I certainly don\u2019t think they necessitate the magnetic timeline and all its confusion (there\u2019s an old proverb about not removing a fly from a friend\u2019s forehead with a hatchet that comes to mind). <\/p>\n

Furthermore, I just don\u2019t trust FCP X with my data. I\u2019ve experienced troubling bugs and have redone numerous days of work as a result. When I deleted a keyword from a large number of clips, FCP X crashed and dumped those same metadata tags. When I attempted to trim a gap clip in the primary storyline, the entire timeline went grey and remained that way despite computer and software restarts (you can see this particular bug in action here<\/a>). I have spent hours on the phone with Apple trying to resolve these bugs to no avail. I simply don\u2019t trust the program. <\/p>\n

So after my last edit with FCP X, I downloaded the Adobe Production Suite<\/a>\"\", and decided to edit my next project with Premiere Pro<\/a>\"\". To teach myself the program I did some tutorials on Lynda.com<\/a> and Creative Cow<\/a>, and I bought the latest Premiere Pro book<\/a> from Adobe. But to be honest, most of what I learned came from just poking around the interface. I think anyone moving from FCP 7 can be up to speed rather quickly in Premiere.<\/p>\n

After cutting a 26-minute film with more than 40 hours of b-roll and four hours of interviews, I can confidently say that Premiere Pro is damn good. <\/p>\n

The autosave features are more robust than FCP X, timeline trimming is intuitive and fast, the keyboard can be customized to your heart\u2019s delight, you can choose how much RAM you want to use, the color correction tools are really good, and the integration with other applications in the Creative Suite is fantastic. <\/p>\n

I can\u2019t tell you what a relief it was to find that when I dragged a photo from Lightroom into Premiere Pro<\/a>\"\", the file that came into the timeline linked back to the original photo at the Finder level. Anyone who has tried a similar action from Aperture to FCP 7 or X knows that Aperture creates an entirely new file buried within its own file structure.<\/p>\n

Additionally, we\u2019ve had a higher rate of success transferring our old FCP 7 projects to Premiere Pro then we have to FCP X. We have terabytes upon terabytes of legacy projects, and we\u2019re constantly working with those archives. It\u2019s important for us, and for many others, that legacy projects be accessible outside of software that is no longer being updated. <\/p>\n

And most important for me, I feel like I have control of my assets in the timeline. When I cut a sequence to music, I have full confidence that the timing will be there if I edit something downstream. When I look at my timeline, I can visually see the organization of audio, stills and video because I have discrete tracks and on-the-fly color labeling. When I want to drop in clips of various formats and frame rates, Premiere Pro<\/a>\"\"
\ndoesn\u2019t blink. When I have multiple types of audio sources, I can choose if I want my dual mono to come into the timeline on separate tracks or as one stereo channel. <\/p>\n

\"\"<\/a>
Placing a timeline from FCP X (top) and Premiere Pro (bottom) next to each other, it\u2019s much easier to distinguish types of assets quickly in Premiere Pro. This level of organization is crucial for me on larger projects that have many levels of assets on a timeline. <\/figcaption><\/figure>\n

In short, I feel more in control, and less interfered with when working on the Premiere timeline, and I value that way more than I value the convenience of the magnetic timeline. <\/p>\n

Furthermore, I trust Adobe in the professional space to listen to feedback and make changes that help us create work and save time. In the two months since I first downloaded the Production Suite, Adobe has updated their suite of applications on a near weekly basis. And they\u2019ll need to be responsive to feedback, because as good as Premiere Pro is, there are a lot of things that need work (which we\u2019ll be discussing in the coming months on the blog). <\/p>\n

I also trust that their ecosystem of products, from Lightroom<\/a> to Photoshop<\/a> to Premiere Pro<\/a> to After Effects<\/a> to Speedgrade<\/a> will keep up with our company\u2019s aspirations to grow and put forward an ever-evolving, and hopefully, increasingly sophisticated product.<\/p>\n

I think it\u2019s likely that one day FCP X will be a very popular, stable and robust program. I\u2019m sure Apple would argue it already is. I\u2019ll be keeping an eye on it as it evolves, with the very real hope that it will become the future-proof timesaver that it claims to be. <\/p>\n

We have no horse in this race. We have no allegiances or motivations. Our move to Adobe is motivated by our personal experiences with each program, and is informed by a method of production that is particular to this studio. At the end of the day, this is about storytelling, and good storytelling is software agnostic. But for the time being, we think Premiere Pro<\/a> makes it easier to get to that story. <\/p>\n

My friend and colleague Eric Maierson posted yesterday<\/a> about his experience with the switch to Premiere Pro.<\/p>\n

In the coming months, we will be sharing our discoveries with you, just as we did with Final Cut Pro. There will be many new MediaStorm blog posts, plus, @PrProShortcuts<\/a> a twitter feed devoted to shortcuts, and eventually a new workflow. <\/p>\n

We hope you will join us on this journey and let us know about your experiences with FCP X and Premiere Pro in the comments below.<\/p>\n

\n

To learn more about our production style, purchase a copy of our Post-production Workflow<\/a>. Readers who purchase our current workflow automatically receive the Premiere workflow when it is released. Learn more about our other online and in-person training at mediastorm.com\/train<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Editor’s note: After seven years working with Apple’s Final Cut Pro, we have decided to begin using the Adobe Production Suite. We were early adopters of FCP 7 and considered making the switch to FCP X. In the end, we felt more comfortable with Adobe’s product than Apple’s FCP X. We know that many people […]<\/p>\n","protected":false},"author":18,"featured_media":12319,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,1,748],"tags":[1231,1227,1229],"class_list":["post-12313","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-editing","category-mediastorm-announcements","category-tutorials","tag-adobe-premiere-pro","tag-final-cut-pro-7","tag-final-cut-pro-x","entry","has-media"],"_links":{"self":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/posts\/12313","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\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/comments?post=12313"}],"version-history":[{"count":0,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/posts\/12313\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/media\/12319"}],"wp:attachment":[{"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/media?parent=12313"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/categories?post=12313"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mediastorm.com\/blog\/wp-json\/wp\/v2\/tags?post=12313"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}