The Libraries were probably planned since the beginning. The fact that the first version of FCPX was named 10. Maybe Apple released FCPX with the "provisional" Events/Projects model, because the Libraries model couldn't be release until Mavericks came out in October 2013. The Libraries media management structure is very complex and it relies on the OS a lot. The same applies to Avid since Media Composer 7, which almost overlaps with CC7 on time.Ībout the introduction of Libraries, I'm not sure that Apple was correcting a mistake with 10.1. As the schedule shows, Premiere's updates become more frequent since CC7. I believe this is what pushed Adobe into the subscription model: it was the only way they could compete with Apple's aggressive development of FCPX. And that's a very important fact in my opinion. From 10.0 to 10.0.9, Apple really set the bar very high up, with frequent and fully packed updates in a way that we had never seen before in NLE history until then. I think the early years of the schedule matter a whole lot. Essentially correcting a path, without admitting they started out on the wrong foot.īut I disagree with Oliver on a few things. Plus the change to Libraries, which was a bit of a step back and regroup move by Apple. With FCP X, nothing matters before 10.1, because that entire first iteration from 10.0 until 10.1 was completing the roadmap of things that were planned awhile back. Last year, all 3 companies released at about the same pace. Really, the only part of this schedule that matters is 2014. To sum it up, I will paraphrase Spiderman's Uncle Ben: " with great design comes great wrote: All this makes FCPX features more effective and better overall because of how well they interact with each other. But they are not being influenced by the competition because they have a coherent design and a clear path. Instead, FCPX is refining the new paradigm and filling the holes. And later, they are incorporating some of the new ideas in FCPX (at least the ones they can fit in their traditional designs). Most features added by Avid and Adobe in the last years were all about mimicking FCP Legacy (at first), to attract Apple users disappointed with the FCPX launch. Also, for me it's not really a matter of quantity but quality:.Instead, the competition is a bit more thorough in their official documentation. Apple doesn't list all the new features that come with every version of FCPX in the official release notes, as Alex himself has noted in his blog many times.But if we go by Alex Gollner's list of features, FCPX updates seem the less feature packed. It seems that FCPX is the one with more updates between 2011-2015.I think this is one of the reasons why Apple had to push the launch of FCPX so soon. It came with 64-bit support and introduced the Mercury Playback Engine. Jean-François, I think the timeline should start a bit earlier than June 2011 and include Premiere Pro CS5, which was released in April, 2010: I did this using Wikipedia, so there might be some errors, but I thought I was an interesting perspective.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |