• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Puget Benchmark for After Effects 24.0.0 does not complete on Intel Arc A770 16GB GPU

Community Beginner ,
Oct 13, 2023 Oct 13, 2023

Copy link to clipboard

Copied

Puget Benchmark 0.96.0 for After Effects 24.0.0 (Build 55) benchmark does not complete because it says frames have dropped: "Error only 53 frames have played out of the total 100"

I have 16GB 4800MHz DDR5 RAM.

12GB allocated to After Effects and 4GB for the Operating System

Windows 11 Pro  22621.2428

Intel Arc WHQL Driver 31.0.101.4887

I am able to run all of the rest of the Puget Benchmarks except After Effects which always fails due to these errors.

Bug Won't fix
TOPICS
Compositing and VFX , Crash , Dynamic link , Expressions , Import and export , Performance , Scripting , SDK , Troubleshooting , UI and UX , Workflow

Views

517

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Oct 30, 2023 Oct 30, 2023

I have finally been able to complete the Benchmark with 16GB of RAM.

Adobe released an update for After Effects 24.0.1 (build 2) and it worked with this.

With plugin: PugetBench for After Effects 0.96.0

 

What else I changed...

I allocated more RAM for the Adobe After Effects application: 13 GB

RAM reserved for other applications: 3GB

Intel Arc Driver: 31.0.101.4887

Current version of Windows 11 as of todays date: 22621.2506

 

I also set the Windows Operating System Virtual Memory to System Managed sized

...

Votes

Translate

Translate

correct answers 1 Pinned Reply

Adobe Employee , Oct 13, 2023 Oct 13, 2023

The error dialog is coming from the Puget Benchmark, indicating there isn't enough memory on your system to preview the entire composition. 16GB RAM is the minimum to use AE these days but that does not gurantee complex compositions can be fully previewed. 

Status Won't fix

Votes

Translate

Translate
6 Comments
Adobe Employee ,
Oct 13, 2023 Oct 13, 2023

Copy link to clipboard

Copied

The error dialog is coming from the Puget Benchmark, indicating there isn't enough memory on your system to preview the entire composition. 16GB RAM is the minimum to use AE these days but that does not gurantee complex compositions can be fully previewed. 

Status Won't fix

Votes

Translate

Translate

Report

Report
Community Beginner ,
Oct 13, 2023 Oct 13, 2023

Copy link to clipboard

Copied

I have just retested 23.6 and 24 with logging enabled and can confirm this error is due the memory being exceeded.

I set the minimum 12 GB it required, but it isn't reclaiming the memory fast enough when rendering the next video.

 

C:\Users\user\AppData\Roaming\Adobe\After Effects\24.0\logs\After Effects Log.txt

C:\Users\user\AppData\Roaming\Adobe\After Effects\23.6\logs\After Effects Log.txt

 

Ticks = 173532 <5836> <U> <5> Preview range is exhausted because purgeable memory has exhausted. Current memory usage is 11.99 GB
Ticks = 173532 <5836> <U> <5> Preview range is exhausted because purgeable memory has exhausted. Current memory usage is 11.99 GB
Ticks = 173532 <14116> <U> <5> Preview range is exhausted because purgeable memory has exhausted. Current memory usage is 11.99 GB
Ticks = 173532 <14116> <U> <5> Preview range is exhausted because purgeable memory has exhausted. Current memory usage is 11.99 GB
Ticks = 173532 <14116> <RenderTaskManager> <5> Multithreaded render report
---------------------------
Total duration: 22.357 seconds
Render threads used: 4
Frames rendered: 59
Frame render avg time(per thread): 0.883767 seconds
Total frames per second: 2.63899
Total per - thread time in big mutex: 0 seconds
Render context creation overhead time(per thread): 2.74e-05 seconds
Starting concurrency: 2
Max allowed concurrency: 20
Thread - safe effects used :
ADBE Box Blur2
ADBE CurvesCustom
ADBE Drop Shadow
ADBE Exposure2
ADBE Fractal Noise
ADBE Glo2
ADBE Lightning 2
ADBE Set Matte3
ADBE Solid Composite
CC Composite
Non-thread-safe effects used :
<none>

Ticks = 174360 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES script:[try { readFile('C:/Users/tauhe/Documents','2023-10-13-15-51','te]...
Ticks = 174360 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES Done, Success:[C:/Users/tauhe/Documents/PugetBench/After Effects/2023-10-13-15-]...
Ticks = 175360 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES script:[try { readFile('C:/Users/tauhe/Documents','2023-10-13-15-51','te]...
Ticks = 175360 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES Done, Success:[C:/Users/tauhe/Documents/PugetBench/After Effects/2023-10-13-15-]...
Ticks = 176375 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES script:[try { readFile('C:/Users/tauhe/Documents','2023-10-13-15-51','te]...
Ticks = 176375 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES Done, Success:[{"fps":"Error: Only 59 frames played out of the total 100","time]...
Ticks = 176375 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES script:[try { writeFile('[ 15:54:2 ] {"fps":"Error: Only 59 frames playe]...
Ticks = 176375 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES Done, Success:[C:\\Users\\tauhe\\Documents\\PugetBench\\After Effects\\2023-10-]...
Ticks = 176375 <15160> <ALOG> <5> Scripting EvalScriptViaNativeES script:[try { showAlert('{"fps":"Error: Only 59 frames played out of the]...

Votes

Translate

Translate

Report

Report
Community Expert ,
Oct 13, 2023 Oct 13, 2023

Copy link to clipboard

Copied

I am also getting errors on an M2 Max MacBook Pro. My failure is the warp stabilizer is failing. I ran Warp Stabilizer and Camera Tracker on 24.0  Build 55, and AE Beta 24.1 Build 50 with the same results. Either the Analysis server fails to launch, or if it does launch, I get an endless loop analyzing the frames with messages like 3 seconds left, frame 43 of 100.

 

I'm preparing a detailed bug report.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 13, 2023 Oct 13, 2023

Copy link to clipboard

Copied

@Rick Gerard That sounds like a third-party plugin that is interferring with the warp stabilizer/camera tracker background process starting up. Take a look in the mediacore plugins folder and see what plugins you have there. 

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 13, 2023 Oct 13, 2023

Copy link to clipboard

Copied

@TAUHEEDUL That all looks correct. You've run out of memory because to hold all the rendered frames and the layer caches for that comp in memory is taking more memory than you have available. If you were able to drop to half or quarter resolution, it'd likely complete the preview. We are looking at ways to reduce memory usage for preview but for now, this simply looks like you need more memory to be able to complete the benchmark. 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Oct 30, 2023 Oct 30, 2023

Copy link to clipboard

Copied

LATEST

I have finally been able to complete the Benchmark with 16GB of RAM.

Adobe released an update for After Effects 24.0.1 (build 2) and it worked with this.

With plugin: PugetBench for After Effects 0.96.0

 

What else I changed...

I allocated more RAM for the Adobe After Effects application: 13 GB

RAM reserved for other applications: 3GB

Intel Arc Driver: 31.0.101.4887

Current version of Windows 11 as of todays date: 22621.2506

 

I also set the Windows Operating System Virtual Memory to System Managed sized and it allocated up to 11GB for the page file.

 

In addition, to free up more memory, I ran all automatic updates e.g. Windows Updates and Store Updates prior to running the Benchmark. I closed any unnecessary applications running in the System Tray.

 

Now when I run the test, the first run occassionally pauses around 80% and doesn't proceed further without displaying errors, but after I restart and re-run the test it actually completes.

 

I have validated this on both the reference Intel Arc A770 16GB and the Asrock Intel Arc A380 6GB cards.

 

The previous error reported continues to persist in the earlier version of After Effects 23.6.0 (Build 62) so there must have been some fixes in there in  After Effects 24.0.1 (build 2) for the Intel Arc cards.

Votes

Translate

Translate

Report

Report