Monday, June 27, 2011

Final Cut Pro X Information & Resources 4

Bug list
The Digital Rebellion is maintaining a bug list, and has 8 so far, including:
  • Projects not saving
  • Clips going offline
  • Undo disabled
  • Crashing when importing iMovie
DigitalRebellion: Final Cut Pro X Bug List

Gamma Issues?
An interesting post from Chris Marquardt notes that the gamma that Final Cut Pro X uses in the Viewer is different from the gamma used in QuickTime X. He notes that he thought Final Cut Pro X was supposed to handle color issues through ColorSync and solve problems like that:
It took me a while to figure out that the viewer in FCP X needs a color profile with a gamma of 1.8 in order to show things the way they are.
ChrisMarquardt: Final Cut Pro X - wrong gamma in viewer?
[UPDATE 9/28: Chris has updated his post with more details.]

I was able to reconnect a missing clip by selecting it in event, then running import, selecting the file. It reconnected.
Paul Antico

More Answers To Questions
Scott Simmons takes a look at some of the unanswered questions about missing features and gives some answers/guesses/rumors:
Will 3rd party I/O hardware be supported at launch?
Negative. My Matrox MXO2 Mini doesn’t work, neither does my AJA Kona LHe. This is the other of the two most glaring oversights that IMHO should have delayed the release of FCPX until it’s a bit more ready for prime time.
ProVideoCoalition: Those Burning Final Cut Pro X Questions Answered

The importance of forward compatibility
Ashley Kennedy polled some editor friends on how important they felt forward and backward compatibility of projects is:
Forward compatibility is very important. I don’t particularly want to have two iterations of the same application on my drive, as FCP7 and FCPX users will have to do now.
- Norman Hollyn
Premiumbeat: FCP X: Is the lack of forward compatibility a deal breaker for editors?

Trying To Make It Work
An Apple Master Trainer in Final Cut Studio, Howard Berry, posts his thoughts on using Final Cut Pro X, documenting his experience trying to edit an interview piece imported on P2 media:
Overall, I found I could cut in FCPX, but I feel it lacks accuracy, and that elements of the interface do not help this. The irritations, audio problems and crashes need to be ironed out soon. While it is quite simple to put clips onto the timeline, I really feel that things like timecode and the HMSF display are a secondary thing, and I really didn't feel comfortable with having to edit with the mouse quite a fair bit.
HowardBerry: FCPX Thoughts

Why The Switch?
Ice Blog Films looks at the math and why it doesn't make sense for Apple to continue development of Final Cut Studio as a fully professional tool:
The pro package was aggressively targeted at pro editors, a demographic that they appealed to very well and with good reason: FCStudio is fantastic. Unfortunately, there are three problems with this demo - it’s not very big, it’s not growing quickly and it’s very fickle.
The arguments make sense - I've always believed that Apple fell into the pro video market much more than it wanted to be there - though I'm not sure I believe that Apple will update DVD Studio Pro in any fashion.
IceBlockFilms: Breaking Down The iMath

More On The Details
Mark Boszko goes through some of the missing features, offering updates and his own thoughts:
There’s no bins. I can’t organize my media the way that I want.
True-ish. There are folders, but FCPx uses a whole new way of dealing with clip metadata that, in my limited experience, looks to be much more powerful than bins. For me, it’s a lot like how I love Gmail’s way of tagging email, and am loathe to move back to a desktop-based email solution that only has folders. In the same way, I think I’m really going to love tagging clips (and sub-sections of clips) with keywords and other metadata. Bins now feel like the past.
Station In The Metro: Final Cut Pro X: Is it really Pro?

When Personalities Become The Story

Richard Harrington's Business Relationships
Richard Harrington has become associated with the negative reactions to Final Cut Pro X, and though he's a Final Cut Pro user, he's also been doing training and giving lectures and demos of Adobe Premiere, which has prompted some to question his motivations. As a result of this, Richard has posted an article that outlines extensively his relationships and affiliations.
Richard Harrington: A Public Statement on My Relationships and Recent Writings

David Pogue takes a third swipe at it
David Pogue is obviously a bit more than surprised by the depth of passion stirred up by the release of Final Cut Pro X. He readily admits that his audience is more lay person than professional editor, and that he was surprised not only by the reaction to his first article, but that a follow-up piece that tried to provide more information only resulted in more negative response:
I’d hoped to clear up some confusion for the professional crowd, in hopes of letting them make a more informed decision. Instead, based on all the comments, all I managed to do was channel their anger at Apple into anger at me.
NewYorkTimes: The Quarrel Over Final Cut Continues
NotesOnVideoSeriously David, What are you drinking? [my own look at the original article]

Walter Biscardi on Transitioning away from Final Cut
Walter Biscardi is another person who has been outspoken in his dislike of Final Cut Pro X [Take Walter at his word, he isn't new to the band wagon; he started trashing Apple when they took over the SuperMeet, before they'd even shown it, and pretty much hasn't stopped since!]

He's received a lot of complaints from people, pointing out that FCP 7 still works, so why the sudden rush away? Walter offers his reasons in this article:
It’s still the same inefficient tool with the digital formats that have been brought to the post production marketplace in the two years+ since it was originally released.

I have been planning to move away from FCP 7 for 6 months now at least and while I knew FCPX would not be the replacement for us back in April, I did wait until the final public product to make the final decision.
BiscardiCreativeBlog: We’re not “Throwing the Baby out with the bathwater.”

See also:

Buy (and download) from the App store

No comments: