Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Beginner question on clips and sequence settings

  • Beginner question on clips and sequence settings

    Posted by Brewster71 on June 12, 2007 at 12:30 am

    I’m just putting together a music video as a home project. I have several clips from different online sources, and I would like to assemble them. I dont need the sequence to be in high definition, but would like to view it on a standard television without serious pixelation. I understand that some of my ‘found footage’ may not be of the same quality as my final output, and that’s fine. What’s the best setting to use? And what method should I use to create usable clips?

    So far I have tried a 640 x 480 DV/DVCPRO sequence, then exported the clips I had (with Current Settings) to try to make them usable/previewable in the Canvas, but they are becoming far too large and even after I’ve exported them, then reimported them, I still get the “Needs Render” message in the Canvas Window.

    I’ve got the FCP Apple Training Series book, and am working on the lessons, but I’d love some advice on how to get my project started. Thanks.

    Jeremy Garchow replied 19 years, 2 months ago 2 Members · 15 Replies
  • 15 Replies
  • Jeremy Garchow

    June 12, 2007 at 2:22 am

    720×480 is the proper size for DV NTSC.

  • Brewster71

    June 12, 2007 at 10:57 pm

    Um, ok…?

  • Jeremy Garchow

    June 12, 2007 at 11:03 pm

    If all of your clips are 720×480 DV NTSC and your sequence is set for dv NTSC, you won’t need to render anymore.

    Jeremy

  • Brewster71

    June 13, 2007 at 11:40 pm

    Okay, that’s what i thought. LOL. I’ve never had so much trouble starting a project. I have a 50GB on my hard disk and every time I render these found clips at 640 x 480 (which are the sequence settings I’ve settled on), it tells me I have run out of room. When I do succesfully render one of them at the current settings (640 x 480), I still have to render. I cannot figure out what I am doing wrong. Is there some other setting that has to be made consistent as well?

  • Jeremy Garchow

    June 14, 2007 at 2:01 am

    [brewster71] “Is there some other setting that has to be made consistent as well?”

    The timeline. BOth your clips and timeline have to be set to 720×480 29.97 fps, 48k 16 bit audio.

    Once everything is the same format, no more renders.

    FCP6 will handle multiple formats and frame rates, but they still have to be a standard video frame rate, codec and frame size. Stuff you download from the web is all over the map in terms of those parameters and FCP doesn’t really know what to do with it. FCP can play different frame sizes/frame rates pretty well if using unlimited rt, but it’s those web delivery codecs that it really chokes on.

    Also, if you plan to do a lot of editing, 50GB is not going to be enough. Get more storage, it’s pretty cheap these days.

    Jeremy

  • Brewster71

    June 14, 2007 at 11:18 pm

    Thanks for the advice Jeremy. I’m gonna tackle this stuff tonight. The one clip I exported so far does let me preview in the Timeline without the dreaded “Needs Render”, but it still has a red bar over it when I drag it to the Timeline. The preview is all I need, so I’m happy with that for now. The files I am using were all downloaded from various sources, and are .movs and .avis.

    Is it normal for an 2-hour long 600MB avi to get so large (11GB) when I export it at 640 x 480 with no audio (using Quicktime Conversion)?

  • Brewster71

    June 14, 2007 at 11:24 pm

    * Is it normal for an 2-hour long 600MB avi to get so large (11GB) when I export it at 640 x 480 with no audio (using Quicktime Conversion)?*

    I meant exporting as Quicktime movie.

  • Jeremy Garchow

    June 15, 2007 at 3:40 am

    2 hours? Sheesh, I have no idea what you are doing but it sounds like a doozy.

    2 hours of dv ntsc is about 25 Gigs.

    If you get a red render bar, something is not right in the settings you chosen for export. You should use the ‘Advanced Format Conversion’ feature in COmpressor to convert to DV NTSC, not quicktime conversion as that leaves a lot of room for error on your part (no offense, it’s just the way it’s setup, compressor’s presets are setup correctly). My hunch tells me that the frame rate or frame size was set wrong in QT conversion.

    Jeremy

  • Brewster71

    June 19, 2007 at 12:01 am

    Let me explain what I am doing, and maybe you can tell me a better way, if you have the time.

    I am trying to make a short music video, comprised of different clips from different sources. Most of these sources are 1-2 hour TV shows. I am trying to do a rough cut, but whenever I assemble the pieces, it gives me the red bar, and tells me that I need to render. All I want to do is see a rough visual of how each clip progresses to the next, but I cannot do that, apparently, without a) rendering every time I add a clip or b) rendering the source file.

    I spent the weekend rendering my 3 hour-long source files, then imported them back into FInal Cut, and I STILL get the render bar, although, granted, I can at least now scroll through the source files without the jerkiness. I cannot, however, cut them into clips (with it In/Out points) and add them to the Timeline without getting the red render bar. I am not sure why this is such a production (other than me being inexperienced with this app). I’ve created many videos in Premiere this way. I don’t mean to sound cranky, I just feel like there is something obvious I am missing. Surely I can import a few hours of footage, and experiment with the placement of clips from that footage without rendering constantly?

  • Brewster71

    June 19, 2007 at 12:02 am

    Also, the only reason I chose NTSC DV Is because I was told to by somebody on here. All I want to do is create a four minute video that looks decent on a standard television. Again, I am open to suggestions. I am *almost* ready to give up.

Page 1 of 2

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