Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy The problem with FCP. (big projects, and slow copy-paste)

  • The problem with FCP. (big projects, and slow copy-paste)

    Posted by Anders Haavie on April 9, 2008 at 5:36 pm

    I have been working with fcp for years now, in big broadcast environments. (xsan etc) Recently we’ve had problems with projectfiles getting very big. We are working on the norwegian version the bachelor shot in panasonic HD, and it’s quite alot of footage. (one episode-1 project). Our projectfiles will be in the ballpark of about 250mbs. When our projects get this big we start getting problems with fcp being unstable, and crashing. One solution is to delete lots of the footage, but even then we might experience projectfiles expanding. The solution is to make a new projectfile and copy paste from one project to the next. However.. since fcp reached version 6.x I think copy-pasting has been getting REALLY slow. If I duplicate a complex timeline (45 minutes) the operation will take about a minute.

    Let’s hope new versions of fcp will fix these problems. I deal with alot of avid editors, and it’s embarassing to see how bad fcp deals with complex projects, compared to avids.

    Anders

    Xraid-Xserve-Xsan-Xeverything

    Mark Raudonis replied 18 years, 1 month ago 9 Members · 10 Replies
  • 10 Replies
  • Aaron Neitz

    April 9, 2008 at 5:48 pm

    Won’t get any arguments here. It’s been a bear ever since inception. Old coding in there that just doesn’t hack it when things get large.

  • Rob Alexander

    April 9, 2008 at 5:56 pm

    Anders,

    regarding the slowing down, does your system use blackmagic or aja hardware?

  • Arnie Schlissel

    April 9, 2008 at 5:58 pm

    Anders, I had a similar problem on Perestroika.

    How many sequences does your project have? See if you can remove some older sequences that you don’t need. If you’re worried about deleting them, you can export an XML of each one, or put them into a new project that acts as your archive.

    Also, I’ve seen instances where if I duped a timeline & exported an XML, the XML was bigger (sometimes much bigger!) than if I copied & pasted everything into a new timeline & exported an XML from that.

    Arnie
    Now in post: Peristroika, a film by Slava Tsukerman
    https://www.arniepix.com/blog

  • Anders Haavie

    April 9, 2008 at 7:23 pm

    Our macs use both Aja and Decklink cards. I am aware of the problem with decklink cards. This is not one of those.

    Anders

    Xraid-Xserve-Xsan-Xeverything

  • Anders Haavie

    April 9, 2008 at 7:29 pm

    XML might fix this, but it is not very convenient to do this in big productions with thight deadlines. I know there are ways to deal with this, I am just dissappointed that fcp doesn’t deal with these problems very well.

    Anders

    Xraid-Xserve-Xsan-Xeverything

  • Chris Borjis

    April 9, 2008 at 7:59 pm

    FCP begins its sluggishness around the 20 minute mark for me.

    Anyone who uses it for long form projects (I do mostly TV commercials and short industrials) knows that it can only
    be reliably used with 30 minute or less sequences.

  • Tom Wolsky

    April 9, 2008 at 8:21 pm

    It probably depends a great deal on how you work. I’ve done a few 60 minute shows working in one timeline and never felt it was especially sluggish. Turn the waveforms on only when you need them helps a lot.

    All the best,

    Tom

    Class on Demand DVDs “Complete Training for FCP6,” “Basic Training for FCS2” and “Final Cut Express Made Easy”
    Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 3.5 HD Editing Workshop”

  • Jason Porthouse

    April 9, 2008 at 10:34 pm

    Hmm. It’s a funny one this. I’ve just finished posting a 95 minute documentary and the project has all been on one timeline. I’ve duped the timeline every so often (for reversioning) and occasionally cleaned up the project. But no issues with slowdown or crazy behaviour. I’ve had a few people look at me as if I’m mad, but all fine so far (touch wood)

    Jason

    _________________________________

    Before you criticise a man, walk a mile in his shoes.
    Then when you do criticise him, you’ll be a mile away. And have his shoes.

    *the artist formally known as Jaymags*

  • Chi-ho Lee

    April 9, 2008 at 11:18 pm

    [Chris Borjis] “Anyone who uses it for long form projects (I do mostly TV commercials and short industrials) knows that it can only
    be reliably used with 30 minute or less sequences. “

    I completely disagree. I’ve used FCP for many long form broadcast docs (45-52min) and I’ve never felt the sluggish. I’m sure I’m not bless by Saint Steve. I think project file size has a lot to do with it. Keep it under 100mb by deleting or archiving old sequences to another project.

    Chi-Ho Lee
    Film & Video Editor
    Apple Certified Final Cut Pro Trainer
    http://www.chiholee.com

  • Mark Raudonis

    April 10, 2008 at 4:35 am

    Another vote for “NO PROBLEMS” with long form.

    Just completed a 2 hour special for MTV. We work with multiple projects open simultaneously in a workgroup environment, which keeps the individual project size down. “Project bloat” is best avoided, and if you do so, the length of show is irrelevant. I think people equate “FCP problems” with longform because one tends to spend more time on a long project, thereby accumulating lots of garbage along the way. If you’re careful to keep a clean project, FCP can keep up with you, regardless of the length of show.

    It also doesn’t hurt to have at least 4 gig of RAM on your computer.

    Mark

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