Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy help – canvas doesn’t match timeline — ghost images appear

  • help – canvas doesn’t match timeline — ghost images appear

    Posted by Mariefilm on January 21, 2007 at 5:39 pm

    Hi,
    After having no problem in panther and final cut 5.0 I’ve had to upgrade to tiger (10.4.8) and FCP 5.1.2. When I opened and edited my project, I got a sort of ghost image (a still image from elsewhere in the timeline) appearing in the canvas over where another clip should be. This happened once and I tried everything (deleting and then brining in clean copy of clip) and no dice. The good news is that when I output to QT.mov, everything looks as it should.

    But suddenly, I’m having this problelm in many areas of my project, which makes it hard to edit at all. Has anyone else had this problem? I’ve tried rendering everything, but it doesn’t change anything.

    Two other clues:
    1) at the same time I’ve had trouble getting VoiceOver to recognize where i am in the timeline so have had to create “In” marker for the project at that spot where I’m doing a new voiceover.
    2) For what it is worth, there does seem to be some odd lines (same color as rendered project but as if cut into smaller pieces in the area of the timeline that triggers this).

    please help! (and thanks in advance)

    Mariefilm replied 19 years, 3 months ago 2 Members · 2 Replies
  • 2 Replies
  • Jhaughey

    January 21, 2007 at 10:48 pm

    Have you deleted your preferences? You should also delete all the render files associated with your project using the render manager (within tools) and re-render everything…. When weird stuff like this happens to me… nine times out ten these two actions put it all right again….
    hope it works out.

    Joe Haughey
    https://www.pogofilms.com

  • Mariefilm

    January 22, 2007 at 7:51 am

    Hi Joe,
    I had deleted preferences and renders, but it turned out to be a corrupted sequence so I ended up cutting and pasting into a new sequence and it worked.
    all the best – and thanks for responding.
    Marie

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