Disk got full while rendering - now I'm stuck

[msf]

As a newbie using FCP and DVD Pro I have had success learning some nuances for making short sequences and burning them top DVDs….lets assume I know how to do that to my satisfaction….for sequences/projects with maybe 30 slides, effects, transitions, audio, etc.

Today I went a step further and now I am stuck.

After editing about 200-300 tiff files in Photoshop and saving them to many folders on my desk top, I imported them into a test sequence and dragged them to the timeline. They were either 72dpi or 300dpi depending on whether or not I wanted to zoom later.

When I tried to export, I was told to render first. When I rendered I got up to 80% and ran out of disk space. Now I can’t render anything, even a couple of images.


Did I fill up my rendering drive (is that the scratch drive) and should one perform maintenance to purge it of unwanted files? Does auto rendering use a lot of space and should I know what and where it is?

Am I neglected obvious maintenance to save space?

If so can I only delete files that I don’t need (i.e. test files) or can I delete files from FCP projects/sequences that I want to save for future use? (I know the tiff must stay, but am asking if temporary or extraneous files can be deleted)

I have 4 drives 2 internal, 2 external – HD2 is getting filled up (even before this test) and HD1 has around 10 gigs left.
Externals have 40 gigs free if I want.
Can I change the drive where this takes place to another drive that is less full?

Problem is now; I can’t render anything including small sequences. IS this a space issue or should I check my image files for corruption?

There are no audio, transitions, effects in this test.

Can anyone give my parameters on what folders to cleanout for both scenarios; one where you want to save the project for future use and one where it was a test or no longer wanted?

I am making a lot of assumptions that may be way off base…please correct my whole premise if I am asking dumb questions.

Thanks,


Mark

[terryj]

As a newbie using FCP and DVD Pro I have had success learning some nuances for making short sequences and burning them top DVDs….lets assume I know how to do that to my satisfaction….for sequences/projects with maybe 30 slides, effects, transitions, audio, etc.

Today I went a step further and now I am stuck.

After editing about 200-300 tiff files in Photoshop and saving them to many folders on my desk top, I imported them into a test sequence and dragged them to the timeline. They were either 72dpi or 300dpi depending on whether or not I wanted to zoom later.

See my earlier post back on your questions regarding
Preparing images for FCP.

When I tried to export, I was told to render first. When I rendered I got up to 80% and ran out of disk space. Now I can’t render anything, even a couple of images.


Did I fill up my rendering drive (is that the scratch drive) and should one perform maintenance to purge it of unwanted files? Does auto rendering use a lot of space and should I know what and where it is?

Possibly yes. And the fact that you have images of various DPI
will lead to increased space needed to render the files to
the timeline. Auto Rendering ALWAYS uses space, that is why
you should set a seperate target drive just for Scratch Disc,
or at least partition a big ( 250GB or more) HD so you
can properly manage your project files in one location,
and have dedicates scratch disc space in another.

Am I neglected obvious maintenance to save space?

If so can I only delete files that I don’t need (i.e. test files) or can I delete files from FCP projects/sequences that I want to save for future use? (I know the tiff must stay, but am asking if temporary or extraneous files can be deleted)

NO FILES associated with a current project should be deleted!
any files that were or are NOT of the current project should be pitched!

I have 4 drives 2 internal, 2 external – HD2 is getting filled up (even before this test) and HD1 has around 10 gigs left.
Externals have 40 gigs free if I want.
Can I change the drive where this takes place to another drive that is less full?

This sounds similar to my system at work:

Internal HD one: Boot HD, 80 GBS
Internal HD two: FCP Scratch, 200 GB
External DV one: Incoming Video, 300 GB
External DV two: Rendered Project Archive, 300 GB

The workflow we use is this:

Nothing gets put on BOOT HD, that includes the Desktop!
( the BOOT HD is for the OS, and Compressor will draw
extra VM Ram from their, as well as FCP , so keep it clear
except for your applications and OS)

All media files get stored onto Incoming Video, including PS
Files, audio files, captured DV, all into a folder located on
Incoming Video drive named the name and date of the project
( such as Training_Vid_8152005)

Files are then created in FCP, with FCP scratch its dedicated
scratch drive.

Once complete, it is rendered out to Rendered Project Archive,
and is either taken from their to the DVDSP3 station to be mastered,
or is kept there for future reference.

Problem is now; I can’t render anything including small sequences. IS this a space issue or should I check my image files for corruption?

There are no audio, transitions, effects in this test.

Can anyone give my parameters on what folders to cleanout for both scenarios; one where you want to save the project for future use and one where it was a test or no longer wanted?

I am making a lot of assumptions that may be way off base…please correct my whole premise if I am asking dumb questions.
Thanks,
Mark

it is definitely a space mismangement issue. Try to re-setup your setup
similar to my work one, and throw away any junk NOT pertaining to
the current project.

[msf]

Thanks,

I violated all hyour rules, all folders on dsktop, too little hard drive space, different dpis, and orphaned test projects...I will free up HD2 with one of my externals, and read up on how to distinguish files I dont need and ones I shoudl keep. Plus I need more space which I will buy before i mpose upon you again.

thanks a bunch

[terryj]

Its ok..Your just getting used to FCP.
There's more to the learning curve than just
reading the manual...