Has anybody actually been able to import an FCP7 XML into X yet? Having trouble here![]()
Glad they're at least letting everyone try it first...
Now if they can give us proper monitoring, batch export, a better way to see source timecode, and aaf/omf support, it'll be 3/4 of what the old FCP was![]()
What would some of you prefer Apple do, not listen to user feedback on v1 software and work hard to address it?
Total crap! Are you even an editor?
I'm a professional cameraman & editor and to be honest I really like FCP X, it doesn't do everything I want, and yes its buggy (10.0.1 has just finished downloading so I'll try it after finishing typing this) but to be honest when I go back to FCP 7 I start to miss the features in FCP X. I've now cut loads of projects on it (some have even been broadcast on national TV!) and its been a dream. In fact several projects are repeats of old projects and I've cut them in half the time it took me in FCP 7.
Yes it's not for everyone, but then neither was FCP 7 which is why Avid, Quantel etc are still doing roaring trade.
Sorry its total rubbish that FCP X isn't pro - when was the last time an amateur piece of software had decent accurate scopes, or able to sync dual
sound systems. Oh and how many amateurs do you know that work of an XSAN (which FCP X as of the updates does!).
Has anybody actually been able to import an FCP7 XML into X yet? Having trouble here![]()
Glad they're at least letting everyone try it first...
Just to play devil's advocate here:
Apple released this stating specifically this is not so much an upgrade, but a complete redesign of the Final Cut Pro series. They released it at a VERY reasonable price.
BUT I think their heads were in the sand releasing it lacking so many important professional grade features. They may not had been as forward thinking as they should have with the professional in mind on the release. If you are going to release a professional software with complete overhaul, you probably want to make sure it has everything that is vitally needed in the software BEFORE it is released.....OR release it as a paid Beta with the very competitive price of $299 for early adapters while keeping previous versions available and supported until the general fixes are comfortably completed.
They dropped the ball on this release, but they obviously acknowledge this and are working to fix it. Offering the trial is helpful, keeping the previous version available is also key. At some point FCPX will obviously be up to spec with what professionals need, and THEN the complaints will end, but is definitely one time Apple deserves what they hear.
Did you even read the article?According to Apple's FCPX site, it doesn't say a word about FCP7 compatibility. I'm interested to hear if people are able to import FCP7 XMLs or if they're still left in the dark...![]()
I don't care how many times Apple loyalists repeat this phrase, FCPX is NOT v.1 software. If it was then they never would have pulled Final Cut Studio from the shelves forcing professionals to use inferior software. Period.
I do not see the update in Software Update or in the App Store or on the Apple website.
Any advice?
Also, i bought FCPX in the App store but it is telling me I did not purchase it there. Weird!
Yoak...
I just read on the kenstone fcp forum that someone spoke with Apple about the problem getting the update and they are aware of the issue and say that it might be available tomorrow.
From what I've read, this update does NOT add FCP7 XML import to FCPX. What it does do is introduce an entirely new flavor of XML that is specific to FCPX.
http://forums.creativecow.net/thread/335/15996
... when "typography" was obsoleted by Apple & Adobe with the MacPlus and PageMaker. It doesn't end well for those who do not adapt*.
Just saying ...
*Sometimes "new paradigms" are worth learning. What's that old saying, oh ya, "Adapt, or perish."
From what I've read, this update does NOT add FCP7 XML import to FCPX. What it does do is introduce an entirely new flavor of XML that is specific to FCPX.
http://forums.creativecow.net/thread/335/15996
"I'll try a system reboot and see if that affects anything."
Okay, rebooted system and now XML works. Odd, since I'd just rebooted the machine before testing.
Sorry for creating a stir everyone.
There are some off base assumptions going on here. First, you assume that everyone will be happy using an aging, unsupported FCP 7 for years on the premise that FCP 10 will eventually meet their needs. This is a false assumption, IMO. FCP 7 was merely a bump up from FCP 6 which came out in 2007. People have been waiting a long time for a significant FCP update and when 10 was launched it fell short of meeting their needs so they went to Avid or Adobe. What was labeled as "knee jerk" by many was actually a transition years in the waiting w/the release of FCP 10 being the final, deciding factor.Right. Did you think that any of those companies were going to immediately switch over to a dramatically new version of Final Cut anyway?
I'm starting to understand Apple's moves here as being a bit more sophisticated and nuanced than most detractors are giving them credit for. Who would think - legions of internal marketing and development teams actually know more about releasing products than random, anonymous Internet users?
1) They release a major upgrade to a piece of software at an excellent price point, fully expecting smaller-scale users to be the first ones to switch. They know that certain features won't make this x.0 version, but that won't stop plenty of casual users from testing the waters. It's also the perfect chance to test the product in the field before it gets picked up by major studios.
2) Over the next few months/years, they release the "key" features that will allow higher and higher tiers of editing shops to migrate their processes. Today we get XML, XSAN, etc. Next year it'll be multi-cam and who knows what else.
3) Within a few years, FCP 7 will be a memory of the past, and younger editors will have been trained on FCP X from the outset. Larger studios, at least the ones who weren't on Avid to begin with, will switch over. Some major motion film will be finished in FCP X, and finally it'll be a true replacement for its predecessor.
Sounds like a damn good plan, actually.
I got the same message. I managed to upgrade compressor, but not fcpx.
Where else would one have bought it than the app store?
I started a thread about it in the video section, so hopefully someone figures it out
The big disconnect is that both these types of people/editors (both the ones who are independent and the ones who work for large production houses) are considered PROFESSIONAL EDITORS, and rightfully so... they both edit video for money in a professional context. So when people gripe about FCPX not being for Pro editors, it's only partially true. The issue is, who gives Apple more money in the end... Production houses who are buying large seats of licenses, or individual pro editors? This is who Apple focuses on, and I think the answer is pretty clear given their recent trends.
Well said there are different types of pros, bottom line If you work in an environment where you need to share and use tools that were taken away then it's not for you and totally understandable you are peeved
If like me you are a small company editing on one system It's great though needs a lot of work on bugs etc
The argument on it being pro or not is not applicable as it it depends on the pro envolved.
P.S. I think it is 10.0.1 because they might be using the same naming convention as OS X
I'm glad Apple fixed SOME of the issues but the multi-cam in 2012 just means most professionals won't switch until at least 2012.