Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy eventually for broadcast

  • eventually for broadcast

    Posted by Andwon on August 18, 2007 at 2:31 pm

    please help unspin my head. this is a true story.

    (part 1)
    i have jumped in on a PAL project that has been shot on digiBeta and also a Sony Z1P and it’s all been digitised as DV PAL and cut in a DV PAL timeline in FCP 6. The final sequence will be output to digibeta and consists of about 20 layers, 4 of which are nested sequences. That’s kinda only the tip of the iceberger. how do I get the best results on playout to digibeta? chances of recapturing aren’t really in the cards. do i get any benefit to switch the sequence settings to 8 or10-bit uncompressed? other options available? if i did recapture, would there be nested sequence nightmares?

    (part 2)
    some of the project has been cut in 5.0 and now it’s being moved to 6.0 with the media end and start message saying they’ve changed and it seems like the audio has gone outta sync. is there a quik solution other than eyeing it back into sync?

    (part 3)
    um, and then, this digi beta playout will end up being ingested into an avid. yeah we don’t have automatic duck. is it possible just to export each audio track, one at a time, as a something pro tools could use to mix? OMF export won’t work, will it, straight outta FCP 6?

    I know a lot of some things, but not this much. a billion thanx in advanced.

    gulp,

    andwon

    mac pro quad
    kona 3
    digibeta

    Nick Price replied 18 years, 8 months ago 4 Members · 3 Replies
  • 3 Replies
  • Chris Poisson

    August 18, 2007 at 3:04 pm

    Broadcasting where, on Wayne’s World? Dude, you’re walking down a hallway with no doors.

    Part 1. Changing the compressor will help, but only your graphics etc. The footage will never be what it was before you went to DV.

    Part 2. Never, never, never change versions mid-project. The guys with the pictures at the top of the forum will spank you mercilessly for this. Best you can hope to do is try cutting and pasting your media etc. from the old to the new, or export a self contained movie.

    Part 3. Going to Avid? Why, after all the pain you’ve been put through would you do this? If that’s what’s hooked up to your digi, you should have kept the whole project in there. I’m not sure about an OMF, sorry. Get a Kona card for Pete’s sake.

  • Michael Gissing

    August 19, 2007 at 12:27 am

    Yes, nested sequences will give you grief when recaptured unless you un-nest before Media Managing.

    Audio should be exported as an OMFi. Your sound post people will not like rendered aifs. Talk to them about handles as well.

    No idea why your audio has gone out of sync. Is there an indication in the timeline that audio is out or it just looks out on your external monitor. Have you checked the audio delay settings for your external monitor?

  • Nick Price

    August 19, 2007 at 5:24 pm

    Hi,

    1. Sounds like the clips havent reconnected to their proper files on te hard drive maybe. I would check lengths and names in the FCp brower, and then the respective file in the finder. Moving from 5-6 shouldnt really affect the project. Or you could try using media manager in version 5 to make a new consolidated project, then open that up in version 6?

    2. Complete the cut then duplicate the sequence and change sequence settings to 8 or 10 bit. Any graphics titles yo have will look much better, plus if you have put colour effects etc they will look better too. Just check the fields are in the right order too, otherwise you will get a juddery effect on any moving images. Use the shift fields filter to sort this.

    3. Exporting an OMF will be absolutely fine for protools. Does what it says on the tin. Done it hundreds of times. But dont export with transitions cos it can mess up.

    cheers
    nick

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