Skip to main content
Participant
November 19, 2023
Answered

After Effects Sluggish Preview

  • November 19, 2023
  • 1 reply
  • 361 views

Hi,

I'm running on a Windows PC with a sluggish preview for a few clip shots (120 fps).  Any ideas on how to fix that?   and     Is it helpful to install CUDA TOOL KIT?

 

Things I have done so far but no result:

1. Updated the latest version of the GPU driver.

2. I have tried different Video Rendering modes (MGA CUDA and OPEN CL)

3. Adaptive Resolution setting 1/8 ===>  Texture memory : 15 Gb

4. Empty the disk case / clean media database, and cash 

5. Tired of different playback preview spaces, Numb, Alt.... etc

6. Max Disk cache size 200Mb

7. Memory reserved for AE 58 Gb

8. Some minor changes in NVIDIA CONTRol PANEL for AE (not for Global setting)

 

PC SPEC:

CPU I9-11900 K

RAM 64GB DDR5

GPU RTX3090

Drive 2 TB SSD with 1 TB free Space

(Using HDMI, not Disport)

 

This topic has been closed for replies.
Correct answer Sam8888

Thanks, Rick.

It was my setting in Nvidia Control panel. But thanks for mentioning the Display refresh rate. 

1 reply

Community Expert
November 19, 2023

Try skipping a couple of frames. You can find the setting in the Preview Panel. That would make the rendered frame rate faster than a feature film or television in PAL countries. Your computer's display refresh rate is probably only 60 fps. The human eye and brain will see smooth motion in as few as 12 to 18 fps, and the purpose of a RAM preview in a compositing and effects app is to see the blocking, timing, and composition. 

 

YouTube, Vimeo, and social media are going to throttle the frame rate to 30 for most viewers to save bandwidth anyway. Unless you are slowing things down in playback, there's not much of a reason to work in a 120 fps comp.

Sam8888AuthorCorrect answer
Participant
November 20, 2023

Thanks, Rick.

It was my setting in Nvidia Control panel. But thanks for mentioning the Display refresh rate. 

Participant
January 2, 2024

Hello, Sam,

I am currently experiencing a problem similar to yours (which has appeared after an NVIDIA driver installation , so I suppose the problem could lie somewhere here, although I have tried different workarounds as well). Could I ask you which settings you customised?