-
FCPX 10.4.9 is out!
-
Sheesh. Thanks for posting. Unfortunately, I find that to be a TOTALLY UNACCEPTABLE answer. It worked in the previous version and that was already with any 32-bit codecs deprecated. It works in Resolve, Premiere, and Media Composer, as well as other apps like Switch – all on the same OS. Had it never worked, then I would have a bit of sympathy. But this update broke it, pure and simple.
– Oliver
Oliver Peters – oliverpeters.com
-
I would add that it’s probably not the camera at all, so that’s a bit of a misleading answer the tech provided. The camera uses an AVC-Intra VBR codec. I have a Sony F55 camera clip, which also doesn’t work in FCPX. It, too, uses this codec. Most likely Apple dropped support for this codec. Not sure why, but I would imagine all cameras that use this codec wrapped as MXF are affected.
– Oliver
Oliver Peters – oliverpeters.com
-
[Warren Eig] “”our OS and software is open source””
BTW – That’s a totally incorrect statement on the tech’s part. Their OS and software most definitely is not open source.
– Oliver
Oliver Peters – oliverpeters.com
-
Oliver,
Don’t shoot the messenger. I’m not the tech support guy. I just came across this answer in another forum.
Warren Eig
O (424) 293-1164email: info@babyboompictures.com
website: http://www.BabyBoomPictures.com
Vimeo: https://vimeo.com/babyboompicturesFor Camera Accessories – Monitors and Batteries
website: http://www.EigRig.com -
Sorry, I thought I was clear that I appreciated your posting that here. And I did say the tech person’s comment. It just shows up as a quote to you in the way the forum formats quotes. Hence the double quote marks. Sorry if I wasn’t clear enough. Please keep the info coming.
In general this release has some cool stuff, but it doesn’t appear that there was adequate QA.
– Oliver
Oliver Peters – oliverpeters.com
-
Resolve has issued a new point update (16.2.6) so that the new fcpxml1.9 is supported. One less thing to worry about. BM sure are quick off the mark.
I must say I’m a bit puzzled by the idea that Sony is to blame for Apple dropping or not at least bug checking codec support. It’s got to be a bug. Just like the weird curves behaviour that people tried to pretend was a feature until Apple fixed it
-
[Oliver Peters] “The camera uses an AVC-Intra VBR codec. “
What codec is that?
-
[Warren Eig] “My recommendation would be to transcode the footage into a .mov using the SONY
software until SONY can possible come out with a plugin (similar to what RED did) that enables the FCP workflow with this unsupported camera. I totally get the frustration on this one. I’m so so sorry this is happening.”
“There’s a lot of weird info here. Sony cameras are importable to fcpx, where the mxf files are transcoded or rewrapped.
There IS a plug-in (that is native to fcpx) that allows this.
I don’t know. This really seems like a bug, not a feature.
-
[Oliver Peters] “I would add that it’s probably not the camera at all, so that’s a bit of a misleading answer the tech provided.”
Using Media Info, FX9 and F55 MXF files are nearly identical, including codec.
F55 imports, FX9 does not.
I import the FX9 clip to Catalyst Browse, and exported ‘Same as source’ and made a new MXF, and that file will successfully import to FCPX.
*shrug*
Don’t really know what to make of it.
-
Here is another part of that same post that seems very relevant………..
“If you open the card in Sony’s Catalyst Browse software and then export the clips as MXF’s – which is basically a passthrough and all this is effectively doing is rebuilding the Metadata – the material loads into FCP X perfectly.”
If this works like he says it’s easy to still get your work done while they figure it out.
It’s funny, this is the only way I deal with my SONY footage in X anyway. I never import directly from the camera. I always use Catalyst to organize my footage in the finder, then from labeled organized folders I drag that into X and let it tag everything.
Reply to this Discussion! Login or Sign Up