Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Will this work?

  • Shane Ross

    June 29, 2007 at 8:36 pm

    [Editguy69] “What about the conversion to 59.94 for delivery?
    Do you drop the 23.98 sequence into a 59.94 timeline
    or do the conversion directly through the Blackmagic or AJA card?”

    Output thru a Kona 3 card. Edit on a 23.98 timeline.

    [Editguy69] “Any issues with moving graphics looking jittery?”

    Hopefully someone who has done this will reply…but if not, you can always test. I did do a test of 720p23.98 output to 720p59.94 and everything, including graphics, looked just fine. GREAT as a matter of fact.

    Shane

    Littlefrog Post
    http://www.lfhd.net

  • Chris Coote

    June 29, 2007 at 8:36 pm

    Oh I almost forgot. The offline editing would be done at another
    company’s location. The captured media would be transfered from the capture drive to their RAID. We were thinking that redigitizing the final sequence would be quicker and easier than having them consolidate their media back onto a transfer drive to send back to us since they are not too technically inclined over there.

  • Jeremy Garchow

    June 29, 2007 at 8:48 pm

    All the more reason to keep a 23.98 workflow.

    Get yourself and the other not to technical outfit a Kona3 and do the real time downconvert to 23.98 dv. Edit 23.98 dv.

    Recapture 23.98 HD, then output with pulldown to 29.97 if the Blackmagic card supports it.

    Jeremy

  • Chris Coote

    June 29, 2007 at 8:57 pm

    OK, yeah that makes a lot of sense.
    One other question (ok maybe more than 1).
    We were hoping to digitize the stuff
    without logging it first – just hitting record and letting
    FCP make the new clips at the tc breaks (free run tc).
    Can we do this accurately in FCP at 23.98?
    If the clips are renamed in the bin after capture will it pose a problem linking back to the actual quicktime media?
    thanks

  • David Roth weiss

    June 29, 2007 at 9:01 pm

    Renaming in the bin does not change the name of the original file unless, in ver. 6, you tell it to.

    “No job is worth doing more than once…”

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

  • Shane Ross

    June 29, 2007 at 9:04 pm

    If you are not using FCP 6…and you want to capture full tapes. PLEASE DO NOT HAVE THE FOOTAGE CAPTURED AND NAMED “UNTITLED!” THis causes so much pain and misery you have NO idea. Name the clip the Tape name. Like we do, 0629_1A. June 29, tape 1, Camera A. Or AJ004. Andrew Jackson, tape 4. However you label your tapes. This way the name is unique.

    Shane

    Littlefrog Post
    http://www.lfhd.net

  • Jeremy Garchow

    June 29, 2007 at 9:08 pm

    No way man. The reason why I am able to respond so much today is that I am trying to capture freee run timecode off of a two camera shoot right now. It is nothing but a headache, even with proper logging. I would suggest to log and capture the footage. Otherwise it takes 6 times as long to capture everything. Do the work in advance so it’ll save you time later.

    Jeremy

  • Chris Coote

    June 29, 2007 at 9:27 pm

    Jeremy

    What is causing it to be so slow? What deck are you using?
    RS422 control? Is this a limitation of FCP in general?
    We have been doing this for years on avids with no problems other than when there is a loss of tc for a few seconds or when the camera guys start and stop rolling within a couple of seconds and there’s not enough pre-roll.
    Having to log and capture would add a ton of time to our digitizing sessions so if there’s any way to avoid it that would be nice.
    Why the headaches if it’s logged already?

  • Jeremy Garchow

    June 29, 2007 at 9:38 pm

    Today I am using the good ole UVW1800 (BetaSP) and Rs422.

    FCP is pretty bad with timecode breaks. It takes forever to search and find them, then make a new clip.

    The headaches come from, not seeing a tc break when there are some (sometimes it’s a static shot and the tc is only out for a couple of seconds) and then there is not enough preroll on the B camera so the tc from CamA doesn’t really match up with B because sometimes B would be started a few seconds later. It sucks and is totally operator error on the shooters/producers part (and this probably won’t pertain to your workflow if you have only one camera)

    When there is a tc break, FCP just takes an eon to find it and make a new clip. If you do your work in advance and make sure that everything is logged properly (which I thought I did) it goes faster in the long run.

    Jeremy

  • Chris Coote

    June 29, 2007 at 10:19 pm

    Actually we’ll be using 3 Cams…yikes.
    Good to know what we’re getting ourselves into in advance.
    Thanks for your advice.

Page 2 of 3

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