that DaVinci Resolve 8.1 now has support for FCP X and conforms and roundtrips. So you can now do a full color out of FCP X, though you audio is still going to be hard to conform without tracks.
You can even move an FCP 7 edit to FXP X using resolve, which is pretty huge. Now they need to add Premiere Pro support!
| The Provideo Coalition is reporting |
OnLineVideo.Net has an article on Final Cut Pro 10.0.1 it is not so positive. I agree with it wholeheartedly.
I like what they have to say about the new feature roles:
To a degree, roles are a solution to a problem Apple created by making Final Cut Pro X trackless. For example, in Final Cut Pro 7, or Premiere Pro for that matter, you could accomplish the same thing by placing narration on one track and music on another, and enabling/disabling the track as necessary for preview or rendering.
In addition to preview, when rendering out to a QuickTime file, you can also use roles to create separate files for further editing in another program. This is shown in Figure 4. For most high-end users, however, OMF or EDL export in Final Cut Pro 7 provides the same capability, while those editing in sister programs like Soundtrack Pro or Color would simply use the direct export feature shown in Figure 2. Apple declined to include industry-standard mediums of exchange in their product, or direct access to Soundtrack Pro, and roles is a substitute. In my view, you don’t get brownie points for fixing a problem caused by your own questionable design decisions.
And in conclusion:
For me, all the glorious new features seem like solutions to problems that I don’t have, added complexity with no payoff. With Final Cut Pro 7 or Premiere Pro, there are projects, clips, and a timeline. You import your clips, organize them into folders, and drag them down into the timeline. Then you trim a bit, add some effects, maybe a transition or two, export, and you’re done.
With Final Cut Pro 10, you have Events and Projects. You have a Magnetic Timeline, Clip Connections, a Primary Storyline, Auditions, Roles, Smart Collections: all are completely new concepts that I’ve never encountered in the dozen or so editors that I’ve cut projects on in the past, and, in some cases, they’re solutions to problems caused by questionable design decisions like the trackless interface.
The result is a cluttered interface that you really can’t control and asset management with even less control. You have effects and other functions seemingly designed to prioritize being different rather than superior. Honestly, was every established editing convention, from marking clips in and out in a source window to three-wheel color correction, so tragically flawed that it wasn’t worthy of being implemented in Final Cut Pro X, if only because it was functional and familiar to all pro target users?
More importantly, within the context of my typical projects, whether a two-hour ballet or music concert, or a ten minute streaming clip or screencam, will these new concepts help me do my job faster or better? I honestly don’t think so, particularly because Final Cut Pro 7 and now Adobe Creative Suite already suit my needs so well.
Exactly, the new features do not speed up my editing, and I actually find them slowly and less efficient. And now that is seems that FCP X has lost OMF export when Automatic Duck went away, so roles is even more useless, as I need OMF much more than just exporting tracks (though I do need tracks as well)
I don’t want a new form of editing, I want new features on top of the way I already edit, and if I like them will use them, but I don’t like the new way of editing of FCP X, and I don’t think I ever will
MacTech is reporting, that Singular Software has announced that a free update to Presto and Plural Eyes will support Final Cut Pro X (so it is good that Apple released an XML for FCP X).
Check out his plug in at Foolcolor. For $89 it will move your FCP X project into After Effects. He is also working on one to export audio to FCP 7 so you can export an OMF and to export FCP 7 Sequences to FCP X and FCP 7 Projects to FCP X.
Pretty awesome that he is doing this, especially with Automatic Duck possibly out of the picture!
FCP.CO has a video by Micha Schmidt on using Roles, and getting out the audio to do a mix.
It is worth checking out, and makes it seem pretty useless as the exports using ROLES for audio tracks, only gives you complete mixdowns of each track that has been assigned Roles, but they are mixdowns, and not at all OMF tracks with individual audio tracks. So not all that useful. Sure you could make versions with audio on different tracks like this (if you have another program to make tapes).
My question do Roles export with Automatic Duck Pro Export 5.0 so that the clips show up in tracks? If that works, then it makes Pro Export more useful, but if not, Roles are pretty useless.
Check out this article on FCP X, and why it should have been a professional app when it was released, and not a partial app that will slowly have new features, which is commenting an article at Post Magazine. Which I totally agree with and have bee saying all along. Adobe did it just fine in bringing their apps to 64 bit, why did Apple have to not have feature parity or even compatibility with their old app?
And the fact that FCP X now has XML, but it is still not, and will never be compatible with FXP 7 is a joke. If Premiere Pro can do, Apple could do it, but they won’t.
I like this part:
At one point in the article Townhill notes that Apple is responding to feedback and changing the application quickly to meet the demands of the Post community. The strange thing to me is that Apple was given much of the same feedback during the beta testing and it was roundly ignored. Pages upon pages of information was fed to Apple with pretty much everything that has been said publicly since the application was released. In all cases, Apple ignored the suggestions moving ahead with the product as they developed it. NOW that there’s a tremendous outcry, NOW Apple is “responding to the Post Production community.” Maybe if they had responded to the people who were testing the product, they could have avoided this entire fiasco.
So it looks to me like Apple’s original plan was to just release FCP X as a prosumer product that really didn’t need the full fledged Post Production community blessing because there are millions of consumers out there and only a couple hundred thousand Post Pros. If it was truly aimed at the pros, then Apple would have listened to the pros during beta testing about all the things that were badly missing from the app.
But with all the subsequent negative press on the product, Apple is desperately trying to backtrack and figure out how to add the extremely basic functions that it left out by “skating where the puck is going.” (read the article to understand)
If Apple was truly dedicated to the professional editing community they would have taken the two to three years to deliver something that built upon their 11 year legacy. I just see what they’re doing now as creating a whole box of band-aids to make the product cobble along and sort of kind of do what the product has done for the past 4 years at least. Apple is admittedly leaning heavily on third party vendors to fill in what they call gaps, what I call chasms in the software.
So true so true. Apple made FCP X on purpose, they knew they were giving up on the pro community completely and all the businesses that make a living making plug-ins and hardware for final cut pro, but they figured they would make more money by making a consumer application and banking on the name of Final Cut Pro which has come to mean something in the industry. Now they realize they may have screwed up, but it is too late. These new features could have been add ons to a true 64 bit Final Cut Pro and it would have been awesome, but this weird prosumer app they have made with some pro features and the rest decidedly consumer will never be used by Pros, and shouldn’t even have Pro in the name.
iMovie is not called a pro app because it is not, and adding some pro features to it, when it forces you to work in it’s limited way does not make it pro, and never will. And nothing Apple does will ever make this app right for professionals, Apple has ceded this market, and Adobe and AVID are going to be really happy to fill the gap.
Macworld has an article dealing with Apple’s 10.0.1 Update to FCP X which will be released today (so far I only see an update to Compressor). Anyway for features they have done 3 major things for editors, the first is to release XML in and out of both project and event information (though likely no FCP 7 integration), added XSAN integration, and allowed intelligent stem export for audio and video using tagging in a feature called Roles.
I was wondering if Apple cared at all about this software to take a solid 3 months for an update, but at least they have updated.
And now you can have tracks be made out of sound for Audio export by tagging content, and it will smart export the tracks to the proper tracks, though I still think track support would be better an easier at least their is now a solution.
Amazingly Apple is also listening and is offering a free 30 day Trial, so you can try it out before you buy it. And they will also be releasing a free PDF Booklet entitled Final Cut Pro X for Final Cut Pro 7 users, which will be available from the Final Cut Pro X website soon. This should have come out with the application, but it is a start.
The article also talks about the release of Multicam and support for video monitoring, which will not be released until 2012, and they don’t say when, making this software not at all a professional app.
I am glad they are adding in features, but to me, they should have waited to release any app called Pro until all these features were integrated, unless they were going to continue to update and support final cut pro 7 during the period!
FCP.co has an article leading to some interesting tutorials from Paulus the Woodgnone.
Pretty cool if you are using FCP X.
Well with all the rumors that Tim Cook is actually listening to customers I decided to leave Final Cut Pro feedback with Apple once again. I asked them to rename FCP X into iMovie Pro and release a true 64 bit FCP 8 (along with a new Color and Soundtrack Pro) with all it’s previous functionality and some of the added features of FCP X. They can even put the magnetic Timeline in, as long as it can be turned off!
I doubt it will make any difference, but it sure would be nice to have FCP 8 truly 64 bit with all it’s functionality, bug fixes and new features that make it the premiere editing system out there. And Tim Cook could make that change, even if he in all likelihood wont.
Hardmac has an article on an official statement from Adobe about them having a 45% growth in OS X after the release of FCP X. Good job Apple! You could not have done more for Adobe, or in all likelihood AVID than crippling FCP X as you did!
And if you cared, you would have released an update to FCP X by now, but obviously you have not, so your claims to caring are shown to be hollow!