-
CC 2014 RAM Previews take too long to Start processing
CC 2014 RAM Previews: On my old AE CS5 (this same exact PC system), once I hit the RAM preview button, I could see the things moving (green dots over the footage) almost immediately.
In my new CC 2014 however, RAM Preview takes its sweet time before even the first dot starts moving (but after that, it processes with reasonable speed.)
So there’s a delay of, I observe, about 10-15 seconds between the time I’m clicking on RAM Preview button, and the time AE CC 2014 seemingly starts crunching the numbers.
Why was CS5 faster?
Since I think I have exact same settings in CS5 vs CC 2014, it is strange to experience such long delay.
In all other aspects, CC 2014 seems actually livelier than CS5, but not with RAM Previews. What am I doing wrong?
-
14 Replies
-
Show a screenshot of your Memory & Multiprocessing preferences.
What operating system?
———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
After Effects product manager and curmudgeon
After Effects team blog
——————————————————————————————————— -
OS: Win 7 x64, CPU i7 970 @ 3.2GHz, Memory: 24GB, GPU: NVIDIA GeForce GTX 470
AE CC 2014 settings:
-
What happens if you mute audio in the Preview panel? (This question is getting at a possible problem in how audio is cached first before the video RAM preview begins.)
Does this occur with all compositions or just with compositions using expressions? (This question is getting at a possible problem in how expressions are pre-calculated when building a RAM preview.)
———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
After Effects product manager and curmudgeon
After Effects team blog
——————————————————————————————————— -
Wow. It absolutely was audio. Audio Muted, the CC 2014’s RAM Previews now start as fast as CS5’s (alas that old one did not seem to care about audio caching, but whatever works!)
About the settings I posted (please see snapshot in the previous post). Is it beneficial to have Render Multiple Frames Simultaneously checked for RAM Preview or not? (right now I have it only for Render Queue, which again I’m not sure is it a good idea or not… some say it actually may introduce problems or even be slower than linear frame-by-frame processing – what do you think?)
-
> Is it beneficial to have Render Multiple Frames Simultaneously checked for RAM Preview or not?
The reason that it’s an option is that there is no right answer for all circumstances.
Try it on. Try it off. Use what works best for you under a given set of circumstances.
———————————————————————————————————
Todd Kopriva, Adobe Systems Incorporated
After Effects product manager and curmudgeon
After Effects team blog
——————————————————————————————————— -
Looking at the settings, I have a followup question: I’d read that it’s normally
best to leave at least a couple of cores/threads reserved for other applications,
but Alex has that set to zero. What effect might this have in practice, ie. with
reserved CPUs = 0? Also, I see at the bottom it states the actual no. of CPUs
which will be used is thre – how is this number derived? I’d have thought with an
i7 970 it would still work ok with 4 or even 5 cores, leaving 1 for other tasks.Or are these both akin to the RAM Preview checkbox, ie. the best settings varies
between scenes, etc.?Ian.
——–
SGI Guru -
[Ian Mapleson] “What effect might this have in practice, ie. with
reserved CPUs = 0?”If you have enough RAM to feed all those CPUs, it can lead to overscheduled processors [link], which in turn leads to slower renders. In this case, you’d actually get faster renders by leaving a little capacity unused than you would by overusing what capacity you have.
Horrible car analogy: it’s like stomping on the gas pedal when your car is stuck in the mud. The wheels are spinning, but the car’s not going anywhere.
Remember, the goal is the fastest render (getting out of the mud quicker), not highest resource utilization (engine RPMs).
[Ian Mapleson] “I see at the bottom it states the actual no. of CPUs which will be used is thre – how is this number derived? I’d have thought with an i7 970 it would still work ok with 4 or even 5 cores, leaving 1 for other tasks.”
This depends on your available RAM and minimum RAM allocation. To use 4 cores with a minimum allocation of 4 GB per background CPU, you need at least 16 GB of RAM available to Ae.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Hey Walter, you wrote:
>>To use 4 cores with a minimum allocation of 4 GB per background CPU, you need at least 16 GB of RAM available to Ae.
So in my screen cap above there’s 18GB available to AE, and 4GB allocated per CPU – shouldn’t it then utilize 4 cores?
Yet it still says 3….
-
[Alex Zvyk] “So in my screen cap above there’s 18GB available to AE, and 4GB allocated per CPU – shouldn’t it then utilize 4 cores? Yet it still says 3….”
Not if that 18GB of RAM wasn’t available to Ae when it started multiprocessing.
These RAM preferences control how much RAM Ae will ask for. They do not guarantee that RAM for Ae because they do not control RAM usage of the OS and other applications.
If you close Ae, quit all your open apps, and then relaunch Ae once everything else has shut down, you may have enough free RAM to get that fourth core going.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Thanks Walter, this is very helpful.
Happy New Year!
Reply to this Discussion! Login or Sign Up