Skip to main content
Participant
September 15, 2025
Question

Preview slow - updated mister Horse plugin and AE - updated sequoia (15.6.1)

  • September 15, 2025
  • 2 replies
  • 278 views

After my updated M4 machine with updated AE apps and MH . The play back is slow in intial time and after cache , its work fine . Intial time its working very slow and memory is not up to mark ( machine has 32 GB ) . Please suggest any log file needed . Now working with adaptive resolution and quarter .

2 replies

ToolfarmJP
Community Expert
Community Expert
September 16, 2025

Would you clear all the cache data?

 

Participant
September 16, 2025

Clearing the cache causes the problem to occur again during the next initial preview.

nishu_kush
Legend
September 15, 2025

Hi Manesh,

 

After Effects takes some time to generate a cache for the frames, which is expected. Could you help me understand the issue better? Is it caching frames slower than it was before? Is it happening only when you use the plug-in? Can you try disabling the plug-ins (Effects > Manage Effects > disable all third-party plug-ins)?

Let me know how it goes.


Thanks,
Nishu

Participant
September 16, 2025
While using Adobe After Effects with the Mister Horse plugin, it has been observed that playback is slow during the initial preview. The issue appears specifically when FX effects are enabled. Disabling FX results in normal playback without any lag or delay.
The behavior is as follows:
During the first preview, After Effects runs slower than expected, showing noticeable lag.
After the first preview is completed, subsequent playbacks run smoothly without delays.
Clearing the cache causes the problem to occur again during the next initial preview.
 
This suggests that the issue is related to how After Effects processes and caches effects during the first playback session, particularly when using the Mister Horse plugin.
nishu_kush
Legend
September 16, 2025

After Effects preview works differently from an NLE like Premiere Pro. It needs to first store all the frames in the cache before it can show the real-time preview. So, in the first run, it'll build the cache (indicated by the green line) and then show you the preview. Here are more details: https://adobe.ly/4nyhKAz

As per your description, the behavior seems as expected. However, it would be helpful to understand what's going on if you could share a screen recording of the issue.

Let us know.


Thanks,
Nishu