-
Is Apple Being Misleading About Native Editing Support?
Just read this post.
https://forums.creativecow.net/thread/344/6404#6404
On Apple’s FCP X site they have a list of Native editing support for. The footnote attached to that statement says: Native editing includes support for import and playback without transcoding.
In that list they include: Sony IMX, XDCAM HD, XDCAM HD422, and XDCAM EX.
But the footnote statement isn’t true. You can’t import XDCAM EX. Not without re-wrapping the files. Granted in the column to the left they do say that import is supported with additional software from Sony. But, if you simply looked for a format under the native editing column and checked the fine print footnote, you’s miss the fact that additional software is needed. Without the additional software, you can’t edit, natively or transcoded.
Deliberate or not, it’s misleading.
-
34 Replies
-
It’s not being transcoded, it’s being rewrapped, so technically they are correct. But of course FCP7 could do this also.
“My Name is Steve and I’m an FCPX user”
-
Final Cut – all versions – support SOME codecs wrapped as MOV containers. If it’s a codec that FCP can handle, then it’s “native” as long as it’s in an MOV container. So it can’t, for instance, handle RED’s r3d container or MXF.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Agree.
Native would mean to be able to drag&drop from a card to the time-line without other intermediate process (L&T).
As an XDCAM user I expected FC to be able to deal with the MP4 or MFX avoiding the Transfer.
If Calibrated plugins can do it, why FC don’t?
rafael -
[Rafael Amador] “drag&drop from a card to the time-line without other intermediate process”
I agree.
Adobe makes this very clear one their website.
https://www.adobe.com/products/premiere/extend.html#Supportedvideoformats
To quote: Import and edit content from Sony XDCAM and XDCAM 50 cameras directly, without rewrapping or transcoding.
There’s a big difference between how PP and FCP X handles the same format.
There’s also a big difference between how Adobe and Apple explain this on their own websites. Apple requires you to not only read the fine print, but to read all the text in that section. And even then you need to understand what they mean by additional Sony software. (and you can use more than just Sony’s software to handle this)
Apple could have been as clear as Adobe, but chose not to.
-
FCPX has hooks that allows camera manufacturers to develop direct plugin support.
Sony has said they will but given Sony’s speed if development it may be long wait. Follow Sony’s move from ClipBrowser and XDCAM Transfer to the unified XDCAM Browser. It’ll be interesting to see what Canon does as well.
-
FCPX has hooks that allows camera manufacturers to develop direct plugin support.
Unless you have updated info to the contrary, according to Apple’s direct comments to me, this will still require MOV wrapped files. And at least as of last week, RED as one of those, didn’t sound too happy about FCP X.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Unless you have updated info to the contrary, according to Apple’s direct comments to me, this will still require MOV wrapped files.”
That would be a disappointment. I has heard otherwise but that was apparently early than the what you heard. I was under the impression AV Foundation no longer made that necessary. It’s certainly not doing that in any visibly or recorded way with AVCHD (BDMV folders). Other formats currently require wrap to mo but my understanding is that is changing.
-
[Oliver Peters] “according to Apple’s direct comments to me, this will still require MOV wrapped files”
Are you saying Apple told you that if Sony develops a plug-in for FCPX, users will still have to re-wrap XDCAM EX files?
Unlike PP which can browse, import and edit these same files without re-wrapping?
If that’s the case, then I’d have to say Apple is pretty much deliberately misleading on this issue.
-
It’s my understanding that AV Foundations changes things under the hood and with hardware IO. You still have to have a file format that FCP X recognizes. It seems that is QT MOV. I have no idea what Apple’s camera SDK involves, so quite possibly it could be something like what MXF4Mac does, using an alias or something like that. Then a non-QT file would be “soft-wrapped” as an MOV on-the-fly. If that’s the case, then we would both be correct.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Kevin Patrick] “If that’s the case, then I’d have to say Apple is pretty much deliberately misleading on this issue.”
Marketing speak, homie.
It does support those codecs natively, just not the containers.
FCP7 supported AVC-Intra natively, but that meant you had to rewrap it.
I hope MXF4mac can make their component work with FCPX, and the rest of the camera manufacturers too. Native container/format support is one of my major gripes with FCPX. The interface can be fixed.
Jeremy
Reply to this Discussion! Login or Sign Up