Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases Major Update and Free Trial for Final Cut Pro X
- Thread starter MacRumors
- Start date
- Sort by reaction score
I made the switch from 7 to X and am really glad I did. There are some things that I revert back to 7 for but they are few and far between and although I had to retrain myself I find my projects have much improved and I enjoy my work more than I used to. Each improvement is anticipated and welcome of course but I like X very much already.
Xsan support is... lacking
"You can store your Events and projects on a storage area network (SAN). These network storage locations give you more options for storing your media and streamlining your workflow over a high-speed local network.
Although you can access SAN locations from different computers on a network, only one installed copy of Final Cut Pro can use a SAN location at a time. If you have Events or projects stored on a SAN location, you must remove the location in Final Cut Pro to make it available to other computers on the network.
The SAN location feature requires a SAN volume, such as an Xsan volume connected using the Fibre Channel Protocol (FCP)."
Hmmmm.... Kind of defeats the purpose of having a SAN. D'oh!
"You can store your Events and projects on a storage area network (SAN). These network storage locations give you more options for storing your media and streamlining your workflow over a high-speed local network.
Although you can access SAN locations from different computers on a network, only one installed copy of Final Cut Pro can use a SAN location at a time. If you have Events or projects stored on a SAN location, you must remove the location in Final Cut Pro to make it available to other computers on the network.
The SAN location feature requires a SAN volume, such as an Xsan volume connected using the Fibre Channel Protocol (FCP)."
Hmmmm.... Kind of defeats the purpose of having a SAN. D'oh!
FCP7 XML not recognized in FCPX???
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...
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...
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...
Thread about FCPX - FCP7 XML on Creative Cow here: http://forums.creativecow.net/thread/335/15996#15996
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
Yep. 4/4 would be no changed UI. So what happened to proper monitoring. I have not heard anyone (not even apple) address monitoring - any news on that front.
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.
as a cameraman you should keep your hands of from editing leave that to the pros. i work with avid composer since 1995 and with premiere since 2 years. final cut x missing basic needs. you know that. no one need scopes without basic functions like a magnetic timeline.
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...
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
Let's see, previous 2-3 upgrades to FCP STUDIO including motion, dvdsp, color, compressor, soundtrack, etc. were ONLY $299. So, yes it is a cheaper price for those that are just starting out. But a MAJOR penalty to those that are going from FCP 7 to X whether it's an upgrade or not it is at a minimum a $100 increase in price for much less functionality. And to those of you just starting out, it's costing you $400 for less than half the amount of software included in the previous "studio" package AND there will be no upgrade pricing in the future so you can plan on your upgrades for less software costing more than the studio upgrades were. Somehow Apple has made people think either of these two scenarios are anything but a cost increase. Wow. Netflix should take some lessons.
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...
Yes, BreuerEditor did read the article. The article is from cnet, and Breuer is saying Apple's site doesn't say the same thing. Turns out, cnet's wrong!
http://forums.creativecow.net/thread/335/15996#15996
Well exactly. It's version 10 software. Nobody really knows what happened to version 8 and 9, but I suppose those were the internal build names of iMovie 09 and iMovie 11.
Basically, the whole mess should've have a new name and they should've just EOL'd FCP 7 over the next year with minor upgrades to keep it functioning throughout Lion's lifetime. People would slowly start making the switch to iMovie Pro (or whatver they wanted to call it) and continue using or buying FCP 7 knowing very well it wouldn't be supported in the year or so to come.
It was handled worse than new coke. Those of you that weren't in high school in the 80s don't know what that was.
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
Thanks for this info Isilver, hope you don't mind me quoting your post in my other thread for others to see there as well.
Bummer. Hopefully a good XML translator arrives in more than just the 'Automatic Duck $500' flavor.
You're lecturing people who have likely switched between more programs you can count on your fingers. The FCPX problem isn't paradigm, it's core functionality.
I just read the post. The guy who started the thread finally posted this:
Not sure if that means it will import FCP7 or not.
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.
Second, you assume that Adobe and Avid won't continue moving forward. They've been doing a lot of things right the last 2-3 years and I don't see them standing still any time soon. I think Apple will continue to lose ground and then eventually gain some of it back but I doubt they'll reach the same levels FCP 7 did in the broadcast and film arenas. They are shooting for a broader market w/FCP 10 and I think they'll hit it.
If the utter disaster that was the FCP 10 launch is a sign of what the "legions of internal marketing and development teams" at Apple are capable of then I think they need to do better in the future.
Lethal
I too had this problem but I googled it and found out that if you put your Final Cut Pro X app in a new folder in the applications folder then drag it to the trash then the app store will allow you to download and install the update. Workded for me!
B
bikemonkey
Guest
Christ. How can people still be whining?!
If you're not convinced with Apple's road map, and efforts so far, fine, go and switch to Adobe or Avid. I don't care. I don't care if Apple lose you as business and, most of all, I don't give a flying blue-arsed monkey ***** about justifying your position lofty position of esteemed video editor who practically invented broadcast editing. That has ***** all to do with the actual constructive development of FCPX, unless you are in fact communicating your feedback to Apple.
I've watched a lot of cool stuff in my time, and I hope I can continue to do so. But, honestly, I don't care how it's made. Yeh, I can understand your frustration but I can't understand your attitude. At least acknowledge that Apple is trying to make amends, and try to be grown up in your response. And, if that isn't enough, move on.
FCP still needs work, I get that. But I'm guessing most of you don't understand software development, just like I haven't a clue about stereoscopic production. We all have our specialisms and, whilst I don't work for Apple, I'm pretty certain they didn't issue the update any earlier because it simply wasn't ready. If they'd issued a buggy release there would be even more complaining, and then I might actually pop a vein.
If you're not convinced with Apple's road map, and efforts so far, fine, go and switch to Adobe or Avid. I don't care. I don't care if Apple lose you as business and, most of all, I don't give a flying blue-arsed monkey ***** about justifying your position lofty position of esteemed video editor who practically invented broadcast editing. That has ***** all to do with the actual constructive development of FCPX, unless you are in fact communicating your feedback to Apple.
I've watched a lot of cool stuff in my time, and I hope I can continue to do so. But, honestly, I don't care how it's made. Yeh, I can understand your frustration but I can't understand your attitude. At least acknowledge that Apple is trying to make amends, and try to be grown up in your response. And, if that isn't enough, move on.
FCP still needs work, I get that. But I'm guessing most of you don't understand software development, just like I haven't a clue about stereoscopic production. We all have our specialisms and, whilst I don't work for Apple, I'm pretty certain they didn't issue the update any earlier because it simply wasn't ready. If they'd issued a buggy release there would be even more complaining, and then I might actually pop a vein.
If you actually talked to the pros out there, particularly the ones that use multi cam etc, you'd likely find that they were never planning to switch to FCPX before 2012 anyway.
Because no real pro switches to new software right away. These are six figure and up gigs for many. No way are they crazy or dumb enough to switch before they have learned the software inside and out, tested it thoroughly and so on