-
Future MacOS/FCPX won’t support DNxHD/HR or CineForm among other codecs
-
I would assume that third parties will convert the footage to one that FCP X’s future versions will be able to edit.
But for still in use media formats this would be a giant step away from Apple’s updating FCP X to meet the needs of media creators of all levels. Just like I hope that classic films don’t become unavailable or even lost, I hope we can forever bring up old projects and give them new life. You can do a period piece; but you’ll never be from that period again. Will we ever return to artists becoming masters and passing that on to the next gen? Personally I’d love to see a movie from early days, B&W silver emulsion, on a silver screen at the frame rate it was shot in.Imacs (i7), Canon C300, Canon 5D Mark IV, Panasonic ENG HPX250P, , FCP X, teach video production in L.A., Cool Light Productions, Producing series of multimedia Portraits of creative women in the production arts.
-
Good explanation by Jon Chappell at Digital Rebellion:
https://www.digitalrebellion.com/blog/posts/thoughts_on_32_bit_codecs_being_phased_out_in_macos
– Oliver
Oliver Peters – oliverpeters.com
-
over my head … but he did end with this…
“… the solution is to allow third-party extensibility in the new frameworks. I’m not holding out hope that this will happen, and our ultimate goal is to be cross-platform so we’d probably go down the ffmpeg route regardless, however if enough people complain they may at least continue to support some additional codecs in FCPX…”
not sure why he doesn’t think that will take place??? … great opportunity for plugs ins.
Imacs (i7), Canon C300, Canon 5D Mark IV, Panasonic ENG HPX250P, , FCP X, teach video production in L.A., Cool Light Productions, Producing series of multimedia Portraits of creative women in the production arts.
-
[Craig Alan] “not sure why he doesn’t think that will take place??? … great opportunity for plugs ins.”
It’s much more involved than simple plug-ins. Apple would have to create/add/enable/allow a framework for third-party codecs to be installed into FCPX or the OS. I presume this would be something like what’s there for REDCODE raw, but it may be more involved than that.
– Oliver
Oliver Peters – oliverpeters.com
-
There is already a framework for third-party decoders for AVFoundation and Final Cut Pro X. But it’s not public (yet).
-
All those “third party codecs” are owned Intellectual property, developed (often at great cost) by business entities.
Sure we all want them built into and usable by all the NLEs we might like to drive.
But that’s simply not the way things work.The codec owner makes it available (or not) depending on whether that licensing fits their strategic plan.
And that’s never going to change.
Additionally, the fact that Apple warns the industry that the internal Apple product development roadmap demands that legacy code be made fully 64-bit native (presumably to preserve operating efficiency and compatibility with their future vision) going forward is something they have the absolute right to require.
It gives you a choice.
If you prioritize backwards compatibility in existing hardware or workflows – you might want to look elsewhere.
OTOH, if you value future performance and continued innovation – and feel Apple is where you will find that – then you revise your software and hardware as needed and go with that flow.
Options are good.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
[Bill Davis] “Additionally, the fact that Apple warns the industry that the internal Apple product development roadmap demands that legacy code be made fully 64-bit native (presumably to preserve operating efficiency and compatibility with their future vision) going forward is something they have the absolute right to require.”
The 64-bit argument is only an assumption and not really something Apple specifically stated in relationship to codecs. So it’s a bit bogus. Codecs are not 32-bit or 64-bit. The software used to create the media files is 32-bit or 64-bit. Furthermore, the 64-bit argument is undermined by the fact that the supported list includes ancient codecs that predated 64-bit, such as DV, DVCPRO HD, XDCAM, and uncompressed.
– Oliver
Oliver Peters – oliverpeters.com
-
It can only be seen as bloody mindedness. I’m always keen to support open codecs and get ProRes removed as a standard delivery codec. Firstly it’s quicktime and secondly it’s proprietary. DNx is a much better family of codecs being free, open and cross platform and mxf, not in the antiquated quicktime wrapper.
If this was anything to do with legacy codecs and legacy wrappers, 32 or 64 bit then quicktime should be the one depreciated. I’m also watching with interest if Apple adopt BRAW. If not then I will actively steer editors away from X like I did in the early days. Having eventually made a fully featured NLE of X and removed much of the island mentality, this is retrograde and a return to the island. Given the move to open X to allow third parties to continue the dev, this announcement will make many third party devs wonder.
-
“Having eventually made a fully featured NLE of X and removed much of the island mentality, this is retrograde and a return to the island. Given the move to open X to allow third parties to continue the dev, this announcement will make many third party devs wonder.”
So your understanding is that the new direction that FCPX is taking won’t allow 3rd parties to provide plug-ins for older cam codecs or ….???
Seems like Apple’s MO is to let 3rd parties fill in the gaps on all their products.
The original debate on this forum was whether Apple would be able or even willing to develop FCPX into a NLE that was a usable pro app. Are we really back to step 1 with this new future update?
Maybe Apple is just giving warning to transcode all your old projects to … if you want to use FCP X and that media in the future.
It used to be that pro gear in any profession would last a life time and then some. Now everything is disposable. Constant learning curve. Constant investment.
Imacs (i7), Canon C300, Canon 5D Mark IV, Panasonic ENG HPX250P, , FCP X, teach video production in L.A., Cool Light Productions, Producing series of multimedia Portraits of creative women in the production arts.
-
[Michael Gissing] “get ProRes removed as a standard delivery codec. Firstly it’s quicktime”
Prores as a codec is independent of Quicktime, the wrapper or player software. It can also be wrapped as .mxf.
Oliver
Oliver Peters – oliverpeters.com
Reply to this Discussion! Login or Sign Up