-
10.0.9 is out. Just a minor update.
-
That’s me as well. Switched my interim laptop with my wifes 2011 iMac while waiting for the new MacPro. It’s been a competent machine, but I’m excited to be on a Mac Pro again. The lack of an SSD in this thing after having one in the laptop is especially painful.
There are very few things I could see being “exclusive” to the MacPro. This discounts the general speed and performance benefits that come with a faster machine.
1. BACKGROUND, background rending. Apple says as much on the MacPro website. While perhaps not technically MacPro exclusive, this feature could very well be limited to dual-GPU machines.
2. Dual scopes. Again, this could possibly be tied to dual GPU setups.
If Mavericks does bring some OS based enhancements, then perhaps 10.9 might be required to run FCPX 10.1. I’m sure that would cheese some people off, but Apple is very keen to keep users up to date with OSX. At this stage, there’d be very few machines that people would want to use FCPX on that couldn’t run Mavericks.
While the MacPro is a nice tie-in to launch a major new version of Final Cut, I truly hope that there will be much more meat to ACTUAL improvements in the software. We’ve been getting a couple features here and there for 2 years now, but with a YEAR between 10.0.6 and now, there’s development room there to make some BIG improvement to the software. In UI, in editing workflow, in cross-program compatibility…
They’ve had a year to execute on user and industry feedback- if MacPro optimization is the big FCPX news this fall, I’ll be a bit disappointed.
-
It’s going to be a big deal.
🙂
-
I think it will too. At least I really hope so.
After moving 2 of my clients over to FCPX in the last year, I’ve run into some resistance from a couple of my other close-working still-FCP7 editors. They know and trust me, but the volume of negativity from other people they know in post can be, I’m sure, unsettling. My response, and I’m fairly sure I’m correct, is that much of the sh*t talk is coming from editors who’ve either NEVER opened the software, opened it make a quick judgement and bailed, or finally tried it VERY early on and haven’t kept up with how big the improvements have been.
While features are nice, I think by biggest hopes for 10.1 are at a very fundamental level. FCPX presents some radical departures from other NLEs. Where they’ve implemented a complete solution, like Event metadata and logging structure, the benefits are clear. Its in the timeline that I think FCPX needs to fill the gaps and make a clear case for the magnetic/connected/”trackless” paradigm they’re presenting. The Project timeline is a mess, and desperately needs to use the metadata at least as effectively as Events do in terms of organization. As I’ve said many times before, right now the Project timeline is like The Event browser if there were no Keyword/Smart collections. It’s a soup of clips. And while in simple timelines that’s no an issue, the deeper it gets the more frustrating it becomes.
Especially after seeing Stack Tracks in the new Logic, I can SEE very clearly a Roles-based structure which brings clear organization back to the timeline, without sacrificing the flexible editing that FCPX “trackless” editing allows.
-
[Marcus Moore] “It’s a soup of clips. And while in simple timelines that’s no an issue, the deeper it gets the more frustrating it becomes.”
Cpmpletely, but there has been major change in the timeline since 10.0.0, we just need more of it.
I’m sure that Apple is on it.
Reply to this Discussion! Login or Sign Up