F55: 4K XAVC support added to FCPX

Hi,
switched my Mac Pro with a fully blown imac last summer...
attached a thunderbolt raid WD 4TB and been workin on it ever since...
best thing, when i have to work at home i just take the raid with me and off i go...
the imac is atruly truly amazing machine.
has me wondering why i should ever upgrade to a macpro again.
we'll see when the new ones arrive, but i think that the sales figures won't be that high...;-)
any chance of posting some xavc clips online? now that we can finally play with them in FCPX???
highly appreciated!

cheers
I'm glad your Imac is doing it's work. I edit these days on a MBPretina and the new Imac and they blow my mind. BUT...Imagine that same sense of power when they upgrade the Mac Pro! It's coming. It has too so that Apple can redeem themselves to pros that think iMacs and FCPX are toys. But it will be very expensive because they won't make very many of them like they do Imacs and iPads. Rumor is the Pro lines will be built here in the states as well. But it's really good to hear that the Sony 4k is running excellent on the Imac in FCPX.
Can't wait to see some of the work you guys will be doing with that fine ass camera the F55!
 
to pros that think iMacs and FCPX are toys.

I can tell you it was very difficult to spend $2700 on an iMac. I had been thinking about it for weeks. So far though, no regrets. Real time in Resolve, haven't found the node limit yet.

Rumor is the Pro lines will be built here in the states as well. But it's really good to hear that the Sony 4k is running excellent on the Imac in FCPX.

I did notice that, took me aback. Assembled in USA. Melrose Mac in Los Angeles stocks the higher end build-to-order iMacs, that's what had kept me from jumping before, waiting for a BTO and not being able to return if it wasn't what I thought it would be.

I spent more time with 4K XAVC in FCPX last night. Truly amazing. But it also really brought home the realization that the need to do it will be infrequent for quite a while.
 
Nate,
Have you tried round tripping a xavc timeline via xml from FCPX to Resolve yet? Im having a hell of a time getting Resolve to automatically recognize the source files and when I try to do it manually it wont work either. As a test I put one ProRes clip in to my FCPX xavc timeline and Resolve found that one clip no problem. I took a guess that Resolve couldnt find them due to the clips being labeled with dates. Final Cut by default is labeling my xavc clips with their date stamp upon import instead of the original clip name. So I selected the clips in my Event Library and went Modify/Apply Custom Name/Original name from camera. This correctly labeled all of the clips in my Event Library and timeline, then I exported the XML. Resolve however is still looking for clips with the date stamp and wont connect.

Im assuming this is all user error as FCPX is rather new to me but when I manually guide Resolve to the xavc source files in their XDROOT folder where I know they are, Resolve shows the Clip sub-folder as empty. Also went to the Event folder that holds Original material and Proxies. I've even tried having Resolve scan the whole drive for the fun of it. No dice

*One note: Im not having Final Cut copy/duplicate import files in to the Event Library or transcode them in to proxies. Im having it directly reference the original XAVC files in their folder on ext. drive.
 
Last edited:
Nate,
Have you tried round tripping a xavc timeline via xml from FCPX to Resolve yet? Im having a hell of a time getting Resolve to automatically recognize the source files and when I try to do it manually it wont work either.

Resolve won't see the re-wrapped XAVC .mov files that FCPX creates and uses. Not yet.

For now, just keep the camera original files handy somewhere. After bringing in the FCPX XML, go into the Media room, and replace all the media in the pool (which will be .mov files from inside the FCP Events folder) with all the media from the cards that you know are used in the timeline. If you do not have the camera original files, you're probably out of luck for moment.

Resolve will then use timecode to fill up all the shots.

The Resolve team surely knows about this and if history is any indication, they will have this fixed in days, not weeks. Those guys are so on top of it it's unbelievable.


*One note: Im not having Final Cut copy/duplicate import files in to the Event Library or transcode them in to proxies. Im having it directly reference the original XAVC files in their folder on ext. drive.

Unpossible. When you import the files, you'll notice the option to NOT copy files into Event is greyed out. It's because FCP wants to re-wrap the files into Quicktimes. Or did you figure out a way?
 
Last edited:
Nate, your awesome! That worked perfectly and glad to see it wasnt totally user error. Your also right FCPX import doesnt allow you to deselect copy files. I think I had deselected it in FC global import prefs but when the actually import window comes up its greyed when trying to import xavc files.

"The Resolve team surely knows about this and if history is any indication, they will have this fixed in days, not weeks. Those guys are so on top of it it's unbelievable."

Until they do, since your forced to make copies anyways, one could have FC just make ProRes proxies, at least those automatically link via XML in Resolve.

Thanks again man!
 
Why does FCP insist on renaming clips by adding time-stamp, this breaks the ease of easily relinking clips by names in a variety of situations where it would be needed?

This isn't something BlackMagic needs to fix, its something Apple needs to stop doing in FCP.


Bill - you could edit the filenames back to what they were in the XML file if you don't have a gaziilion XAVC files from your exported edit.
 
Why does FCP insist on renaming clips by adding time-stamp, this breaks the ease of easily relinking clips by names in a variety of situations where it would be needed?

This isn't something BlackMagic needs to fix, its something Apple needs to stop doing in FCP.


Bill - you could edit the filenames back to what they were in the XML file if you don't have a gaziilion XAVC files from your exported edit.
Learn to have the names displayed as original. It's very easy.
 
I'm just trying to understand Bill's problem, if you can leave the names displayed as original - what is the problem?

The problem has nothing to do with filenames as he originally suspected. It's moot.

Resolve can't read the .mov XAVC files FCPX makes. It can only read the .MXFs.

On top of that, FCPX XML doesn't reference media used in the timeline by filename. It references by File ID number, a system level identifier.
 
Last edited:
This might be of interest to Mac users who need to deal with XAVC footage. Copied more or less from the update notice that just popped up on my computer:

A new update from Apple for ProApps Quick Time codecs 1.0.2 adds codecs for use by Quicktime based applications:
-Apple Intermediate Codec, Pro Res, AVC-Intra, DVCPRO HD, HDV, XDCAM HD/EX/HD4:2:2, MPEG IMX, Uncompressed 4:2:2, XAVC
Recommended for all users of Final Cut Pro X, Motion 5, or Compressor 4

Most of that doesn't sound new, but the XAVC does.
 
This might be of interest to Mac users who need to deal with XAVC footage. Copied more or less from the update notice that just popped up on my computer:

A new update from Apple for ProApps Quick Time codecs 1.0.2 adds codecs for use by Quicktime based applications:
-Apple Intermediate Codec, Pro Res, AVC-Intra, DVCPRO HD, HDV, XDCAM HD/EX/HD4:2:2, MPEG IMX, Uncompressed 4:2:2, XAVC
Recommended for all users of Final Cut Pro X, Motion 5, or Compressor 4

Most of that doesn't sound new, but the XAVC does.


It will only help users who have access to XAVC material already re-wrapped by FCPX into .mov files.

Out of the camera, the files are wrapped in .mxf, and this update will not allow Quicktime to open them straight out of the camera, unfortunately.

What would REALLY be cool, is an update to Quicktime and AV Foundation to read both flavors of MXF containers!
 
The problem has nothing to do with filenames as he originally suspected. It's moot.

Resolve can't read the .mov XAVC files FCPX makes. It can only read the .MXFs.

On top of that, FCPX XML doesn't reference media used in the timeline by filename. It references by File ID number, a system level identifier.

..and unfortunately still cant after the 9.1.3 Resolve update. Unless I did something wrong that is. Bummer..
 
When it can't find the files, you need to point it at the "original Media" folder in your FCPX event, then it works
 
No dice for me, Resolve will not recognize the XAVC (id).mov's in the Event/Original Media folder for me. I even tried it from Media section, manually navigating to the folder. The only way it will work is the way you showed me before the update Nate.
 
Back
Top