Marcus Moore
Forum Replies Created
-
Caveats, of course. It comes from a certified trainer who says he’s in the middle of 2 back to back FCPX courses at the BBC.
I read it this morning, and just thought that I’d toss it in here. Though I’m not sure which part of the BBC it is he’s talking about- news, drama, documentary.
-
Tangental to this (and sure to break Aindreas’ mind), someone on Facebook recently posted they’ve been training 20 BBC editors for the transition from 7 to X.
-
I like your logic!
-
I don’t think anyone has looked at his 4 blog posts and come up with a consolidated list of what made it into 10.1.
I know he’s found a lot more stuff than has actually been implemented. Alex’s earliest discoveries around “Collaborative Workflow” guards still haven’t made it into the released software yet.
-
I dunno, I’d suggest we’ve already seen more evolution to X in the last 3 years than legacy FCP had in it’s decade of active development. While there were feature additions, and eventually Studio cross-platform functionality (parts of which never worked properly), X has already seen one massive foundational change with the 10.1 Library structure.
You’re right, it’s hard/impossible to say what the “end game” is for FCP X. Is more cross-application support coming ala the old Studio model? Are there more Pro Apps coming to fill out the picture? Does Apple plan to build up the internal feature set so only super-specialized workflows need to go outside? Or does Apple see FCP X as a platform on which 3rd party tools play an important part of filling out the needs of different workflows?
Every NLE in the last decade has wrestled with questions like this, and I don’t think anyone has the right answer- at least not for everyone.
At the core of what makes X special is the differences it has from other NLEs- those are the things I’m most keen not to have them give up. That they’re preferred or right for everyone isn’t possible. I’m glad there’s traditional track-based solutions out there, but I’m also glad that there’s a different solution available as well.
-
While I think some built in LUT controls are nice, the depth and breadth of LUTs provided by Denver’s LUT Utility is pretty hard to match- All the different film stock emulations and variables… It’s probably still a good investment.
-
It appears versions of FCP X are the engine at the core of iMovie, with essentially a walled-off UI and limited/alternate feature set.
Alex found a version of 10.1 at the core of iMovie 10 released last October- a full 2 months before the FCP X update was released to the public. That pretty much told us about the new combined Library structure.
So it’s clear that FCP X is in the driver seat, with pre-release builds being integrated into iMovie updates.
There’s not as much new stuff here, but who’s to say how far along the next FCP X update was when this code was ported to iMovie.
Interesting stuff though.
The two highlights for from his article are the LUT support and possible XML import/export improvements.
-
Likely- Scott Simmons on twitter is saying not to expect too many surprises on the video side. We got our news at NAB.
-
I’m not sure I understand the issue. Wouldn’t you be required to actively maintain your AELP membership if that’s how you purchased the software? Regardless if updates are free or not, I’d think you’d have to maintain enrolment in ALEP to continue to have access to the software.
Maybe I’m not understanding the Program correctly- it’s an education volume purchase program, right?
-
You’re right, but the rumours typically go that OSX developers get moved to iOS to meet a delivery deadline (or vice versa as was the case this year).
But I’m not sure Pro Apps devs fall into that same pool. Maybe they do, but the rumours of when that’s happened haven’t pointed to it.