Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Apple Final Cut Pro X Clips shot at 120fps showing as 23.98

  • Clips shot at 120fps showing as 23.98

     Jeff Krieger updated 1 month ago 5 Members · 6 Posts
  • Jeff Krieger

    February 16, 2023 at 4:52 pm

    I have clips shot on a Sony FX6 that I’ve brought into Final Cut. They were shot at 120fps. But Final Cut is showing them as 23.98. Was trying to quickly identify all my slomo clips, but this is making hard. Any advice? TIA.

  • Eric Santiago

    February 16, 2023 at 5:13 pm

    How are you seeing this 23.98 fps?

    Visually on the info tab or are you saying it’s playing back at 23.98 fps?

    All clips have a frame rate base on the camera settings.

    Up to you to place it in the timeline at whatever framerate for output.

    If you are saying you did all that but the clip plays back in real time then I’m not sure.

  • Jeremy Garchow

    February 16, 2023 at 8:47 pm

    That’s how the slow motion works. You film 120 frames per second, and play it back at 23.98fps. This then, is slow motion. If the clips came in at 120fps, then they would play back in “real time”. So you will need to manually identify which clips are slow motion and tag them using a keyword collection or mark them.

  • Ben Balser

    February 17, 2023 at 12:01 am

    Where exactly are you seeing the FPS data?

    If you drop them into a timeline, FCP automatically adjusts the FPS to playback at normal speed. You need to change the Rate Conform for it to play back as show in slow motion.

  • Joe Marler

    February 19, 2023 at 3:16 pm

    There are two ways cameras shoot slow motion: (1) Sensor and encoding frame rates are increased, with intention of retiming in the NLE, and (2) Sensor scan rate is increased but material is encoded at a lower frame rate and bit rate. IOW the slow motion is “baked in”. That is how the FX6 handles 120 fps material.

    The FX6 can only do that frame rate in S+Q mode. I believe the reason for that restriction is the XAVC-I codec and MXF container format do not support the required encoding bit rate to shoot and record true 120 fps. In return the MXF container has much richer metadata than the MP4 container and better supports timecode.

    The metadata which indicates the FX6 sensor frame rate is unfortunately esoteric, but it can be seen using Sony Catalyst Browse or the 3rd-party tools MediaInfo or Invisor. In Catalyst Browse, the metadata field is denoted “Capture frame rate”, as opposed to regular “frame rate”. In the other tools the metadata field is called “CaptureFrameRate_FirstFrame”.


    I tried using the command-line utilities ExifTool, ffmpeg and ffprobe but they do not reveal that metadata. If they did you could batch process a bunch of camera clips and rename them to indicate the 120 fps stuff. Then you could use Finder tags or an FCP filter to keyword those.

    I also investigated what video metadata is indexed by MacOS Spotlight search and what metadata fields Finder can search. Unfortunately they don’t handle sensor scan rate in XAVC-I/MXF.

    However Invisor can display metadata from about 10 clips at the same time in a spreadsheet-like grid, so you can find them like that.

    MediaInfo is a GUI tool but has an available command-line interface, but it’s limited and I don’t think it handles sensor scan rate.

    FX6 in S+Q mode at 120 fps does not record audio, so maybe you could find them like that (maybe even in FCP). In hindsight that might be the simplest method but I didn’t think about it until just now.

    Of course that doesn’t consider all the camera operators who shoot normal frame rate and forget to turn on their camera mics 🙂

  • Jeff Krieger

    February 19, 2023 at 6:04 pm

    First of all, thx so much for the detailed response and all the time it seems it took you to research this.

    I actually tried a lot of those (except third party apps)…I will try Catalyst Browse again. It kept crashing on me.

Viewing 1 - 6 of 6 posts

Log in to reply.

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