Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy PROBLEMS WITH SEQUENCES

  • PROBLEMS WITH SEQUENCES

    Posted by David Reichelt on September 5, 2007 at 6:17 pm

    Hi I have a few sequences in one of my projects. When ever I cut and paste some material from one sequence into another one, it wants me to render. I checked the sequence settings and they are the same, so I’m not sure what the problem is.

    Tom Daigon replied 18 years, 7 months ago 5 Members · 8 Replies
  • 8 Replies
  • Anders Haavie

    September 5, 2007 at 6:45 pm

    Hmm. Sound very strange. Try duplicating the sequense and remove the stuff you don’t need instead. (just an idea how to get around the problem)

    Anders

  • Sherwood Ball

    September 5, 2007 at 7:28 pm

    I’m having the same problem in a workaround.

    Is FCP losing the paths to the original renders?

    G5 Dual 2.5 GHz
    6G Ram OSX 4.8
    Sata drives
    Final Cut Studio 5.1.1, Logic Audio 7.1
    PS CS2, AE CS2

  • David Reichelt

    September 5, 2007 at 7:46 pm

    I’m sorry, upon closer inspection it looks like two sequences are 29.98 frame rates while one has a 29.97 frame rate. Is there a way to change the frame rate with out disaster?

  • Tom Daigon

    September 6, 2007 at 1:10 am

    Yes, it a problem many have come across and Apple has documented. It seems to happen when you dupe a sequence…then at some time power down the computer. When you resume the rendered file are lost and cant be connected.

  • Jhmcf2

    September 18, 2007 at 10:41 pm

    Has apple issued a solution to the problem

  • Tom Daigon

    September 18, 2007 at 11:48 pm

    A little more info or a link might be nice…

  • Jhmcf2

    September 20, 2007 at 9:58 pm

    Sorry for the confusion. My last post was a question. You said apple documented the problem. Did they release a solution to the problem?

  • Tom Daigon

    September 21, 2007 at 1:24 am

    Sorry…my mistake as well. Their solution is a work around, but unfortunately I dont have a link to it.

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