Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy 5 hours of footage – all needs rendering!!!

  • 5 hours of footage – all needs rendering!!!

    Posted by Joseph Wilkins on December 3, 2008 at 8:52 pm

    So I was given some footage… 5 hours of it that was previoulsy captured in iMovie of all places, so it is .DV format.

    I imported it into FCP and can play it just fine, but the audio is not playing…. it tells me I need to render it, which for 5 hours worth is a nightmare situation.

    I looked at the setting for the DV footage and it said it was 32.000 khz stereo, so I went back to my final cut sequence and tried adjusting the clip settings to match, but still i get the dreaded red line of render!

    Please help if you can 🙂

    Shane Ross replied 17 years, 9 months ago 2 Members · 5 Replies
  • 5 Replies
  • Shane Ross

    December 3, 2008 at 9:15 pm

    #20 Using iMovie to Capture for FCP edit

    Shane’s Stock Answer #20: Using iMovie to Capture for use in FCP.

    iMovie handles the media differently from FCP, specifically where audio is concerned. So it is not a recommended workflow. Here’s why…

    iMovie captures using DV Stream (.dv) standard which does not use timecode. That is a big disadvantage over the way that FCP captures in that you can’t go back and recapture the material at a later date if you need to revisit a project.

    The DV/NTSC specification (the one FCP uses) also calls for seperate tracks for audio and video, even if you capture it as one clip. iMovie’ DV stream format is muxed audio and video, which means that they are tied together (I can’t get into specifics because I ain’t no engineer or programmer). FCP is a bit more demanding and captures the seperate audio/video tracks, either in a single media file or as seperate video and audio files. With FCP you could capture video only or audio only because each is defined by the DV specs. while with iMovie you can’t.

    Also, if you drop the iMovie footage into the timeline, your will get the RED render bar forcing you to render the footage in order to see it. As you know…

    You can use either QT Pro or Compressor to convert the .dv footage into DV/NTSC in order for FCP to work with it without needing to render.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • Joseph Wilkins

    December 3, 2008 at 9:22 pm

    OK.. so in short, I have to put up with the render… since I dont think I want to recompress

    One follow up, and thanks for your reply… once I rendered this and it took an hour and a half… then I saved and closed and the next time I reopened the red line was back…

    What gives? How can I make sure that does not happen?

  • Shane Ross

    December 3, 2008 at 9:31 pm

    Rendering is recompressing the footage as well. Best to do it so that you don’t have to render. Because every cut you make, anytime you move the footage…anything, you have to render again.

    Recompress the footage. Save yourself a headache. Or edit in iMovie.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

  • Joseph Wilkins

    December 3, 2008 at 9:46 pm

    You are right, In a normal world would render it all out, but because of the nature of this project.. (there is no editing to do), all I need to do is show it to the client, then export to DVD… for that reason (and because I just spent an hour and a half rendering the audio.. I just need to make sure I can save it and that when the client comes tomorrow to watch it, the audio render will be in tact… I will not be moving or changing anything in the timeline.

  • Shane Ross

    December 3, 2008 at 9:59 pm

    Then why bother with FCP? Use iMovie and send it to iDVD.

    Shane

    GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
    Read my blog, Little Frog in High Def

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