Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy hi res stills slow down and crash fcp

  • hi res stills slow down and crash fcp

    Posted by Amy Wilson on August 11, 2008 at 9:39 pm

    I am editing a feature doc on a 2x 3GHz dual core intel mac pro (6GB mem) using fcp 6. I have lots of hi res photos that I need to use and am doing everything for this project online, but just by double clicking on the jpegs in my browser to look at what I have to work with ends up really slowing down fcp after looking at a few photos and even when I stop trying to look at the photos, it is so slow that I can’t edit and I have to restart fcp. I’m not that savvy with motion or after effects. Do I need to reduce the resolution and have my photos be an offline edit, while the rest of my sequence is online? Can I recompress the photos to another file type while maintaining the high resolution and native aspect and that will solve it? Please tell me there’s a good solution within fcp.
    thanks
    Amy

    Amy Wilson replied 17 years ago 6 Members · 15 Replies
  • 15 Replies
  • David Roth weiss

    August 11, 2008 at 9:50 pm

    Amy,

    To help you we need to know the following:

    1) What are the pixel dimensions of the scanned photos?

    2) What are the file sizes of those photos?

    David Roth Weiss
    Director/Editor
    David Weiss Productions, Inc.
    Los Angeles

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, and Indie Film & Documentary forums.

  • Amy Wilson

    August 11, 2008 at 9:56 pm

    My project is HD (1920×1080, 23.98fps) so I need very high res stills. Our different sources have given us all different file sizes but some of the larger ones are 1800×1204, 1500×1062… around 1.3MB, 580K, 1018K, etc.
    Thanks

  • David Roth weiss

    August 11, 2008 at 10:27 pm

    Amy,

    Those stills aren’t actually all that large and so they really should not be causing the issues you’re reporting.

    Are the stills located on your media drives? And, even more important, are your media drives by any chance getting full?

    David Roth Weiss
    Director/Editor
    David Weiss Productions, Inc.
    Los Angeles

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, and Indie Film & Documentary forums.

  • Oliver Peters

    August 12, 2008 at 12:29 am

    Make sure they are RGB and not CMYK.

    Sincerely,
    Oliver

    Oliver Peters Post Production Services, LLC
    Orlando, FL
    http://www.oliverpeters.com

  • Rafael Amador

    August 12, 2008 at 3:06 am

    Have you increased the FC’s “Stills Cache”?
    In the Preferences.
    Rafael

    http://www.nagavideo.com

  • Amy Wilson

    August 12, 2008 at 1:47 pm

    My stills are on my media drive, which still has 2.3tb free.

  • Amy Wilson

    August 12, 2008 at 1:51 pm

    I just opened a bunch of them in photo shop to check and all the ones I checked so far are RGB.

  • Amy Wilson

    August 12, 2008 at 1:55 pm

    That sounds like a great idea! I will do that and see how it goes. Thanks!

  • Amy Wilson

    August 12, 2008 at 3:17 pm

    increasing the stills cache helps somewhat, but just means that it takes a little longer before fcp slows down again. Should I use a file type other than jpeg maybe?

  • Rafael Amador

    August 12, 2008 at 3:32 pm

    Hi Amy,
    JPG is a compressed format, so before to be processed needs to be decompressed (converted in a bit map or so).
    Any uncompress format (PNG, Tiff, Targa..) would made unnecessary this step, so in theory would make the process easier.
    Anyway, with the system you are using, you shouldn’t be having those problems even managing many many .jpgs.
    Try to optimize your system: maintenance, permissions, clean directories.
    Rafael

    http://www.nagavideo.com

Page 1 of 2

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