MUBIan

Q: Why is my video shorter after import, and how can I fix it?

Hello Everyone,

 

I was redirected here form the FCP X boards, and please let me know if you know the answer.

 

I have a video (a ProRes MOV, 23.98fps) that's 1:19:16,01 long. However, when I import it into FCP, it shortens it to 1:19:10,19—apparently speeding up slightly to lose 6 seconds.

 

This is a problem because we're using FCP to burn in subtitles for a film, and the subtitle track and the video file are now falling out of sync.

 

The details...

  • This happens in FCP X, our old FCP 7, and Adobe Premiere as well
  • It effects frame rates that are not whole numbers. 23.98 fps is effected, but not 24fps. 29.97fps is effected, but not 30fps.

 

I gather this has something to do with how FCP measures the video, creating a discrepancy between duration and number of frames. Is there any way to fix it?

 

I've attached some screenshots, made using the open source short film Tears of Steel. As you can see, both the 23.98fps version and the 24fps version are the same length (12 minutes and 14 seconds). But when put into Final Cut—or Premiere Pro—the 23.98fps version loses a second.

 

Tears of Steel 23.98.jpeg

Tears of Steel 24.jpeg

And now, the different durations...

Tears of Steel FCP Import.jpeg

I've been tangling with this for days, and any advice would be much appreciated. Thank you!

Final Cut Pro 7, OS X Mavericks (10.9.4)

Posted on Nov 2, 2015 2:56 PM

Close

Q: Why is my video shorter after import, and how can I fix it?

  • All replies
  • Helpful answers

  • by Shane Ross,

    Shane Ross Shane Ross Nov 2, 2015 6:20 PM in response to MUBIan
    Level 8 (43,004 points)
    Nov 2, 2015 6:20 PM in response to MUBIan

    Where did you export this from? How do you know it's that long?  I mean...was it 1:19:16,01 long, then exported it's 1:19:10,19?  I'm just trying to get a grasp on this.  So you started with a 23.98 sequence in ______ app, exported, imported into FCP, Adobe, FCX, and it's shorter.  Right?

  • by MUBIan,

    MUBIan MUBIan Nov 2, 2015 6:25 PM in response to Shane Ross
    Level 1 (0 points)
    Nov 2, 2015 6:25 PM in response to Shane Ross

    Thanks for the reply, Shane!

     

    The film that's 1:19:16,01 long was sent to us by a distributor. We're preparing a subtitled copy. I don't know what program they used to make it, though I would add that it shows up at that length in QT7, QTX, and VLC.  And the "shortening" in Final Cut and Adobe Premiere seems to be happening for ALL 23.98fps files, including those I create myself as a test.


    For instance, in the screencaps above, I played around with Tears of Steel as an experience. The source file was 24fps. Using this source, I made a 23.98 fps version in Premiere Pro. QT recognizes that it's the same length. But when I import into FCP (or even back into Premiere) it loses a second.

  • by MUBIan,

    MUBIan MUBIan Nov 2, 2015 6:30 PM in response to MUBIan
    Level 1 (0 points)
    Nov 2, 2015 6:30 PM in response to MUBIan

    As an FYI, here's a forum thread with a user experiencing the same problem years ago...

     

    https://forums.creativecow.net/thread/8/1151482

     

    ...but the thread trails off without a solution.

     

    I originally posted this on the FCP X board, but they directed me here. They write: "This is a frame count problem. Files that are in standard 23.98 or 29.97 should use drop frame count, but most don't, so there is a discrepancy between the frame count and actual time."

     

    Let me know if you have any idea how I can fix this. The goal is simply to drag and drop the file into Final Cut and have it show up as the same length as it does in all the video players I've tried.

  • by Shane Ross,

    Shane Ross Shane Ross Nov 2, 2015 6:31 PM in response to MUBIan
    Level 8 (43,004 points)
    Nov 2, 2015 6:31 PM in response to MUBIan

    So you are relying on them to tell you that the file is a certain length?  Because I wonder if they are viewing it with 29.97 timecode timing. This is something I do when cutting 23.98 in Avid...we need to time it for 29.97 output, so even though I'm cutting 23.98, I view the time as 29.97 drop, so I can get the timing right. Because 23.98 will have a different time, due the the fact that it doesn't do drop frame time code...so it runs shorter than the properly timed 29.97. 

     

    And yes, if you take a 24fps straight up file, convert it to 23.98...that is slightly altering the speed...it will be shorter.

  • by Shane Ross,

    Shane Ross Shane Ross Nov 2, 2015 6:32 PM in response to MUBIan
    Level 8 (43,004 points)
    Nov 2, 2015 6:32 PM in response to MUBIan

    And the video players you mention don't always show accurate run times. Don't rely on them. 

     

    This is a pickle...pondering.

  • by MUBIan,

    MUBIan MUBIan Nov 2, 2015 6:38 PM in response to Shane Ross
    Level 1 (0 points)
    Nov 2, 2015 6:38 PM in response to Shane Ross

    Thanks for the ponder. : - )

     

    Worst case, when they send us a 23.98 source file, we can just convert it to a flat 24 fps, and then it will be in sync with the subtitle track we're burning in. (Although, it'll have an extra frame every ~50 seconds, which we could live with).

     

    I'm more perplexed why the length would show up as the same, regardless of the framerate, in video players but not editors. Like the two versions of Tears of Steel in the picture above were made from the same source and nothing was trimmed out...they should be exactly the same length, or close to it

  • by Shane Ross,

    Shane Ross Shane Ross Nov 2, 2015 6:51 PM in response to MUBIan
    Level 8 (43,004 points)
    Nov 2, 2015 6:51 PM in response to MUBIan

    24fps to 23.98...or vise versa...doesn't add a frame. It's a slight speed change. So, this subtitle track...it must not be 23.98...but rather be 24fps.

  • by MUBIan,

    MUBIan MUBIan Nov 2, 2015 7:07 PM in response to Shane Ross
    Level 1 (0 points)
    Nov 2, 2015 7:07 PM in response to Shane Ross

    Hmm...that might be it, but I'd be surprised. They sent us a subtitle file, and we used a subtitle editing program to toss their .srt and .890 files into FCP.

     

    We can control what timescale the subtitle track uses, and whether we send it to FCP as 24fps or 23.98fps, it's still out of sync with the video track. That is, the timing in the .srt (as opened in TextEdit) is preserved in Final Cut, and the SRT's timecode corresponds to the right timecode in QuickTime, but that's not where that line of dialogue ends up being after we put it into Final Cut.

  • by MUBIan,

    MUBIan MUBIan Nov 2, 2015 7:11 PM in response to MUBIan
    Level 1 (0 points)
    Nov 2, 2015 7:11 PM in response to MUBIan

    P.S.

    Are you certain there's no frames added? As a test, I opened the two Tears of Steel samples in Handbrake, and the 23.98fps sample and the 24fps sample are showing a different number of frames (17600 and 17617 respectively) for the same length. Is Handbrake off?

  • by belloqr,

    belloqr belloqr Oct 12, 2016 8:10 PM in response to MUBIan
    Level 1 (8 points)
    Video
    Oct 12, 2016 8:10 PM in response to MUBIan

    MUBlan, I'm sorry to resurrect a 2015 thread, but I see no way to contact you directly- did you ever resolve this issue or find a workaround? I am having the same problem now. I am not a pro, but I'll try to explain my situation. Before importing clips into the browser or inserting the clip into a sequence, I ensured my settings were correct for my video: 23.98 (23.976) etc. My video clip, which was verfied to be a certain time length by the apple finder info, VLCplayer and quicktime, is then instantly and significantly shortened when imported into the FCP browser, which destroys the sync to the already separate audio tracks. The audio tracks are imported into the FCP browser but retain their correct time lengths. I've tried transcoding the video to LT and HQ 422 prores  files in quicktime and mpegstreamclip and the shortening happens in all cases. This problem has arisen over several years in different situations per the various threads below. The only potential workaround that "Benny Krown" mentions is in the first thread below. I will contact him next to inquire exactly how his workaround works, but it appears that it requires subsequent rounds of transcoding files that already are in prores, which is obviously a sub-optimal solution.

     

    https://forums.creativecow.net/thread/8/1084387

    https://forums.creativecow.net/thread/8/1160685

    https://forums.creativecow.net/thread/8/1132569

    https://forums.creativecow.net/thread/8/1167772

    https://forums.creativecow.net/thread/8/1151482

    https://forums.creativecow.net/thread/8/1106140

    http://originaltrilogy.com/topic/Fan-Edit-Sync-Issue-Please-Help/id/16548