Marcus Moore
Forum Replies Created
-
Set your clock for a year from now I think you’re be warmer.
-
I don’t necessarily see any connection between hardware announcements and the imminent FCPX update.
At WWDC, 10.0.5 was tied to the premier feature of the centrepiece hardware of the keynote.
I don’t think another size of Retina MBP, or a MacMini/iMac update brings anything new to the table to tie into. Even if the iMac came with Retina screen (insanely doubtful), FCPX has already been updated for Retina support.
10.0.6 and all the goodness it will bring could come out tomorrow, or it could come out a month and a half from now. At this point I think each Tuesday has an equal chance. My only opinion on it at this stage is that I doubt it will be released in December. Noone releases anything in December, software or hardware. So I say between now and November 27th.
-
I get paid to edit in FCPX, and I find your solipsistic, self-centered viewpoint franking insulting.
Today’s FCPX user is tomorrow’s Pro, and they’ll continue to use it if it grows with them; the same way Legacy FCP did, the same way Premier did, and the same way Avid did way back (and yes, I was there and using it myself).
It’s lame ducks like you poisoning the well with your apparent bias that makes it really hard for people like me who’ve given the software a chance– and found it not only not awful, but pretty remarkable in a lot of respects. But you know what, when I DO get to sit down with those people and show them FCPX- not one of them has left the meeting thinking I was crazy.
After 20 years of NLEs chasing the same paradigms, I’m thrilled… ABSOLUTELY THRILLED to see someone innovate in this space. Even if everything FCPX proposes doesn’t end up working out, even if FCPX eventually does go under, I’m glad someone took the chance on trying something new.
If you don’t like it, fine. You’ve got your own way to work. Awesome. But personally I’m glad that there’s more than one binary process now. Editors have a choice, and that differentiation in the market can only make all products stronger.
-
I alternately thought you were insane and dead-on in this. Bravo.
-
I think there’s a big analogy to be made with AE. While AE is capable on it’s own to do lots of work- it’s real strength in market is the verbose plug-in support which allows it to expand into areas that aren’t necessarily worthwhile for Adobe to build-in to the software.
If Apple can create a solid foundation in FCPX that 3rd parties can build on, then everyone’s needs are met without having the software bloat (and cost) of a features you don’t use in your specific workflow.
And while I know that using a 3rd party plug-in for importing FCP7 projects into X might seem a real user deficiency, just ask anyone who has had a problem with translating their projects using 7toX how fast Philip and Intelligent Assistance can react and get a new build out to the appStore. If this was built in functionality, then those same users would have been waiting on average 3 months for improvements to come with FCPX’s updates.
On the MacPro side. Someone can correct me if I’m mistaken, but after looking at Intel’s Xeon website- how was anyone expecting a new MacPro to integrate USB3 and TB; since those technologies aren’t embedded into the chip. Seemingly this is why it took until IvyBridge for the laptops to get USB3, since it was the first chipset with support built in. So if that’s the case, then it wont’ be until the next Xeon (Hasslebridge?) that we’ll see that, which should line up with a late ’13 launch of the MacPro replacement, AND the feasibility of producing 27″ Retina screens in volume. It seems to me they decided to take the short term hit and wait until they could make a big splash next year. Rather than providing a confusing no USB3/Thunderbolt update as an interim step toward the real relaunch of the product in whatever form it’s going to take next year.
-
I’m a big FCPX supporter, and have been using the software primarily now since March.
That said, I don’t begrudge any company for moving to another platform. The simple fact is that FCPX is not yet ready for every workflow. Companies have to produce work, and you can’t wait for the software/hardware to be ready. You have to go with the option that fits your needs.
We’re going to keep seeing these articles for a little while longer, but I don’t think this will last. I personally don’t believe that Apple has any intention of abandoning the upper tier broadcast/film market long-term. Every update to FCPX brings back more of the features that are necessary for those markets.
What we have here is a unfortunate alignment of transitions in 2 product cycles. On the hardware side, we’re waiting for whatever the MacPro replacement is going to be in 2013. On the software side, Apple decided to completely re-write FCP and ruffled a lot of feathers. It really too bad they’re both happening a the same time because the backlash from one is just adding fuel to the fire about complaints on the other.
FCPX continues to reintegrate (and IMHO improve) legacy features. New Pro hardware next year. If AFTER Apple’s cards are on the table anyone wants to make claims about who their products are meant for, then be my guest.
Finally, and I can’t say it enough, FCPX was an unmitigated marketing disaster. A one year open beta program, with a clear timeline for transition, would have made FCPX more of an exciting future prospect, rather than the scary/disappointing/incomplete product is was at launch. Apple is STILL not brining it’s A game to this problem, and they need to. Otherwise, the perception of FCPX’s failings are going to linger long after it addresses them technically.
-
Except SHAKE hadn’t had continual updates for the past year and a half. Though 10.0.6 has been a bit longer coming, let’s not forget that FCPX has seen 5 updates in the past 16 months. That’s a faster update track that legacy every had.
The Programs that weren’t going to survive the purge are already gone: Color, SoundtrackPro, DVDStudioPro. The functionality of those programs has either been deemed better suited to be handled by 3rd parties or has been (or is likely to be) folded into the FCPX, Motion, and Compressor. With Logic likely seeing a more integrated role into the suite in the near future.
-
Well, I certainly doubt we’ll have to wait THAT long. I can’t remember Apple releasing anything of substance after mid-November. So I would be absolutely astounded if 10.0.6 isn’t released by then.
They’re way over their regular schedule. The longest update cycle up to now was 10.0.1 (91days), and it’s been 119days since 10.0.5. So I think every Tuesday (the day updates have generally occurred for FCPX) is potentially THE day.
The longer it is, the more I think they’ll have packed in there.
-
I think the one’s they’d be demoing by NAB2013 WILL be new features, not the legacy reintegration updates that we’ve seen so far (as modified and enhanced as they’ve been). I figure we’ll have 2 more feature updates and 2 more maintenance updates by then 10.0.6-10.0.9. Then it will be mostly new territory, I think.
I think they NEED to come back to NAB for exactly the reason you mention.
And I’m fine paying $299 bi-annually for software that nets me tens of thousands of dollars in work.
-
I think the odds of the next update being paid are VERY slim.
I’m still imagining we’ll see a preview of 10.1 at NAB and a paid upgrade in June.