Transcode not enough space

[Eric Santiago]

Did you check your project settings like where all the files are?

Seems to think it’s on the local drive.

Unless the footage you are transcoding is 4x the size of the drives.

What settings are you using?

[Ben Balser]

Duration of the Project?

What codec are you exporting to?

What drive are you specifying FCP to write that to?

[Ted Irving]

Right now TRT is 15 minutes. Aiming for 30 min. External USB3.1 drive is 14TB. Codec is Apple Pro Res which should have smaller file sizes than H.264.

[Doug Metz]

“Right now TRT is 15 minutes. Aiming for 30 min. External USB3.1 drive is 14TB. Codec is Apple Pro Res which should have smaller file sizes than H.264”

ProRes is typically quite a bit larger than H264, but that depends on the bitrate for the H264 files. I’m going to assume that your external 14TB drive is HDD and not SSD, so you should check that the disk’s format is correct. Partition map should be GUID (device level), and volume format should be HFS+ for spinning disks (APFS for SSDs). You can check this with Disk Utility – show all devices in the upper left. If the format isn’t correct, you’ll need to back up everything on that drive and then wipe it / reformat.

In any case, you’ve got plenty of space available, just need to verify a few things first.

[Ted Irving]

Thanks for all the tips. Error seems to have disappeared, however, I now have some files with the dreaded all black and red that are not offline. LOL SMH

[Robert Olding]

It’s probably the cache location. Most applications use both RAM and the cache location as temporary storage while they’re processing files. My assumption is that your cache is set to the Library or some other place on your local disk.

If you’re able, you should purchase a really fast separate 1 to 2 TB drive and use it only for the cache location.