Insufficient disk space?

I just tried to render a ten minute sequence in a FCP project I've been working on, and I got a prompt that said "Render error: Insufficient disk space. Free up space with the render manager and retry?" I didn't want to get rid of any of my renders, so I checked my render drive, and there was 15 gigs of free space on it. Then I checked to see how much total data FCP was using on the drive, and it was only about one gig (and my project is already more than half rendered). So why is FCP telling me the disk is full when it's only using a small fraction of my free space?


I deleted some files from the disk anyway, so now it had about 20 gigs of space, then I started up FCP and tried to render again, and I still got the same message. Then I went into the system settings and added a second scratch disk, which had about 50 gigs of space, but then when I tried to render, I got the same message again!


Finally I went into the render manager and got rid of the undo queue and a few other things, and this time I was able to start the render process, but it said that it would take "70 weeks!" After a few minutes, that number went down to a few hours, but then it stopped when it was about halfway through, and I once again got that "insufficient disk space" message.


So why does FCP think that I have no disk space when I have plenty of space?


I'm using FCP version 5.1.4.

MacBook, OS X Mavericks (10.9), 2.13 GHz Intel Core 2 Duo, 5 GB ram

Posted on Feb 16, 2014 4:29 PM

Reply
5 replies

Feb 17, 2014 5:23 AM in response to Jeremy Bell2

Just to be clear - are you running FCP 5 on a MacBook runing OSX 10.9? If so, you are running ancient software on a current OS where there has been no support/updates in, what has it been, 7 years?


If you have plenty of free space on all drives, things that cause "out of space or out of memory" errors can be using CMYK or B&W graphics in a sequence or having a corrupted sequence, render or preferences or editing a non-native format.


To address corrupted prefs -use FCS remover from Digital Rebellion to delete your preference files.


To address a corrupted render - delete all renders and start again


To address a corrupted sequence - copy the files in the sequence to a new sequence.


To address a corrupted file - do a binary test - try exporting half the sequence and see if it works, if it does, try exporting the other half. Once you find the clip that is bad, go back to your original media and reimport.


Of course it could be you are editing a non-native format like mp4 or h.264. If you are, the material must be converted to a native format - like DVCProHD - before editing.


x

Feb 17, 2014 1:16 PM in response to Jeremy Bell2

Jeremy Bell2 wrote:


I just tried to render a ten minute sequence in a FCP project I've been working on, and I got a prompt that said "Render error: Insufficient disk space. Free up space with the render manager and retry?" I didn't want to get rid of any of my renders, so I checked my render drive, and there was 15 gigs of free space on it. Then I checked to see how much total data FCP was using on the drive, and it was only about one gig (and my project is already more than half rendered). So why is FCP telling me the disk is full when it's only using a small fraction of my free space?


I deleted some files from the disk anyway, so now it had about 20 gigs of space, then I started up FCP and tried to render again, and I still got the same message. Then I went into the system settings and added a second scratch disk, which had about 50 gigs of space, but then when I tried to render, I got the same message again!


Finally I went into the render manager and got rid of the undo queue and a few other things, and this time I was able to start the render process, but it said that it would take "70 weeks!" After a few minutes, that number went down to a few hours, but then it stopped when it was about halfway through, and I once again got that "insufficient disk space" message.


So why does FCP think that I have no disk space when I have plenty of space?


I'm using FCP version 5.1.4.

Unless your "render drive" is less than 250GB, you are violating an accepted guideline for disk usage (never exceed 80-85% of total disk capacity) and FCP doesn't want to help you... in an era when data storage is less than 5¢ a gigabyte it seems foolish to endanger your projects by trying to cram a few more bytes onto an already full drive.


More than 50-60% on system drives and 80-85% on data drives is just asking for trouble.

Feb 27, 2014 2:41 PM in response to Studio X

Thanks for your replies everyone -- I got a bit sidetracked and wasn't able to check your answers until now.


Just to clarify, I'm using small render drives: A 40 gig drive and a 160 gig drive. My 1TB drive died on me last year, and these drives are plenty big enough for what I'm doing anyway.


Anyway, it turns out that when I added the second scratch disk, I forgot to actually check off those Video&Audio Capture and Video&Audio Render check boxes, so even though a second drive was listed in the scratch disks, it wasn't actually enabled for use.


I'm still not sure why it wasn't finding space on the first drive, but at any rate, I deleted most of the renders and re-rendered them, and now it seems to be working fine, so maybe Studio X was right about it being a corrupted render.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Insufficient disk space?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.