Puget System benchmark stops mid test (After Effects 18.12.1)

Report · Aug 01, 2021

Hi there,

I've bought a new Latop (Ryzen 5800H, onboard graphics, and Geforce GTX 1650) and tried running the Puget Benchmark Test with Adobe AE 18.2.1 (I read before, that the test doesn't work with 18.4 at all).

Right at the beginning I get error messages, but the test succeeds ("Couldn't rename projekt").

Mid test during the Cloud Lightning Project, I get this error message (picture), when I click ok, nothing happens, the test doesn't stop, nor does is cancel itself, or something like that.

What could be the problem?

p.s.: On my older (intel i7, GTX 1050ti) system, I had no such issue, except, that the Benchmark ran for hours (and not for the 15-30 min) and had to be stopped by me.

Report · Aug 01, 2021

It's hard to say. I get a similar error on one of the full resolution ram preview tests. 72 out of 100 frames and then the test fails. I don't have any luck with the test but I can get the comps open, run previews on all of them and render all of them. The only thing that does not seem to work is the automation. I would check with the developers. The code needs to be improved so that a ram preview that stops when the memory gets full does not foul up the whole test.

Here are the results of the test I ran on the most basic M1 Mac Mini*. Pretty darn impressive for an under $700 computer with an external $100 SSD used for the creative cloud files and all the storage.

I'll have to check render times on my other machines and see if I can see any from other systems for comparison.

* The "Drag & Drop here..." area is buggy and should not be used to share images. Please use the toolbar or just drag your images to the reply field.

Report · Oct 12, 2021

I for one, had to change the language settings of my OS and Adobe Programs to English. Than all ran till the end of the test.

Report · Mar 17, 2024

I had a similar problem with the benchmark.

It struggles a lot with 16GB or less memory. If you have 24GB or more and you still see the error, it's probably something else. Try turning on logging before running the benchmark and try again, review the output of the log at the end of the file and share the error messages there

https://community.adobe.com/t5/after-effects-bugs/puget-benchmark-for-after-effects-24-0-0-does-not-...