Im confused how your Mac Pro is set up
This should be:
the system boot drive containing the OS, applications and your FCP project files.
the internal Raid which is a separate physical drive from the boot drive containing the scratch disc folder
see the Edit Smarter web page on how best to configure FCP here:
I would suggest deleting FCP preferences as per Digital Rebellions Preference Manager
I would further suggest buying and running Disc Warrior on all your drives regularly:
OK...I know the "shoulds", and while I use Disc Warrior religiously at home, I leave maintenence at this client's facility to those who get paid to do it here (I'm a mere freelancer without an admin login).
What I'd like to get out of this post and discussion is...
is the fact that ALL data, apps, prefs AND media reside on the same logical unit (the RAID5 which occupies all four physical slots in the computer) the reason I'm losing render files? And if so, what is the mechanism behind this mystery?
To clarify Gary, the machine is set up simply (and incorrectly, according to best practice): the tower has 4 physical 1TB drives striped into a RAID5 array, giving 2.61 TB of usable space. All files (system AND media) are on this RAID. I have an external server attached via ethernet which is used soley for backup storage. That's pretty much it...
is the fact that ALL data, apps, prefs AND media reside on the same logical unit (the RAID5 which occupies all four physical slots in the computer) the reason I'm losing render files?
Cant guarantee this but this sounds like a disaster!
Every competant advice I have seen suggests the following:
read Larry Jordan's advise (setting scratch disc)
Final Cut application installed on boot drive
boot drive has OS installed, applications and project files
project files backed up daily to a separate back up drive
project files are the .fcp files that are saved from FCP when File > save as
scratch disc folder located on the media drive not on the boot drive
media drive is physically separate from boot drive and offers sufficient throughput for the CODEC being used
hi mike, did you ever figure this out? i'm having the same problem and it's getting worse. i'll save a project and then re-open it immediately and most of the render files are gone. no change in scratch disk or anything else. i like to add color correction (LUT's which require lots of rendering) after a rough edit so nesting isn't really an option as i'm still editing.
i have 7.0.3
system SSD with OS and apps
internal RAID (scratch) with multiple 1TB drives (RAID 0)
12 GB RAM
dual quad 2.26
gt 120 and gtx 285
The one thing that occurs to me is whether the system is connected to a network. If so, I'd try disconnecting and see if that solves the problem.
Also, do the renders actually disappear or do they simply become disconnected? I know that it's usually not possible to "reconnect" renders, but this will give us a clue.
Also, I wonder whether it's an issue with the raid. Since the OP also had a raid. Why not get an external firewire drive and try setting that up as your render scratch disk? I realize that the thruput might not be ideal, but as a troubleshooting step it would be extremely useful. If the renders do NOT disappear from the external firewire drive, the problem is almost definitely something in the raid setup.
@ Heath, no, never did actually "solve" the problem, however, minimized the amount of rendering needed during edit by correcting our edit workflow to stay in XDCAM EX (1920x1080i) all the way through the edit, converting to (required by the mothership) 1440x1080i XDCAM HD for "feed" to the playout server, etc.
@ Michael, a useful suggestion, sir, to set up a temp external rendering disc...I have one I can donate to the cause for the time being and will check.
System is of course connected to a network (isn't everyone?), no getting around that...I'll just render to a specific disc first and see if the files actually "disappear" or if they just disconnect, and report back.
And, thanks for the troubleshooting links. As might be noted by my silence, system behaves much better (not perfect, but then neither were the builders of said computer...) by simply editing in our shooting codec. Like they say, put the square peg in the square hole...