Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro FCPXML going to Resolve with slomo clips

  • FCPXML going to Resolve with slomo clips

    Posted by Oliver Peters on September 26, 2016 at 7:12 pm

    I have 60fps slomo clips (23.98 timebase). I’ve built a “selects” timeline in FCPX and exported an FCPXML. This has been imported into Resolve. There, the durations are correct, but all clips play fast. However, when I export clips, the rendered file plays correctly in QuickTime player. So this issue is only a problem when playing the timeline in Resolve. If I simply import the camera clips directly into a clean Resolve project (FCPX and FCPXML not involved), the playback speed is correct in the Resolve timeline. So something must be wonky with the FCPXML – either in its generation or the import/translation in Resolve. Thoughts?

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

    Eric Santiago replied 9 years, 11 months ago 2 Members · 3 Replies
  • 3 Replies
  • Oliver Peters

    September 26, 2016 at 7:23 pm

    FWIW – a quick test with Premiere and its XML doesn’t exhibit the same problem. Playback speed is correct in Resolve coming from Premiere and its FCP7 XML format.

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Oliver Peters

    September 26, 2016 at 7:45 pm

    Figured out the culprit. It’s not the FCPXML at all. It’s the monitoring setting on the BMD card. These are 2K clips (2048×1080) in a 2K timeline. If you set the Resolve timeline to 2K, but leave the monitoring setting as HD 1080, then playback speed is OK. If you change the video monitoring to also be 2K, you’ll get an error message, but it also messes up playback speed of the timeline. This happens to the desktop playback, regardless of whether or not you are actually looking at the card’s output. Go figure!

    – Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Eric Santiago

    September 27, 2016 at 12:01 pm

    Not the same issue but I found a bug from FCPX to Resolve where the project would not switch to 23.976 due to accidentally starting at 24.
    I had to scrap the whole project in Resolve all together and I found it odd that I couldn’t switch on the fly like other XML flavours.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy