-
Slow to start on the Capture Now
We have four edit bays with OSX 10.3.9 – FCP 4.5 on Dual G5 2.5’s – 4 gigs of ram. Each room is connected to it’s own Apple Xserve Raid 3.5T. Digitizing footage via AJA SD box & a Sony Beta SX machine SDI in & out. The Raids are split in half, each room has two icons on their desktops, 1.35T each. Limit Capture Now to: set to 10 minutes.
Ok now for the problem. We all use that so called practice of Capture Now because of the short lengths of clips we use daily. We do name them with proper names, so they don’t end up with a bunch of untitled clips, we also use Batch Capture, but manily Capture Now. In the past, when we all hit the old Capture Now button it would start digitizing the second you hit it, now it takes eight or more seconds to start, after the Allocating Disk Space message goes away. Yes we have tried to switch what half of the Raid we are using. You might be asking yourself (self) how much space is left per Raid per room? all averaging around 1.12T & 1.15T left. It’s hard to believe it’s a disk space issue. BUT when we do use the Batch Captures, that starts right up. Anyone else using the same type of hardware setup, & having these issues.
Ok I’ll say it, stop using the Capture Now function & use Batch Capture instead. Just want to figure out what went wrong & how to fix the problem, since it’s happening in all four Bays. (maybe a bug)
Thank You.
TD/Production Editor
WJBK FOX2 Detroit -
1 Reply
-
If you turn on the Limit capture now captures in the scratch disk settings to some sort of file size limit, the system will allocate that disk space before it starts the capture… suppose that’s what’s going on?
Jerry
Reply to this Discussion! Login or Sign Up