Forum Replies Created

  • I did what Shane suggested (I think) and just rendered each track out again, and they became the new masters. HDD’s fill up quickly when you have multiple copies of the same thing, and it starts to get confusing, but that is ultimately how I was able to cut the project.

  • Chris Trainor

    February 25, 2013 at 9:18 pm in reply to: Nesting/Merging For Multi-Camera Edit

    I asked a very similar question earlier this week, well, sorta.

    Essentially I did a multi cam shoot, and some of the other photogs started and stopped recording during the shoot.

    I posted on here to see if there was a work around to get FCP to work with multi cam editing.

    Here is the original thread:
    https://forums.creativecow.net/readpost/8/1171909

    Essentially ended up rendering out each track to a new complete mov, then bring them all back in and they’ll all be the same length and complete, with black where the cams were started and stopped. Then I could use the multi cam editor.

    Was initially using ProRes Proxy, but now I am just rendering out each track in it’s entirety using prores 422.

    My question:
    Now that I am rendering out each track, is it better to do as a self contained file, or does it matter? I totally understand about any original source material changing and you’ve got big problems when not self contained, etc. my question is more about resources.

    Since I now have 3 or 4 1080i video tracks, each about 1.5 hours long, its going to tax my machine when I go to the multicam edit.

    So I was wondering if it would be easier on my machine and its limited resources to do the stand alone self contained files, or uncheck the box and do them as ‘reference’ files. Or does it matter when it comes down to the resources needed to play it back smoothly?

    That is my main concern, getting the files to play back smoothly enough that I can utilze multicam. Hope this makes sense….

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