OS 10.7.5, FCP X 10.0.7, Retina Display MacBook Pro
Internal SSD of 500 GB with 337 GB available
RAM 16 GB
Project is about 35 minutes of 1080p video plus music
Try to 'Duplicate Project' from USB 3.0 Drive (2 TB with 830 GB available)
to a 6 TB Thunderbolt drive with 4TB available. Trying to move everything over as it will be an archive.
When I try to Duplicate Project, it runs for a while saying it is processing the files and the available space on the internal SSD decreases and then an errro message pops up that says the SSD is out of space, although get info says it has 273GB of space.
1. What is happening?
2. Can I reconfigure FCPX to look at another drive so it does not use the internal SSD?
3. Is there a work around solution?
1 = You are running out of Disk Memory
Reasons for that:
1 = You have "Include Render Files" checked with the "Duplicate Project Only" option
2 = You have chosen a drive that does not have enough space to accommodate the size of the project
2 = YES.... In Duplicate Project dialog - right under the "New Project Name" there is a drop-down menu called "Location" there you can choose which disk to store on
3 = See point 1 & 2 ;-)))
Item 2-No... it has 4TB available and why is memory decreasing on the SSD?
I dont know... hard for me to see what you are doing there ;-) (Post a video, perhaps)
The "Render" files have nothing to with event files... If you want to consolidate the Event & Project to another disk do this:
Select the "Duplicate Project & Used Clips" or "Duplicate Project and Referenced Events" and then choose the right location from the drop down. It works.. At least I did one as recent as yesterday ;-)
The Manual provides a good scope on the Project Duplication Options
if those are the options you are using.. There is NO excuse for writing to ANY other disk than "Movies Desk 1"
I do NOT have this issue which in now way means that you dont...
Please report this to FCPx feedback and give them a link to this thread...
Describe Step by Step what you are doing and then show them this here image.
Here is a second set
The top right is the info for
Macintosh HD Available 111GB
Movie Desk 1-Available 3.75 TB
A few minutes later
Macintosh HD Availble 87.37
Movie Desk 1- Available 3.75
For Movie Desk 1, you can also see used amount which has not changed appreciably
The bottom picture show
Macintosh HD available 7.42
Movie Desk 1-Available 3.75, but amount used has started to go up...BUT FCPX crashes
in the permissions panel of the big drive it says fetching...... Does it ever fetch the group date (under stevenseelig)
Reason I ask is that perhaps some permission on the drive got corrupted which would prevent FCPx from writing to it and perhaps making it default to the MacHD...
Try quittin FCPx and and set the permissions on the big drive to "ignore ownership on this volume"
(you need to tick the little check box underneath the permissions pane)
ALSO --- Do you have another drive you could check with... Just to make sure the drive is not weird....
Perhaps there is a bug in FCPx preventing from writing to a RAID (Given the nature of 6GB I am assuming it is a RAID)
An additional tidbit
On my Macintosh HD drive there are a huge number swapfiles each of which are 1.07GB plus a sleepimage file.
As I am sitting here, the computer is slowly deleting these swapfiles
So I Forced Quit FCPX, and reopened it. There appeared an event 'Camp Jabulani" and there was a Project 'Camp Jabulani' which appeared fine, except when I ejected the disk I was moving the project from (called Mobile 22), and then the files went missing. Inspection of the Event file showed it was all pointers and when I plugged the Mobile 22 backin, everything seemed fine.
I then chose Consolidate Project Media. FCXP created a new event called 'Camp Jabulani (fcp1) and is in the process of moving all the files over to the Movie Desk 1.
When it is done, I will test the concepts
1. Ignore ownership
2. Name change.
Immediately before FCPX crashed, it had started to write to the Movie Desk 1 drive.. perhaps it wrote as much as 2-4GB of data.
The sleepimage file is a copy of your memory that gets written to the drive to allow your mac to deep sleep (sometimes called "hibernate"). If you set your mac not to hibernate, you can the reclaim that space.
(in regular sleep, your mac still has to use a little bit of energy to keep your ram contents "alive"; in deep sleep, your ram contents are written out to the sleepimage file, and get read back on wake from sleep; this is why sometimes a mac takes a while to go to sleep, especially if it has a slow HD and a lot of RAM; this is also why some people, like me, choose to disable it, although arguably it may be "safer").
The real BIG question here is why you have all these swap files. This suggest that your real RAM gets used up, so your mac is swapping out to virtual memory - which is what is *really* using up your SSD space.
Try keeping Activity Monitor open and look at the values in the memory tab. (Activity Monitor is in /Applications/Utilities; or you can hit cmd-space to access spotligt and type ac <enter>)