Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP 5.0.2 Multicam Issues

  • FCP 5.0.2 Multicam Issues

    Posted by Thom Whitehead on August 3, 2005 at 6:33 pm

    I’m trying to edit a 4 camera interview in multicam. Time of day timecode is slaved to each source.

    During the course of the show, certain cameras shut down and restart at different times. For instance, in the same timespan, there might be 3 clips associated with cam 1 and only one clip for cam 2.

    The clip naming convention is as follows: CAM1-1-A (for cam 1, start 1, angle A) CAM1-2-A (for cam 1, start 2, angle A) CAM4-3-D (for cam 4, start 3, angle D). I have a unique angle id indicated in the browser “angle” column corresponding to each camera (A B C D). The angle information was logged before capture.

    Problem is that FCP sees EACH clip as a separate angle, and I end up with a multiclip containing 28 angles…not very satisfactory. I’ve tried different naming conventions, as well as multiclip and multipclip sequence…no difference.

    I know a workaround would be to put all the clips for each camera in a sequence and export, then import and group the four cameras…what a pain (also the interview is over two hours long and I have 4 cameras!!!).

    Anyone wanna tackle this one?

    We all owe our jobs to Philo T. Farnsworth .

    Dan Riley replied 20 years, 9 months ago 5 Members · 5 Replies
  • 5 Replies
  • Ben Insler

    August 3, 2005 at 6:58 pm

    Hey Thom,

    I’m not sure if this will work, and I’m actually using FCP 4.5 HD right now so I can’t test it, but could you nest each camera clip (or series of clips) in its own sequence and then make a multiclip out of the sequences instead of the master clips themselves. I don’t know what issues you’ll run into later if this works now, but you might be able to tackle the problem that way. Just brainstorming – hope this helps.

    Ben Insler
    Editor
    Telemark Films

  • Mark Raudonis

    August 4, 2005 at 3:44 am

    Yep. This is a problem. Your workaround seems like it would work. Consider trying this: Sort through your browser and reassign the angles for the “successive” clips.

    My only other suggestion for your next project is to slave code for all four cameras and NOT use T.O.D. code.

    We’re struggling with your same problem.

    Mark

  • Tom Wolsky

    August 4, 2005 at 7:01 am

    Multiclip sequence is supposed to be just for this purpose. It should allow you to break material into separate groups based on how far apart they are from a specified TC. You should be able to get not a multiclip with 28 shots, but a few multiclips with groups of shots. I’ve never tested it as I’ve never had access to that type of material, but that’s the theory of how it’s supposed to work, for exactly what you describe.

  • Mark Raudonis

    August 4, 2005 at 2:45 pm

    [Tom Wolsky] “I’ve never tested it as I’ve never had access to that type of material, “

    Our experience is that the successive clips generated by the discontinous code do NOT all show up automatically as angle #1. Rather, they populate the multiclip grid sequentially (angle 1, angle 2, angle 3). In other words, you’d expect all the clips from a tape labeled “Camera one” to stay in the “camera One” box of the grid. Currently, Multicam is not doing that. Each successive clip takes on the next angle. Hopefully this will be addressed in a future release.

    mark

  • Dan Riley

    August 6, 2005 at 5:26 am

    When you log your clips, are you entering the camera,
    or angle number in the angle number box, or are you
    trying to get FCP to assign the cameras based on
    your clip label? If all your clips are assigned
    angle 1, they will stay in the angle one box,
    in my experience. Are you saying even when
    you tell FCP during logging that a certain reel
    from camera 1 is angle 1, it doesn’t end up there?

    Dan

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