[Jeremy Garchow]

Unfortunately it seems, FCPX and Compressor can’t handle this material correctly. FCP7 had the tools, FCPX does not. Importing the footage in to Premiere shows the premiere understands what is happening and removes the correct adv pulldown frame and results in correct 23.976 playback. THere’s a checkbox in the interpret footage that says “Remove 24p Dv pulldown” that is enabled by default with this footage, so it is recognizing the flags. FCPX does not.

There was a software program that could help with this, called Calibrated Software, but I am not sure if it is relevant anymore as MXF is mostly supported natively on macOS these days, but it might be worth pinging the developer to check out any options they may have for you. Ideally, you’d run this software on the P2 footage itself, and get self-contained movs that you import to FCPX (similar to what happens when you use the import window in FCPX).

https://www.calibratedsoftware.com/ProductInfoFCPX.php

[Jeremy Garchow]

Thanks. Is there an untrimmed version?

[Jeremy Garchow]

Do you me to send you the original 24pA clip?

Yes, Phil. Please send a clip.

You can send it here. It should be a clip that’s been imported directly, and not reexported.

https://www.dropbox.com/request/TjAabjIMAk6yNhJ2HnIY

[Jeremy Garchow]

24pA is 29.97. Fcpx does not remove the pulldown when it wraps. Fcp7 does remove the pulldown on import. So what fcpx is showing you is right, it is rewrapping the op-atom MXF to 29.97 .mov

Have you tried dropping the 29.97 in a 23.98 Project yet?

Also, can you post the wetransfer link?

[Jeremy Garchow]

I don’t really know as I don’t have either, but it seems like the Sonnet boasts faster speeds. Either way, how can you go wrong? It’s going to be wicked fast storage.

[Jeremy Garchow]

Joe-

It’s 24pA footage. A format left over from when baseband 24p was much more difficult than it is today.

It’s a variation on 3:2 pulldown in that every 5th frame a pull down frame instead of every 3rd and fourth. The motion isn’t fluid, like 3:2, but it makes removing pulldown easier as there’s no frame reconstruction, just removing every fifth mushy frame.

[Jeremy Garchow]

I don’t think fcpx removes advanced pull down like fcp7 did. What you could try, though, is simply putting your video in a 23.98 timeline. Try this with a few clips and step through them frame by frame and see if fcpx removes the advanced pulldown frame.

[Jeremy Garchow]

I was able to export XML files which opened nicely in FCPX, but the media is not playing back?

What did you use to translate the XMLs?

[Jeremy Garchow]

so there’s no way to reach the user interface to initiate a restore job or to transfer the restored files across the network to our server.

Did your network change since the last time you used it? I had a similar experience and the Cache-A Bonjour name didn’t work anymore, and I had to enter in the IP address, and that worked.

Use Angry IP Scanner (https://angryip.org) to get sense of what your network looks like, and hopefully you can find the IP address from that as the “Hostname” may mention the name of the Cache-A device.

[Jeremy Garchow]

ProRes or ProRes HQ will be perfect for FCP7 and FCPX.

And for the streamed version, they may be able to take the ProRes file you create. If not, a higher bitrate h264 should be fine. It might be worth looking up any specs on OneStream’s site and see what is recommended. I quickly found that files over 5GBs aren’t accepted unless they are hosted on Dropbox or other cloud service. Cheers!