Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Found the answer to timecode on quicktime player from FCP

  • Found the answer to timecode on quicktime player from FCP

    Posted by Dan Riley on May 2, 2007 at 11:39 pm

    Actually Matt, from the AJA forum pointed it out to me.
    Here’s what you do: either a clip in the viewer or a sequence,
    you export a quicktime ref movie first, then drop that into compressor
    to make the h.264. Don’t do a quicktime conversion in FCP and do the
    h.264 that way. I tried it from an original DV captured clip also, just
    dropping it in compressor to make the h.264 and it works too.
    Very cool. Thanks Matt for helping me.

    Dan

    John Pale replied 19 years ago 3 Members · 11 Replies
  • 11 Replies
  • David Roth weiss

    May 3, 2007 at 12:38 am

    Odd, but it does not seem to work with 8-bit uncompressed. The captured file does show timecode in the QT player window, but when I export an H264 of that from Compressor it has no timecode.

    David Roth Weiss
    Director/Editor/Post-production Supervisor
    David Weiss Productions, Inc.
    Los Angeles

  • David Roth weiss

    May 3, 2007 at 1:25 am

    Analog video doesn’t work, looks like all digital formats do…

  • Dan Riley

    May 3, 2007 at 1:35 am

    What do you mean, “analog video doesn’t work” ?

    Dan

  • David Roth weiss

    May 3, 2007 at 1:42 am

    See my first post above. I meant captures from analog format such as BetaSP captured as 8-bit uncompressed. It clearly has timecode that shows in QT player, but it doesn’t tranfer oevr to an H264 conversion in Compressor.

  • Dan Riley

    May 3, 2007 at 1:50 am

    Interesting.
    I’ll try it tomorrow at the office.
    But my stuff is 10 bit, and was from DigiBeta but from BetaSP masters.
    What card are you using and what codec to do the 8 bit captures?
    I use Aurora Pipe Studio and Aurora 10 bit uncompressed codec.
    We’re still an SD house, until this summer.

    Dan

  • David Roth weiss

    May 3, 2007 at 1:58 am

    Using a Kona LH to capture Beta to Kona 8-bit uncompressed, whgich is the very same thing as Apple 8-bit uncompressed.

    I’m guessing any digital format captured via firewire or SDI will allow the timecode to transfer over, but nothing captured via analog component.

    It just a guess, but it seems to be so…

    DRW

  • Dan Riley

    May 3, 2007 at 2:39 am

    Well that is a different problem. You are saying your 8 bit clips from BetaSp
    don’t have the original timecode from the tape on the captured 8bit
    quicktime clips? Don’t you have rs422 connected from the BetaSP to your KONA card?

    Dan

  • David Roth weiss

    May 3, 2007 at 3:40 am

    Nope, you misread my post. I said the captured 8-bit does have timecode, it shows up in QT player, but that timecode does not show up after making an h264 conversion in Compressor.

  • John Pale

    May 3, 2007 at 12:37 pm

    Import the H264 clip into FCP…load it into the viewer, then use the Modify Timecode command to add the correct timecode to it.

    Easy.

  • Dan Riley

    May 3, 2007 at 3:02 pm

    This is not the workflow I’m trying for.
    The idea is, instead of making DVDs with burned in timecode from
    DigiBeta or BetaSP playback, we can take a firewire drive of backup files
    and have someone drop those files into compressor to make h.264
    files then upload to our site for online viewing. Even a computer without FCP.
    With the discovery yesterday of how to do it, this important addition
    to the quicktime player eliminates a real-time expensive step in the
    process. Having to go through your process on hundreds of files,
    in my opinion would increase the chance for errors as well as tying up
    a workstation. For the one-off sequence now and then, yes I can see
    doing your process so thanks for showing us to do that. I’m sure it will
    come in handy.

    Dan

Page 1 of 2

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