It seems that with Red Cine 8 every time I make the slightest adjustment it wants to process the entire clip, rather than the frame I'm using for judgement. This, on a laptop, can make basic first light a very tedious arrangement. How do I stop it?
|
|
Paul,
Thats correct. We re-cache the clip whenever changes are made. You can shorten the clip (set in/out point) or edit a still, save the look, and copy it back
to your original clip if you don't want this behavior.
We do not offer a way to turn off background caching.
David
Thanks for the response, David. It strikes me that being able to turn off caching in the main interface would be a great boon, the still editing method is tedious in comparison, and it's too easy to forget that you've added extreme in/out points. Could that be added to a future release?
Paul: that's definitely something worth considering. Do you mainly run in to this issue when you're fine tuning a look (doing many changes back-to-back) or are there other use cases you run in to this issue?
There is a setting in the preferences in the Playback section for Maximum Memory Usage (% of total Ram) if you set this to 1% the amount of frames it caches will be reduced drastically, this will effect playback performance, however you can always set it to a higher value when you are done grading.
On my workstation in the studio it's not so noticeable, because that's a big beast with a RAID 1+0, 24GB RAM and 8 Cores. But grading in the field, on a superfast Asus G73S with 8GB RAM, it's unusable on even the first adjustment. Using any slider causes massive delay.
@Matthew - that's a great tip, I'll check it out.
It's unusable on this machine. Even trying to adjust the slider for Cache in preferences causing a major 'not responding' hang which can be interrupted by a Ctrl-Alt-Del. The behaviour continues in Beta 9 too. It's obviously some major incompatibility with my laptop. How can we track it down?
Paul please send log files from an instance where RCX goes into that not responding state to redcinex at red dot com
Today I upgraded to V9 and did a hardware restart and behaviour has gone back to normal. Sliders are usable and everything works as it should. Note that the behaviour didn't improve after the upgrade, only after the hardware restart. I reckon it is some kind of cache issue. If it re-occurs I'll set the program to verbose logging and see what it generates.
| « Previous Thread | Next Thread » |