Marcus Moore
Forum Replies Created
-
It may be that both iPhoto and Aperture were both going to require just too much recoding to work at the core of this iCloud-based photo solution.
Perhaps the critical decision was made to just start from scratch. Combining the apps and making everyone happy will be an ENORMOUS challenge though. The type of challenge I don’t think they’ve met before.
-
[Aindreas Gallagher] “so as I understand it, twenty editors, trained by him in the BBC, are editing or re-editing 30% of BBC output. okedoke. that all seems in order.”
I got some followup info from the guy. Here it is verbatim-
Ollie Kenchington,
“Simon Catt, head of BBC’s re-versioning unit in London. He looked in to Premiere but stuck his neck out and moved his whole dept. to FCPX. At the end of the course, he said he knew he’d made the right decision. As they re-edit a lot of other dept’s output, they effectively finish 30% of total output.” -
As Philip says, be wary if you need XML, any 3rd party apps, like X2Pro, will need to be updated.
-
Here’s what I don’t get. How do they launch Yosemite this Fall without Photos?
I guess they leave iPhoto in there for now and then update it with a 10.10.1 or something.
-
If they know they’re going to be EOL’ing Aperture, I do give them credit for announcing it sooner rather than later- like this fall when Yosemite ships or just before the new app is released next year.
Thank goodness they made special mention of FCP and Logic in the PR. Or I’m sure thousands of lines of speculation would have resulted.
Though the release makes it clear that you’ll be able to migrate from Aperture to Photos- what sort of relative feature set Photos will have is, of course, the BIG question.
It’s hard to imagine a single app squaring the divide between iPhoto and Aperture though.
-
There aren’t too many things Motion users can hold above their AE counterparts, but I know that AE was (I hope not still is) requiring workaround for reflections while Motion has had them since version 4.
And if I think back maybe Motion’s build-in particle generator was ahead for a while. But anyone who’s serious about that stuff is using Particular anyway.
I very much hope that the FXPlug3 support in Motion encourages developers to bring some of the more popular 3rd party plugins to Motion.
-
That just doesn’t jive with what I’ve heard about the X team spending lots of time (not publicly, mind you) trying to get the software into more complex workflows where they see an opportunity.
That said, depending on what Disney meant by “collaborative”, X may just not be ready for their needs in whatever timeframe Disney UK needed.
-
[Aindreas Gallagher] “so as I understand it, twenty editors, trained by him in the BBC, are editing or re-editing 30% of BBC output. okedoke. that all seems in order.”
Yeah, I don’t get that statement either. If true, they must be talking about a percentage of work for a specific group or division.
BBC just isn’t centralized (or small) enough for that statement to be possible.
-
In the interest if full disclosure I’ll just quote the original message in its entirety. Veracity TBD.
Ollie Kenchington-
“I’m an Apple Certified Trainer for FCPX and am currently delivering back to back FCPX101 courses for the BBC. 20 of their staff editors are moving up to X from 7, with my guidance, and they LOVE it. Their lead editor told me that they edit (or re-edit) 30% of all the BBC’s output.”If (being the operative word) the above is true it sounds like more than testing, but actual adoption.
-
Maybe it shouldn’t have taken this long, but ANY platform move (no matter how beneficial it would be) can take years at a given company, based on training and budgetary considerations.