Creative Communities of the World Forums

The peer to peer support community for media production professionals.

  • Posted by Steve Denn on June 24, 2005 at 1:12 pm

    We have a Apple Raid 3.5T connected to a G5 Dual 2.5 w/4gigs of ram, FCP 4.5 on OS X 10.3.9.
    I have the Raid split into two drives 1.5T aside, I’m down to 567megs on the first half of the Raid & haven’t used the other half yet.
    Here is the issue. Last week I could hit the Capture Now Button & within a second it would start recording.
    This week is a little different, now when I hit the Capture Now button it takes 8-10 seconds to start recording,
    I get the Allocating Disk Space message at the bottom of the Capture Now window.
    I trashed my FCP Prefs & POA Cache & still take the 8-10 seconds to go into record.
    I have seen this issue posted in the past but never read the findings.
    Any Clues?

    Steve Denn replied 20 years, 10 months ago 4 Members · 6 Replies
  • 6 Replies
  • David Bogie

    June 24, 2005 at 2:22 pm

    Why do you have the RAID partitioned? That starts to defeat the purposes but never mind.

    You’re out of space. Period.
    FCP requires a minimum amount of drive space to be left open and you’ve probably hit that ceiling, it’s in the default prefs so tossing them won’t change anying.
    Move your scratch drive designation to the other partition.
    Post back.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • Steve Denn

    June 24, 2005 at 3:52 pm

    I wrote I’m down to 567megs of space I ment 567gigs left. My error.
    The company inatlled it that way , 2 1.5T’s in each bay.
    I tried to assign it to the other side, it does the same thing
    a good 8-10 seconds to start in record

  • Daniel Weber

    June 24, 2005 at 4:31 pm

    Why use capture now? log and in and out and let the system do the work.

    Guess I am an old style editor, but I can never figure out why people just use capture now to bring in footage.

    Don’t mean to harp on your situation though.

    Do you have the 512 cache on the RAID?

    Dan Weber

  • Steve Denn

    June 24, 2005 at 10:34 pm

    Dan

    I guess the question is work flow.
    I have worked in a broadcast house since the mid 70’s.
    When you have to meet a deadlines in a short periods of time,
    I can’t stop & put an in in & then zip to the end of my clips for the outs. (way too many tapes)
    For my work flow it’s just not time efficient. OUR in house producers seem to frown apon that.

    Not sure on the amount of cache on our raids
    But I do remember hearing more than 512.

  • Michael Alberts

    June 24, 2005 at 10:51 pm

    From my experience, the larger the volume, the longer Capture Now takes to estimate the drive space allocation. This has always been true. There was a new driver for the XServe RAID that may or may not have reduced this problem. I’m surprised that you haven’t experienced it before. If you want to start Capture Now immediately you can select another smaller drive as your Capture Scratch and move the media later. Capture Now to your internal drive will be almost instantaneous.

    Michael Alberts
    Ambidextrous Productions, Inc.

  • Steve Denn

    June 24, 2005 at 11:19 pm

    Micheal

    I will have to dissagree with you on that one.

    We have converted all our Avid Edit Bays to FCP 4.5 with Apple XServer Raids.
    Each room comes with it’s own 3.5T Apple Raid. Since they have been installed back in Jan. In the other three FCP bays when they hit the Capture Now, it starts recording within a second.
    This just started last Monday, my room is the only room that this is happeninig to.

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