Final (Cheng Gu) Mac OS
The backlash against the newly introduced Final Cut Pro X rages on, but Apple is at least trying to quell the fears of angry users with the help of a FAQ page about what will and won't work as users transition from Final Cut Pro 7 to FCP X. Some of the answers will calm users who were unhappy with FCPX's initial showing, but other professionals will remain unhappy with Apple's decision to seemingly alienate those whose livelihoods depended on previous versions of the software.
Apple only introduced FCPX a week ago, and the reaction was mixed right from the beginning. There were significant changes in the user interface, not to mention a plethora of missing or hobbled features compared to FCP7. The biggest cause of the outcry seems to be the fact that FCPX cannot import projects from previous versions of Final Cut Pro—no, not even the most recent one—making it laughably difficult for any professional who depends on the software to make a seamless transition to the new software. Additionally, users have complained that there's no support for output to tape (while input is limited) or EDL or XML export, and no OMF output for mixing audio in Pro Tools, among other things.
View Kuncheng Li’s profile on LinkedIn, the world's largest professional community. Kuncheng has 4 jobs listed on their profile. See the complete profile on LinkedIn and discover Kuncheng’s. Hackintosh.com links to everything you need to build a Hackintosh and get macOS Big Sur (macOS 11) as well as many earlier versions of Mac OS X running on an unsupported computer - instructions, step-by-step 'how to' guides, and tutorials - in addition to installation videos, lists of compatible computers and parts, and communities for support. View Qiong Cheng’s profile on LinkedIn, the world's largest professional community. Qiong has 1 job listed on their profile. See the complete profile on LinkedIn and discover Qiong’s. Get more done with the new Google Chrome. A more simple, secure, and faster web browser than ever, with Google’s smarts built-in. IMessage on the desktop went from a wish to (beta) reality in just four months. It's now on the Mac OS X desktop as part of Apple's Mountain Lion update, and our friends at Ars Technica have taken.
Cheng Gu Microsoft
Apple has already communicated to some video editors that this is not the 'final state of FCPX,' as noted by Gary Adcock, with some features apparently coming as part of the release of Mac OS X Lion. Still, as evidenced by Apple's new FAQ page, there are some things that just plain won't change.
For example, the company is quite blunt when answering a question about ever being able to import FCP7 projects again: because the software includes an 'all-new project architecture' and 'new and redesigned audio effects, video effects, and color grading tools,' there's no way to bring in old projects without losing data, Apple says. When it comes to editing a tape-based workflow, Apple reminds users that FCPX 'is designed for modern file-based workflows' (ouch) and doesn't support all the same tape capture features as FCP7, though it does support FireWire import for DV, DVCPRO, DVCPRO 50, DVCPRO HD, and HDV.
Advertisement
Final (cheng Gu) Mac Os Download
As for the good answers, Apple says that it plans to release a set of APIs 'in the next few weeks' so that third-party developers can create tools to support OMF, AAF, EDL, 'and other exchange formats.' In an answer to another question, Apple indicates that it's aware of users' need for XML exporting features, saying 'we expect to add this functionality to Final Cut Pro X,' but with no specific timeline. And in an answer to a question about assigning audio tracks for export, Apple says an update coming this summer will let editors use metadata tags to categorize audio clips and export them from FCPX. Volume licenses are coming too, 'soon.'
Apple's posting of the FAQ page comes just a day after news began to spread that the company had begun giving refunds to some dissatisfied FCPX buyers, despite it being against the Mac App Store's terms of service. But other users remain upset and confused by the re-architected software and have gone so far as to demand that Apple restore FCP7 under a new name or auction the source code to a third party by January 1, 2012. A petition has been posted online with (as of this writing) more than 5,200 signatures, chastising Apple for making such significant changes to industry-standard software:
Many have invested hundreds of thousands (some even millions) of dollars in creating Final Cut Pro based companies. These are now threatened by a 'prosumer-grade' product upgrade of Final Cut Pro 7 titled 'Final Cut Pro X,' and will likely put several of these companies out of business. The costly process of migrating studio hardware and software is a major burden, especially on studios that have made recent upgrades to support Final Cut Pro. If many had known of the Final Cut Pro X release prior to investing in expensive hardware and software licenses, most, if not all, would have sought alternative solutions.
A few of those users may want to rescind their signatures after reading Apple's FAQ, but we get the feeling that most plan to stick to their guns—especially after reading Apple's confirmation that the ability to import previous FCP projects will never come.
Final (Cheng Gu) Mac OS