[Rob Gilpatric]

Oh, I forgot number three

(3) If these both fail, cut and paste the *contents* of your sequence (i.e. all the clips, transitions etc.) from the TL into a new sequence in a new project. If that doesn’t do it, I’m not sure what else to try.

Rob

Rob Gilpatric

[Rob Gilpatric]

Wow, this sounds a-n-n-o-y-i-n-g. But it not a setting issue. Most likely, you’ve got a small corruption or glitch in either your sequence or your project. Some things to try:
(1) Trash your preferences. I doubt this will work. Go here to learn how: <https://docs.info.apple.com/article.html?artnum=93385>.
(2) Cut and paste the sequence (from the browser) into a new project; Save the project, close the original, and test FCP’s performance. This will test if the sequence has a glitch.
(a) If the problem goes away, then the problem is in the project and you must beware of that project. To protect that work from corrupting further, cut and paste all of its contents into a new project and test performance again.
(b) If the problem persists, then the problem is *not* in the project — the problem is in the sequence itself and you must do an emergency measure: Export the sequence as XML data, then re-import it into a new project and see if the problem persists. This will scour out any glitches because the process completely alters the language in which the sequence is stored. If that don’t work, you’re up the creek, but it should. 😉

Rob

Rob Gilpatric