After months of testing, playing, discussing, testing, playing, and then discussing some more, we’ve decided that Biscardi Creative Media will support both Adobe Premiere Pro and Avid Media Composer workflows moving forward.
What we found as we went through the testing is that there are positives and negatives to both systems so it’s really hard to just choose one. As my editors got to playing with both systems it became clear that for certain workflows, one tool works better than the other. So why limit ourselves to JUST one or the other. Put both tools in the toolbox and utilize the most efficient tool for the job at hand.
With Adobe, it still feels too much like it was “designed by an engineer” and not by editors. If you go with the Adobe keyboard presets, it’s not all that intuitive if you’re coming from FCP or Avid. Switching to the FCP presets makes things a bit better, but things like track assignments, stereo vs. mono tracks and other functions throughout the app that should be simple, sometimes are a bit convoluted. Such as not making it all that easy to adjust your audio before placing the material into the timeline, FCP was much easier with the multi-tabbed Source window layout. The more you play with Premiere Pro, the more you “forget FCP” and adapt your workflow to the new tool.
The biggest hit against Premiere Pro now out on the forums is the sometimes tremendous render times at the end of a project. This is mainly due to the fact that Premiere Pro can utilize just about ANY format natively, and in realtime during the edit. The price you pay is that at the very end of the project, you must render the entire timeline and depending on the raw formats, timeline settings and other variables, it can sometimes add up to a significant render time that far exceeds anything we saw in FCP. This can definitely be a scary prospect when you’ve got a tight deadline to get something out the door.
Now the absolute positive about Premiere IS the ability to edit in just about any format. I had a timeline with RED 4k, DVCPro HD, HDV and a few others and the darn thing just played. No need for conversion, no waiting, no special formulas. This is fantastic for shorter projects and we’ve especially found it useful for creating sizzle reels and pitches for networks. I recently cut a 6 minute sizzle reel using YouTube videos, H.264 HD files, ProRes and an MPEG-2 in about 4 hours flat because I didn’t have to convert anything. I even had time to design a quick logo and make lower thirds. That was fast.
Adobe has gotten a ton and I mean a TON of feedback from newly converted FCP users and hopefully they’ll be able to combine the legacy of the underlying horsepower of their system with making the system more editor centric and less engineer centric as the product line moves forward. They have been truly open and honest about listening to the end users. I expect great things of Premiere Pro over the next few years.
Avid Media Composer 6 just far exceeded anything we expected from the third party support perspective. AJA Kona Boards – Work. Small Tree Ethernet SAN (NAS) – Works. Tape capture and mastering – Solid.
The biggest thing to understand with MC6 is that while the AMA features do work, they tend to bog down the system very quickly. AMA is Avid’s attempt to edit non Avid footage natively. You can bring the footage into the project and you can edit with DVCPro HD, ProRes, DSLR footage natively, sort of. Start putting these clips into the timeline and your system can crawl to stop.
The obvious way around this is to simply convert everything to DNxHD. We have found this to be an incredibly painless and efficient process with Avid so that’s what we’re doing with all of our Avid projects. The conversion happens by simply “Importing” the footage. No “Log and Transfer” type of operation necessary. Just grab the clips and “Import” and Avid will convert all the footage based on your Import settings you establish in the preferences. Quite simple actually and we find the process happens faster than Apple ProRes conversion process.
Now the only unknown is to see how well Avid can transition from a big box company to a software predominated company. That’s a big change to the open architecture so we’ll have to see how they make that work.
Now the other big reason why we are making this transition to both Adobe and Avid at this time is the cross platform nature of both applications. As we are at the point where we need to start upgrading our older Mac Pro systems, these software platforms give me the option to transition over to Windows if I should so choose. I would never change over my Mac to Windows overnight as that would be silly, but simply have the Macs work alongside the Windows machines as we need to upgrade and replace.
So for us, being an independent Post Production facility, we have found no reason to simply settle on either Avid or Adobe at this time. We’ll simply use the best tool for the job at hand.