Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity › Forums › Apple Final Cut Pro Legacy › Clips Play Too Fast?

  • Clips Play Too Fast?

    Posted by Ben Mossman on September 1, 2009 at 5:46 pm

    Hello everyone,

    This is my first post in this forum, although I have been reading it and others for a while now on here.

    I have a problem with some clips playing too fast in FCP but the quicktimes prior to and after play at “normal” speed.

    Basically, we have some playbasts from Maya being run through Nuke to convert the .tif sequence into a QT with the “none” compression on. These are imported into FCP with the same settings and arranged and exported, however while editing the footage seems to play faster than it should. Both the clip and timeline are at 23.98fps and various codecs in the timeline have yielded the same results.

    Any thoughts?

    Ben Mossman replied 17 years ago 3 Members · 9 Replies
  • 9 Replies
  • Jeremy Garchow

    September 1, 2009 at 7:56 pm

    [Ben Mossman] “Both the clip and timeline are at 23.98fps and various codecs in the timeline have yielded the same results. “

    The clips needs to be 23.976, not 23.98.

    Jeremy

  • Ben Mossman

    September 1, 2009 at 11:15 pm

    Would the difference between the two be that noticeable though? It plays fairly fast compared to the quicktime I see after (which I use the sequence settings for).

    Ben

  • Arnie Schlissel

    September 2, 2009 at 3:39 am

    [Ben Mossman] “Basically, we have some playbasts from Maya being run through Nuke to convert the .tif sequence into a QT with the “none” compression on.”

    Don’t use “None”, use uncompressed or ProRes. None is a very old codec that’s basically obsolete. You can get the same quality with smaller file sizes using 8 bit uncompressed. 10 bit should be better (no banding, but larger file sizes).

    Arnie
    Post production is not an afterthought!
    https://www.arniepix.com/

  • Ben Mossman

    September 2, 2009 at 4:09 pm

    Unfortunately Arnie I’m not in control of the conversion itself, I’m just given the clips afterwards.
    Thanks for the tip though.

    An update on this; I’m editing another project now and it too is playing fast, which leads me to believe this is a System/User setting and not a codec or frame rate issue.

    Anyone know what might cause this?

    Thanks,
    Ben

  • Jeremy Garchow

    September 2, 2009 at 4:09 pm

    [Ben Mossman] ” It plays fairly fast compared to the quicktime I see after (which I use the sequence settings for). “

    What frame rate is your sequence? This sounds like an even integer vs a fractional integer to me (59.94 vs 60.0, etc, being forced out through a 59.94 output, or whatever the frame rate is).

    And I agree with Arnie, no reason for ‘None’ as you will have to render it out again. ProRes 4444, or ProRes HQ should suit you well.

    Jeremy

  • Jeremy Garchow

    September 2, 2009 at 4:20 pm

    Ben, you have to give more info, please. Like what’s the frame rate of your sequence, the frame rate of your footage, and the video output setting of your capture card.

    Jeremy

  • Ben Mossman

    September 2, 2009 at 4:22 pm

    My clips are 23.98 and my sequence is 23.98.

    I feel a bit silly now for not mentioning this earlier; I am also using an AJA controller for output. Turning this off seems to have solved the problem, I’m guessing it was at the wrong setting.

  • Jeremy Garchow

    September 2, 2009 at 5:06 pm

    OK, are your clips 23.98 or 23.976.

    Jeremy

  • Ben Mossman

    September 2, 2009 at 5:20 pm

    Sorry about the lack of info before,
    My timeline is at 23.98, None compression, 720×486
    My clips are at 23.98 (according to QT & FCP), none compression, 720×486
    My AJA output was set to 525i 23.98 8-bit 720×486 (turning this off put playback to it’s normal speed)
    I am outputting to a 720×486 QT at 23.976 MJPEGA 100%

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