Marcus Moore
Forum Replies Created
-
110 days this Tuesday. Apple’s guidance is 3-4 months.
This month, I’d wager. Before WWDC.
-
Now that compressor has been updated properly- Aperture is the last of the ProApps that needs a serious overhaul. But I haven’t heard a peep about Aperture development for quite some time.
-
I would be disappointed to see tracks return. It works very well for me at the moment, but I’m more than willing to admit that improvements need to happen before it’s a “no excuses” alternative to track-based workflows.
I see some really promising ideas with Roles, and I hope Apple follows thru.
-
Even as a staunch FCPX user, on this point I’d agree. Adobe has had a great, steady update cycle over the past 3 years, and I think even improved since CC transition (since they no longer have to “horde” features for an update they have to convince their users to buy every year).
I think they do two solid feature updates a year. One announced at NAB and released during the summer, and one around IBC and released near the end of the year.
And I think that sounds about right, especially for evolving applications like Pr and X.
I hope Apple gets back to that this year.
-
Sorry, yes, in reply to OP.
-
I’m all for stability and performance improvements. If we could make the decision for one over the other, I think most people would want a rock-solid version of what we have now.
That said, I’m not sure the FCPX team has to make that choice. Are the same people who fix code bugs and improve performance the same people who design new UI and features? I think if the team was only interested in stability improvements, chunks of the team would be sitting around with nothing to do.
-
Really, you should only need to use something like this over an entire timeline when something has gone horribly wrong on set.
If the client complains about rendering time, then tell them to get a better shooter next time! Unless you’re also the shooter, then it’s your mistake. 😉
-
Yeah, it’s Neat Video. Great plugin, but a pig for rendering, and probably not optimized for the MacPro yet.
-
With ProApps like Aperture (a VERY promising app early on) disappearing further and further into the rear view mirror by it’s competitors, it’s of course always going to be worrisome that the same thing will happen to X.
And while we just plain don’t hear anything about Aperture development, everything I’ve heard from people who have spoken to the team, indicate that this is NOT a product that they intend to languish.
As I’ve outlined in a few places, I think development has been caught behind some walls that were not of the X team’s creation. The new Library structure required Mavericks, so it just plain couldn’t be launched until it 10.9 was in October. And even then it was another 3 months until the co-ordinated MacPro/FCPX 10.1 launch in LATE December that we finally saw the update.
I’m really hoping that the X team can get back onto more regular feature updates now, unrestrained by having to couch to any new hardware or software shifts. I definitely want to see the slowing progress of updates reversed with a nice feature update with 10.1.2 in the near future.
-
Agreed about 10.1. I think those were foundational changes which probably forestalled some other, more surface level, feature work.