Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro I have a question about converting 23.976 fps into 24.

  • I have a question about converting 23.976 fps into 24.

    Posted by Ryan Elder on August 19, 2019 at 2:30 am

    I am making a DCP of a short film of mine for festivals. I was told to convert it to 24 fps for the DCP. I did some reading on how to do that, and I was told that I would need to convert the audio from 48 khz to 48.048 khz to match the 24 pull up.

    But in Premiere Pro, I don’t have a 48.048 khz option to export with. Does anyone know what to do then?

    Ryan Elder replied 6 years, 8 months ago 4 Members · 16 Replies
  • 16 Replies
  • David Baud

    August 19, 2019 at 3:57 am

    They are 2-main flavors for making a DCP:
    . Interop
    . SMPTE

    . Interop only accepts 24p master
    . SMPTE accepts both frame rates, 23.976fps & 24fps

    Interop will be more compatible with older digital projector/server system, whereas SMPTE is the newer DCI standard for DCP.

    If you still decide to go with DCP Interop, because the speed difference between 23.976 and 24fps is not that great, I would first run a test: create a new 24fps timeline and drop in it your 23.976fps film. Watch it and listen to it and see if the sound quality is acceptable to you.
    If not then I would use an audio software to speed up the sound of your film to match 24fps to compensate for the pitch changes.

    David Baud
    Colorist & Finishing Editor
    KOSMOS PRODUCTIONS
    Denver – Paris
    http://www.kosmos-productions.com

  • Ryan Elder

    August 19, 2019 at 4:11 am

    Okay thanks, but if I drop the 23.976 movie into a new 24 fps timeline, there are black spaces in between some of the clips because of the new timing, it causes black spaces in the video. If that makes sense? So the sound seems fine but the video is not then.

  • Chris Wright

    August 19, 2019 at 4:44 am

    you have to render it out so its all one video so it all changes at the same time.

  • Ryan Elder

    August 19, 2019 at 1:12 pm

    Okay thanks, but if I do that, are you saying to set the export setting at 24 fps instead of 23.976? Cause if I do that, won’t the speed of the audio still be the same though, and not change with the fps?

  • Chris Wright

    August 19, 2019 at 4:48 pm

    export the 23.976 out in a 23.976 timeline, then re-import in and interpret footage as 24 into a 24 timeline. this will change both the duration and audio without making spaces.

  • Ryan Elder

    August 19, 2019 at 11:49 pm

    Okay thanks, but I already tried this, and there are black spots in the video. What I mean is that every second there is 0.024 of time left over after every second in a 24 timeline with 23.976 footage imported into it.

    So when every second hits that 0.024 of empty space, it creates black spaces in the video. What do you do then, or at least that is what is happening, when I import 23.976 footage onto a 24 fps timeline.

  • Chris Wright

    August 20, 2019 at 12:53 am

    you render out the whole thing as 23.976. not individual clips. you don’t import 23.976 footage onto a 24 fps timeline, you interpret framerate to 24, then place that 24fps into a 24fps sequence. there are no gaps because you have a whole movie with no cuts.

  • Ryan Elder

    August 20, 2019 at 1:22 am

    Oh okay, my mistake. I can render it out in DNxHD then, but would there be a quality loss though, if I rendered it out in that format, then reimport it, then render it out again?

  • Chris Wright

    August 20, 2019 at 1:37 am

    if its 8 bit or 10bit depends. You can go super quality visually lossless DNxHR 444, DNxHR HQX or completely lossless with 8 bit full uncompressed png quicktime or 16 bit EXR full math lossless.

  • Ryan Elder

    August 20, 2019 at 2:45 am

    Okay thanks. It says 24 bit on the export settings, unless I’m reading the wrong setting?

Page 1 of 2

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