If you’ve been following my blog for a few years you may remember back in the summer of 2010 I created a project that I called “Switch to Premiere Pro” or “#X2PPro”. If you check your twitter feed you will see that that hashtag was used in 2010 and 2011. At the time I was very unhappy with what Apple was doing with Final Cut Pro and its progress. I set out on my own to find a replacement for a tool that I had used for a long time.
The “campaign”, if you will, proved to be quite successful. Many of my professional peers were shocked that I was considering leaving Final Cut Pro, a tool that I had used for over a decade. Even Adobe Systems noticed my blog entries and asked me to be a part of a few events designed to promote Premier Pro.
Not wanting to be a “spilled milk” kind of guy I left one part of the story out of my blog. After six months of following the “Adobe Way” I tired of the application and moved on. The biggest stumbling block that I had was the lack of what is commonly called Smart Renders. Smart Renders allow you to begin rendering a timeline and then abort that render midway while keeping what has been rendered thus far. Since Adobe’s biggest selling point was a lack of rendering due to the power of the Mercury Playback Engine, I guess it took a while for the good people at Adobe to decide that this was an important feature. What this resulted in was often times getting to the end of a project but requiring one long massive render in order to deliver. This made it very difficult to calculate how long it would take to send a file to a client.