[Marcus Moore]

Yes, and they have been.

Even if you discount maintenance updates (which in many ways are as important than new features), FCP X has been updated much more frequently than in the Legacy days.

10.0.0-10.0.1 91 DAYS
10.0.1-10.0.3 133 DAYS
10.0.3-10.0.6 266 DAYS
10.0.6-10.1.0 428 DAYS
10.1.0-10.1.2 190 DAYS

10.1 took seemingly forever, and is well out of line with the rest of the updates. I think maybe there was a lot of debate about scrapping the Event/Project structure, who knows… And I have heard rumours that 10.1 may have been sitting around waiting for the MacPro to launch. Regardless, 428 days is still less than the 2yr + cycle of the Legacy days.

With 10.1.2 reversing the trend of ever-expanding intervals, I certainly hope they can keep to a roughly “twice a year” update cycle, in much the same way Adobe had with Premier CC updates.

[Marcus Moore]

I wouldn’t equate it to anything to do with mobile. It’s an entirely different market.

Only Apple knows it’s numbers for sure, but it seems certain that Xserve was never a big player in the server space overall, and I don’t think the specialized hardware provided enough of a benefit over burgeoning technologies like Thunderbolt, which was announced on the first Mac not long before or after Xserve was EOL’d.

[Marcus Moore]

I wonder of Thunderbolt had anything to do with it? With with lower-cost, higher bandwidth storage no longer the realm of fibre-channel arrays, could Apple have seen solutions like Xserve becoming an increasingly small niche?

[Marcus Moore]

Apple is more into enabling connectivity than the hardware.

Thunderbolt continues to take lumps because it’s not as popular as USB3…. well DUH!

But here we are with Mac with a 20Gbps I/O, and next year it’s going to be a 40Gbps.

And iCloud is still finding it’s legs, so if a collaborative solution is going to sit on the back of that- we may still have a while to wait.

[Marcus Moore]

I think if there’s an update with that quick of a turnaround, then 10.1.4 will be another maintenance update for Yosemite compatibility.

I did this post a couple months ago on when 10.1.3 might be released. Took all the maintenance update intervals and it came out like this-

https://disproportionatepictures.blogspot.ca/2014/08/final-cut-pro-x-whats-next-1013.html

Apple ended up being pretty much smack dab on the average.

So I’m prepping another post on when we might see 10.1.4, presuming it’s a feature update, using past dates.

[Marcus Moore]

I haven’t opened FCP7 in 2 years, so no issues there…

If history holds, Yosemite will be out in late-October after a Special Event for iPads, Macs, and anything else Apple want to announce for the holidays.

If there’s going to be another FCPX update this year, I wouldn’t expect it until after that, maybe even December again like 10.1.

[Marcus Moore]

What’s included? Anything interesting?

[Marcus Moore]

I would agree, except that Motion has become a defacto graphics engine for Final Cut- so I think it’s too tightly integrated (even without round-tripping- grrrrrr…) to be EOL’d at this point- the only other option I see is if it’s abandoned as a standalone product and wholly absorbed into FCP X.

[Marcus Moore]

I think there was a time around 2005 when Apple would have had enough money and possibly the inclination to buy Adobe- but I think those days are long gone. They still have the money to do it, but no will to do so- and that’s if Adobe was even willing.

[Marcus Moore]

I don’t know-

You’re right, other than a the UI update and the FCP X integration, no serious feature additions have been made to Motion since Version4.

I think much of Motions functionality could come from 3rd parties, if Red Giant or Trapcode plug-ins could make their way over I think it would fill many gaps.

The big hole in my mind right now is a really well integrated 3d motion tracker. SynthEyes is probably the best solution, but it’s not well integrated.

I need broadcast monitoring back as well.