[Chris Elley]

I was having trouble getting the text to copy into Word. However, I found that it copied fine into Text Edit. From Text Edit, you can copy to Word.

Chris Elley
Electro-Fish Media Inc.
Austin, Texas

electro-fish.com

[Chris Elley]

It’s probably a stretch, but would it work to run TC OUT from the camera to REF IN on the Kona (in addition to HD/SDI)?

I doubt the Kona utilizes the REF IN when the input is set to HD/SDI, nor am I convinced the TC audio would be compatible with video reference signal. Just lobbing out ideas.

Chris Elley
Electro-Fish Media LLC
electro-fish.com

[Chris Elley]

Dean,

We did not find an ideal solution to this problem. The only effective route was to break the project into a number of smaller projects.

On principle, I do not like doing this, however it is a feasible workaround. In this endeavor, we’ve begun to think of project files as very large bins or folders, so we keep our scenics in one project, our music in another, etc. Rarely do we need many projects open at the same time. Regardless, it’s still a bummer.

If anyone has resolved this issue, please let us all know.

Best,
Chris Elley
Electro-Fish Media
Austin, Texas
electro-fish.com

[Chris Elley]

Jack,

We are on two external SATA 8-bay towers from Sonnet, with a card from CalDigit.

Chris Elley
Electro-Fish Media LLC
Austin, Texas

[Chris Elley]

Jack,

We never reached a true solution. Practically speaking, we took our 100-hour project and broke it down into many smaller projects. This eliminated the error messages and quirky behavior.

We do not consider this the best of solutions, because we know that some projects cannot be broken up as easily, nor would you want to. However, we followed all of the other information posted on this thread to no avail (incl. paired memory from the same manufacturer installed evenly across both platforms).

There seems to be hope that in the future, individual applications will be able to utilize more than 4 GB of RAM. We’re told that FCP uses 1.5 GB for framework and up to 2.5 GB for its other functions.

In our understanding, 8 GB of RAM means FCP can use up to 4 GB and other applications can run simultaneously with relative ease.

If you do discover something that eliminates your error messages, please post it on this thread.

Best,
Chris Elley
Electro-Fish Media LLC
Austin, Texas

[Chris Elley]

I confirmed that my hard disks are not allowed to sleep, however they ‘were’ accessible to Finder, so that has been corrected.

This brings me to Borjis’ point to set the processor to “High” in the “power saver area.”

I cannot find such a setting. I’ve looked through all the system prefs. “Power saver” sounds like “energy saver” but energy saver does not appear to offer me such an option.

Am I looking in the wrong place? Could this be a setting only available in older versions of the OS or older systems?

Thanks,
Chris

[Chris Elley]

We’re using a 4TB RAID 0 eSATA Port Multiplier tower with 8 bays. The (8) 500GB drives are striped into (4) 1TB partitions (A, B, C, D). Currently, the footage resides on Partition C (with 40 GB still available) and on Partition D (with 25 GB still available). The eSATA box is from Sonnet. The SATA controller card is CalDigit FASTA-4e 4 port PCIe Host Adapter.

I do notice that the SATA drives almost “go to sleep” sometimes after not used for several minutes. Give them 10 seconds or so, and they wake up and work perfectly until I leave them unattended for awhile. “Work perfectly” that is, with smaller projects.

I’m happy to provide additional information.

Thanks,
Chris Elley
Electro-Fish Media LLC
Austin, TX

[Chris Elley]

I’m not convinced by the corrupt file theory only because we have started over fresh a few times with the same results. That makes me lean toward a limitation of the application and OS, but it sounds like confirmation from others would help.

Is anyone out there successfully editing very large projects that are comparable to the ones mentioned in this thread?

Thanks,
Chris

[Chris Elley]

We are having the exact same problems on a MacPro 8-core with 8GB of RAM running FCP 6.0.2. SATA storage with plenty of space available. Healthy system drive, etc. Tiger.

We have 100 hours of DVCPRO HD footage in the project and it refuses to show video on playback, even after turning off external video output. The only thing that comes up in the preview window is bright green. “Out of Memory” is one of a handful of error messages that can pop up. We can see all bins and navigate about the project, but none of the video or audio will actually play.

We have trashed preferences and rebuilt the project a few times with the same results. We noticed the phenomenon set in around 70 or 80 hours of DVCPRO HD footage. I’m not sure what the file size was at that time, but with all 100 hours the FCP file is around 135 MB.

The only workaround we have found is to break the large project into several smaller projects. This method has produced absolutely no error messages and beautiful performance, reaffirming the system’s performance. However, not all projects can be conveniently broken up, and this worries us for the future. Has anyone been able to pinpoint the source of these errors?

About Memory: We’ve been told that FCP (and other apps) max out at 4GB of usable memory. 1.5 is for background framework and up to 2.5 is user definable in FCP. Apparently, the only benefit beyond 4GB is the ability for the system to run other applications simultaneously. Does anyone concur?

Thanks,
Chris Elley
Electro-Fish Media LLC
Austin, Texas

[Chris Elley]

The Mac Pro is very new, so there has not been opportunity for maintenance.

Rafael, I am not familiar with setting a processor to “high.” What do you mean by this and how would one do it?

I have learned that all OS X applications are currently limited to 4GB of RAM. In the case of FCP, 1.5 is used in the background and only 2.5 is user settable. This current limitation seems to mean that very large projects (such as 100 hours DVCPRO HD) have to be split into smaller multiple projects. Can anyone else confirm this?

Thanks,
Chris