[Arnoud No]

Tom thanks for you re:
it’s an outline text or normal text generated by fcp itself (from the pulldwn options in the Viewer).
Other apps don’t seem affected ram wise.
When I conform the sequence to DV it doesn’t occur (even though the native codec is prores).
Other titlers (Boris 3D) have the same issue but effects, like a timecode generator etc do not.
It appears indeed the cache fills up after just one or two texts, but is there a way to clear it?

[Arnoud No]

Tom, somewhat off-topic but dealing with the same orange nightmare:
on a prores HD 422 proxy (or no proxy, same thing) timeline, I get the still cache warning when adding a text layer (subtitles). See the image attached. Even on a new clean project with just one clip in it, same thing. Adjusting the cache doesn’t solve it. Notice in the image how the first text is okay, but from the second it goes wrong. The image plays back quite jerky, as if it needs a lot of real time rendering.
This occurred about a week ago with green lines first, and going to orange next.
I’ve had no clues so far neither from my own network nor Cow. Do you perhaps have an idea?

FCP 703 / MBP 15″ i7 / 8GB RAM / FW800 WD 2TB

[Arnoud No]

quick update I found out in the mean time that FCP indeed only supports 2GB RAM (still quite a lot of course!) and trashed prefs, updated to 7.0.3, but the problem persists. I feel the problem must be somewhere else.
“The RT still cache is full” Increasing it’s size in the Memory tab does nothing. Playback frame rate is low, what is going on?!

thanks for any ideas on how to solve this.

arnoud

[Arnoud No]

Thanks Jeremy for clarifying that. Like you said it’s not the greatest sorting concept in the world but who knows now I at least understand it who knows ill be able to work with it!
Cheers, Arnoud