Marcus Moore
Forum Replies Created
-
I’d hesitate to guess that this is the second time in 2 years that FCPX development has been at least somewhat guided by hardware support. Last year with the 10.0.5 Retina release for the rMBP at WWDC, and now for the new MacPro. While both of these are nice, I wonder how much further along things would be in other areas if Apple hadn’t had to align with those hardware releases.
-
[Oliver Peters] “The real concern, now that Apple has decided software updates are free, is that there is no external driver for feature improvements. The “rapid updates” mantra is nothing other than marketing spin. For all we know, there are very few engineers actually working full time on FCP X software development.”
On your first point, IF Apple has decided that you’ll only ever need to buy FCPX once (and I don’t think we can make this assumption just on this release), and updates are free in perpetuity- then the driver for Apple is most likely hardware. If Apple can sell customers a Mac (from a few thousand to higher-end MacPros) every few years), I think that more than makes up for $299 every 2-3 years.
On your second point- with the OS oriented (let’s not forget that this couldn’t’ have been released any earlier than Mavericks) structural changes to the database, those foundational changes may have prevented/delayed more surface work. Alex4Ds iMovie blog posts certainly point to LOTS of features under development in the code that were not there in 10.0.9. Plus, with the quick slipping of dates, it certainly seems like this release of FCPX was waiting on the MacPro, rather than the other way round. Weeks, or perhaps even months.
Finally, the info I’ve heard is that the FCPX team is not reduced in size from what it was 3-4 years ago.
-
One update that’s not on that list that surprises me is the save/versioning enhancements- which was addressed.
Along with FCPX’s automatic saving, the autosave vault has returned. While “Snapshots” allows you to do multiple named “saved states” of the same project file, pretty much eliminates the need for endless duplication of projects.
-
It’s hard to say at this point if Apple will be motivated to charge for an X update.
If FCPX is getting people to buy a Mac, THAT’S where their profit centre is.
-
Thanks for the correction.
-
Until today (should 10.1 be released tomorrow) we were 4 for 4 FCPX feature releases on Tuesdays. That’s not prognostication, that’s a trend!
If I had to lay money on which day of the week the next feature release would come, I’d still bet Tuesday.
-
How are you making a call on which processor to get? I’d pull the trigger tomorrow but I need to see some real-work FCPX and Motion specific benchmarks with the various CPUs.
-
But with no monitors. If Apple surprises us with a 4K display, I’ll scream with joy while my wallet will scream in terror!
-
Probably more like $9,499. The spread on US and CAN prices of Apple products is pretty narrow right now.
-
As someone who got burned, I would say no- it’s not terribly risky. I’ve done it many times on other computers.
In years past it was a much easier decision to go after market because the price-spread was so much wider. If you bought your RAM from Apple you were paying a huge convenience premium.
In recent years the price gap as narrowed somewhat, but the stigma of MASSIVE overcharging still lingers.
In this case, with that price gap, I’ll find my savings somewhere else. But it IS $300.