Forum Replies Created

Page 10 of 22
  • Got it. I answered my own question. I had a couple layers with FX that needed to be rastorized. Now I understand the mystery of the fickle layed photoshop file in Final Cut! “Fickle layered photoshop file in Final Cut” — say that ten times fast.

  • Nevermind. It was so stupid I’m afraid to even say what I did.

    “THE LOST SKELETON OF CADAVRA”

    And more…

  • Bill Russell

    February 1, 2008 at 12:25 am in reply to: Deinterlacing issue or bug in 6.0.2?

    Hi, thank you for responding! I double-checked just now. The following all have the same settings, which are NTSC DV, 720×480, 29.97, lower field:

    – The clip in the sequence
    – The sequence
    – The clip which had been exported from the sequence

    These are all correct it seems. Any output of any of the above, from 6.0.2 (on two Macs) results in a single-field playout to tape (I figured out this morning that it was single field only, hence the 30P — my tired eyes last night saw it as a full resolution deinterlaced frame! Now it makes sense. But notwithstanding….) 5.1.4 has no trouble playing any of the above sources, either from sequence, or from the exported clip from the bin.

    ?

    “THE LOST SKELETON OF CADAVRA”

    And more…

  • Well, now that it is not 4am I’m thinking a little clearer. Looking at the tape output today, it is clearly a problem of simply single field play to tape in 6.0.2. No matter what I do, it plays to tape as one field per frame. 30i DV file, two Macs.

    So…

    Help!!! 🙁

    Thank you!! 🙂

    “THE LOST SKELETON OF CADAVRA”

    And more…

  • Your guess would be right. Thanks hugely.

  • David, thanks. That fixed it.

    Interesting notes: One clip, though clip settings saw it as 23.98, CT (Cinema Tools) saw it as 24. However, on another problem clip, CT saw it as 23.98 already, but I conformed it to itself anyway, 23.98, and that fixed it. Weird. Thanks for the answer.

    “THE LOST SKELETON OF CADAVRA”

    And more…

  • Thank you David! Do you happen to have the link of that previous post? (I’m not finding it.) Thank you.

  • Bill Russell

    January 10, 2008 at 12:31 am in reply to: (782×480)? Problem

    Okay, do this.

    1. Right-click on the clip and choose “Reveal In Finder”

    2. Open the media clip WITH QUICKTIME PRO (not with Final Cut)

    3. In Quicktime, under the Window menu choose “Movie Inspector” (or hit Apple-I)

    In the movie inspector, my hunch is that the correct size of 720×480 is listed to the right of “Format”. BUT to the right of “Normal” and “Current” size you’ll see your strange size of 782×480.

    Is that right? I don’t know why this happens sometimes. But if this is right, then continue with the following steps:

    4. Under the Window menu choose “Movie Properties” this time. (Or hit Apple-J.)”

    5. At the top select “Video Track” (Don’t unenable it, just select it).

    6. At the bottom you will see scaled size set to 783×480. Right? Okay, UNCHECK “Preserve Aspect”. Now enter 720×480 in that box. You’ll notice that “Display size” changes to 720×480 too. Okay?

    7. Under the file menu choose “SAVE” (or Apple-S)! Now close Quicktime and return to Final Cut Pro.

    8. You will have to import the clip anew (just reconnecting won’t work), and re-cut it into your sequence. But Final Cut will now recognize the clip with the correct size of 720×480.

    As Quicktime gets more “advanced” it gets weirder. Oh well. Enjoy. – B

    P.S. You’ll need to be using a fairly recent version of Quicktime Pro

    “THE LOST SKELETON OF CADAVRA”

    And more…

  • Nope, just checked, thank you, the Quicktime clips ARE 23.98. When you step through them in the viewer, or otherwise on the UNRENDERED timeline, or even in Quicktime, there are no repeat frames. The repeat frames only appear when these clips are RENDERED on the timeline.

  • There are two people in this thread having the exact same immediate problem, myself and one other person who piped up: FCP5 to FCP6 corrupts, no media management in the equation. That’s issue #1. That person writes that s/he is also familiar, no surprise, with FCP’s longstanding problems with MM — MM causing exactly the same kinds of problems as moving a project from FCP5 to FCP6. It’s clearly all related to one longstanding media linking bug in FCP, I think we are saying. That’s issue #2. That linking bug rears its ugly head in XML export/import too, and OMFs too — you know, speed changes, transitions, motion tab attributes, general keyframing, the way that stuff gets messed up in these processes. So if there is a shared solution to a shared problem (1 and 2), yes yes, we are interested!

    That brought us to the article on the Ken Stone site — yes I have seen the MM article years ago, and so thanks to you I took a look at it again. I decided I would try one of it’s tricks to try to solve problem 1. — namely, to make sequence clips indpendent first, before then saving this FCP5 project and then trying to open it in FCP6. I did try that, and it did not make any difference, so that was that for the MM article in question and for its relevance to problem number 1.

    However — I tried an XML import, again thank you for suggesting that, and you are brilliant, ’cause yes! it did make a difference… with the speed change errors. To be sure it produced other undesirable results, mainly resetting the scale attributes on graphics keyframed in the motion tab. BUT! this is real progress and could really help me, I truly am grateful to you — I think I can use both types of sequences, drawing from both the straight open and the XML open versions of the same sequence, in order to breeze through a much faster work-around process. That is not ideal, but it IS EXCELLENT. Hope for getting around (much more so) problem number 1!

    Then. In regards to your latest suggestion that, as a way to solve problem 1, I DO attempt media manage first… but you see, that invokes the discussion of number 2, now we are linking the two topics materially: Because MM causes errors too, this is experienced by many and often talked about, so do I really want to introduce MM into the equation in order to solve problem 1? But, you say, MM works “if done properly”. So, back to the “do tell!” part. Perhaps you are saying that by doing some MMing before opening the FCP5 project in FCP6, that some problems might be solved? I think that is what you are suggesting.

    I would like to try that. But for the time-being… recapturing would take two days, and I don’t have the clients offline tapes anyway, plus about a fifth of the show is Edgeworks (Kid Stays in the Picture folks) After Effects comps — so no, I am not doing any recapturing, relinking or media management on this particular show. Not yet. The only thing I’m trying to do now is open the FCP5 show in FCP6 without errors.

    HOWEVER later – January now — I WILL be recapturing the live action footage to an open timeline as HD (hence the desire for FCP6), that’s the grand design here. For the rest of the “tapeless” media I will be relinking from the offline version of the AE comps to the HD versions, among other things.

    Yes, indy documentaries, usually years in the making, make for complex sequences, hence I think why MM and or linking errors show up so much in the indy docu world, causing so much suffering.

    At that point, in all of this, MM will come very much into play in order to online / finish the show I have in my lap now — again, I’m not looking foreword to what further surprises MM has in store. But that all happens way later, not yet, I’ve got other prepping to do first. Phew, my friend, have a missed anything? Now you REALLY know my whole story! 🙂

Page 10 of 22

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