Render Cache - What is it?

Every so often, a client will pop up with a question that shows off another area of knowledge I lack. This one is the render cache.

My client says some sequences won't render, giving a message about the render cache being full. Plenty of drive space on the Scratch Disk, pleanty of RAM. So, what is the render cache, and where is it?

A temp file someplace? Stored in RAM? Will closing the sequence free the render cache up?

Can somebody educate me here? Thanks.

Quad-core G5 5GB RAM, Aja Io-LA, FCP 5.0.4, Mac OS X (10.4.4), Lots of toys, over 5,500 posts served

Posted on Feb 3, 2006 2:03 PM

Reply
30 replies

Feb 3, 2006 2:18 PM in response to Brian Conner

I should have added:

If the error message is merely referring to render files, then why does it says render cache? The two instances referring to render cache in the FCP manual seem to point to the render cache being render files. If that's all it is, then I can troubleshoot from there. I was assuming the cache was a temporary thing. Grrrrrrrrrrrr.

Feb 3, 2006 5:28 PM in response to Brian Conner

That's the oddest error message ever. Render cache?

Anything out-of-the-ordinary about this client's setup? You mention that some sequences won't render - what about the others?

Personally, I think this is another bug in FCP's render scheme - like corrupted render files, and the issue of (rendered) nested sequences failing to update in parent sequences.

Feb 3, 2006 6:09 PM in response to hanumang

Client indicates it's a random thing. But since I did an Erase & Install upgrade to Tiger and new install of FCS on all three of their systems earlier this week, they say that a 2nd workstation is now seeing this. I'm waiting to hear more details - the client was supposed to call me this evening, but no call yet.

What's your impression of the two terms - render cache and render files - are they the same thing? Or is a new cache created each time you open the sequence?

EDIT: It sudenly occurs to me to list their config: 1st gen dual 2GHz G5, 2GB RAM, Io, Huge Systems SCSI array, FCS (FCP 5.0.4 and the latest updates of all the ProApps), QT 7.0.4, OS v10.4.4.

Feb 3, 2006 6:15 PM in response to Brian Conner

Well, here's a case of the blind leading the stupid (or is it the other way around??) but isn't the render cache the queue thingie that remembers the sequence of all the renders and what belong to what version of what sequence?

not at my edit station, but isn't render cache set with waveforms and thumbnails and all that when you set up your prefs?

Talking through my hat, but I'll bet a restart of fcp or a reboot of the system would clean it up.

Feb 3, 2006 6:28 PM in response to Jim Cookman

Believe it or not, I'm not offended at being called stupid. 😉

Render cache is not one of the items in System Settings.

I think you're right that it get reset by a restart of the app or the computer. The only way to know for sure is if my client sees the problem again, and immediately Quits and re-opens FCP, then tries the render again.

I probably won't know till next week, as it's getting late here in the midwest, so I doubt the client will be calling me tonight.

I'll post back when I know something, but if anyone has knowledge that will help, I'll all ears. Even if you call me stupid. (You thought you were the only one who could get away with that, huh Jim?)

Feb 3, 2006 7:24 PM in response to Brian Conner

Jim might be close to it. What are the file names created when you set your scratch disk? Isn't one of them Render and one Waveform?

Could be that the permissions for those drives and or folders got messed up. Would be the answer if client can save to another project... ie 'nother set of folders even maybe on another drive.

But I did find this from v1 days:
http://docs.info.apple.com/article.html?artnum=60277

and this from v4 days:
Audio and video render cache files are now managed separately. Modifying video edits and making changes to video effects that overlap audio effects no longer affects rendered audio render cache files, and vice versa.

and this again from v1 days:
Scratch disk options include:
Capture Audio and Video to Separate Files: when on, video and audio are saved separately, which allows for better performance during playback and capture. To save audio and video files separately, you must specify a different disk for each (no tincluding the system disk).
Video, Audio, Render storage: the disk or folder where video, audio, and rendered files are stored; specify more than one disk for increased storage space. The program automatically uses the specified disk with the most space available (rendering) or the next disk listed (capturing) when the current disk runs out of space.
Waveform Cache: the folder or disk for waveform cache files (graphical representations of audio signals)
Thumbnail Cache: the folder or disk for thumbnail cache files
Minimum Allowable Free Space on Scratch Disks: when disk space falls below this minimum, the program will use another specified disk


So it seems CLEAR to me that FCP manual writers don't know a cache from a file... though in MILITARY terms, a cache IS a storage area... not temporary as it were.

Check the permissions and trash the junk!

Hmmm.

Don't worry Brian... My wife calls me stupid... I think we can take it from Jim.

CaptM

Feb 3, 2006 7:56 PM in response to Captain Mench

The folders that are created are Capture Scratch, Render Files, and Audio Render Files.

Thr caches that are set are Waveform Cache and Thumbnail Scratch.

There is one entry named render cache in the Index of the FCP5 manual, but when you go to that page, the actual term "render cache" is not on the page. Render cache is mentioned once in the entire manual.

Not many clues, that's for certain. But I think everything's pointing to a problem with render files. Here's a theory: Somehow, FCP is getting a clue that the file it's about to render is larger than the available space.

Feb 4, 2006 6:29 AM in response to Brian Conner

Has anyone tried to search the drives for "render cache"?

Recall our collective experience that FCP's error reporting system is goofy. The error window that comes up is only FCP's best guess and it must come from a limited supply of pre-designed error box resources.

I'm guessing the error you're seeing is not directly related to the real cause but there's probably something about "rendering" that needs to be fixed. Render Manager?

The Clueless. The Blind. The Stupid. The Meek.
Together we totally rule.

bogiesan

Feb 4, 2006 7:30 AM in response to David Bogie Chq-1

LOL. We rule, because the jocks are too busy recalling their glory days. 😉

I get no hits on my system for "render cache". I'm close to concluding it's a long standing terminology error, dating way back before Apple acquired the app.

I need to ask the client if there are any layered PSD files with empty layers. IIRC, those can cause out of memory errors. Anything else?

I've had the client DL & install the latest MacJanitor, v1.3, to clean caches and temp files and stuff. The reinstall is too recent for that to be a problem now, but it couldn't hoit.

BTW, this is going to be a difficult thread to mark only two Helpfuls. We'll see what the solution turns out to be before I say it'll be equally hard to mark only one Solved.

Feb 4, 2006 8:33 AM in response to Jim Cookman

Thanks, Jim. And I'll post what I replied to your earlier Email where you said much the same thing to me:

No offense taken., Jim. I've reached the age at which few things offend me. When I was young, nearly everything offended me.
The fact is, sometimes I am very stupid. I post stuff that is wrong and knowably wrong. As soon as somebody corrects me, I slap my head, because I knew better, but posted the stupid thing anyway.
So, we're cool. No offense at all. Thanks.


Quad-core G5 5GB RAM, Aja Io-LA, FCP 5.0.4 Mac OS X (10.4.4) Lots of toys, over 5,500 posts served

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.

Render Cache - What is it?

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