Puget Systems print logo
Read this article at https://www.pugetsystems.com/guides/1519
Article Thumbnail

PugetBench for Premiere Pro

Written on December 11, 2019 by Matt Bach

At Puget Systems, one of our primary goals is to provide fast and reliable workstations that are perfectly tailored to each customer's unique workflow. As a part of this, we publish an ongoing series of hardware articles for Premiere Pro - as well as numerous other software packages - in order to discover what hardware configurations are optimal for these specific applications.

However, while this ensures that we are selling the right hardware, it does not give our customers a great idea of how much faster a new workstation might be compared to their existing system. In addition, with the amount of hardware that is currently available, it is impossible for us to test everything on our own, so we want to provide tools for other hardware reviewers to perform real world benchmarking in professional applications like Premiere Pro.

To address both of these issues, we are making our Premiere Pro benchmark available for download so that anyone can can perform the same testing we do in our hardware articles. Even better, this benchmark is compatible with both Windows and Mac-based systems which allows for cross-platform performance comparisons.

Step 1: Get the Plugin

Find it on Adobe Exchange

Free version is suitable for personal use.
Results upload to the PugetBench online database.

Step 2: Download Test Assets

Download Files (6.5GB)

Includes assets for Standard and
Extended test presets

Commercial Edition

More Information

For commercial use - includes optional uploading of results, email support, automation, and logging.
Feature Free Edition Commercial Edition
Benchmark Scores
PugetBench Online Database
Windows 10 Support
MacOS Support
CLI Automation
(Windows only)
.CSV Logging
Licensed for Commercial Use
Support Community Email
License None More Information
Be sure to check out the full list of benchmarks we have available!

PugetBench for Premiere Pro

System Requirements

  • Adobe Premiere Pro 2021/2020 (support for 2019 removed in version 0.86 BETA)
  • 32GB of memory
  • 4GB of GPU VRAM
  • 100GB free space on your drive
  • Compatible with both Windows 10 and MacOS
  • Premiere Pro/OS language must be set to English
  • Must be run from a local drive (no network attached storage)

Note that this benchmark is still in BETA. Plug-ins and customized preferences in particular may prevent the benchmark from running properly. If you run into any issues, we recommend resetting your preferences either by following Adobe's guide or by using our Adobe CC Preference Backup/Restore/Clear utility (Windows only).

How to run the benchmark

  1. Add the benchmark plugin to Creative Cloud from the Adobe Exchange
  2. Follow the directions to install the plugin on your system
  3. Download test assets
  4. Launch Premiere Pro and open the "Benchmark_Project.prproj" project file for Premiere Pro 2020 (14.x), or "Benchmark_Project_15.prproj" project file for Premiere Pro 2021 (15.x)
  5. Start the plugin from "Window->Extensions->PugetBench for Premiere Pro"
  6. Configure any settings you want to change (especially if you have a commercial license).
  7. Run the benchmark!

While a there are no configuration options in Premiere Pro that need to be set, there are a few things you need to do before running the benchmark depending on your OS.

  • Windows: make sure that the program window is in the upper-right quadrant of the Premiere Pro application. We need to use an external app that clicks in this are in order to change the playback resolution.
  • MacOS: you need to go to "Security & Privacy" and add Premiere Pro to the Accessibility list. In addition, a few seconds or minutes after the benchmark starts, a popup will come up that asks you to allow Premiere Pro access System Events. Again, this is so that we can change the playback resolution (via the top menu bar).

When the benchmark is complete, it will give you an "Overall Score" and upload the results to to our online database (unless told not to with the commercial version). From the uploaded results, you can view the sub-scores and individual test results.


If you have any issues with the benchmark not properly running, first verify that your system meets the System Requirements and that the version of Premiere Pro you are using is supported. If there are no issues with your system or software, there are a number of troubleshooting steps you can try:

  • Make sure you are following each step listed in the How to run the benchmark section
  • Do not attempt to use the system while the benchmark is running. Defocusing the application window can break the benchmark in many situations.
  • If you are on MacOS and have renamed your drive, the benchmark will not be able to get your system specs. The only work-around at the moment is to rename your drive back to "Macintosh HD", or you can continue to run the benchmark without it being able to pull specs.
  • Some MacOS systems will not open the main benchmark project properly, complaining of an unsupported codec. If this happens, make a new empty Premiere Pro project and save it over the "Benchmark_Project_15.prproj" project file.
  • Clear the application preferences and reset them to default.​​​​​​ by either using Adobe's guide or our Adobe CC Preference Backup/Restore/Clear utility (Windows only).
  • Disable Windows Defender or any real-time virus scanning programs when you run the benchmark.
  • Ensure that your OS and Premiere Pro is set to English and that the path to the benchmark script does not have any special or non-English characters.
  • The benchmark does not work over an unmapped network drive (I.E. // Mapped drives should work, but we highly recommend having the benchmark on a local drive as storage performance can affect the results.
  • Re-download the benchmark and use a unzipping tool like 7zip to unzip the files rather than the tool that is built into your OS.
  • Uninstall and reinstall the benchmark plugin.

Lower than expected performance can be caused by a number of factors, but the most common are:

  • Outdated BIOS/drivers/software
  • Running background processes (Antivirus, Windows Updates, etc.)
  • Windows power profile (High Performance is recommended for the best results)
  • Adobe application settings are not correct (GPU acceleration not enabled, etc.)

If you continue to have issues, we recommend posting in the comment section below - ideally with a screenshot of the problem and a copy of any log files that are generated by the benchmark.

What is tested?

Our Premiere Pro benchmark looks at both live playback and export performance with a wide range of codecs at 4K and 8K resolutions. In addition, there are dedicated "Heavy GPU Effects" and "Heavy CPU Effects" sequences that are designed to individually stress the GPU and CPU beyond what a typical Premiere Pro user will do.

Our test media consists of the following resolutions and codecs:

Test Media (59.94 FPS)
4K H.264 150mbps 8-bit (59.94FPS) 4K ProRes 422
4K RED 8K H.265 100Mbps

For each type of test media, we look at four test sequences:

  1. Standard - Two 59.94FPS clips in series with a Lumetri Color effect applied
  2. 2x Forward - Four 59.94FPS clips with Lumetri color set to 200% speed in a 119.88FPS sequence to simulate performance when playing at 2x speed.
  3. 4x Forward - Eight 59.94FPS clips with Lumetri color set to 400% speed in a 239.76FPS sequence to simulate performance when playing at 4x speed.
  4. MultiCam - multiple clips across four-six tracks in a multicam sequence. Playback is tested in "Multi-Camera" display mode.

These tests are all used for live playback performance testing at Full playback resolution. The Standard sequence is also used to test export performance using the "Youtube 2160p 4K Ultra HD" preset (H.264, 4K, 40mbps) as well as exporting to 4K ProRes 422HQ 8-bpc.

In addition, we have a "Heavy GPU Effects" sequence using:

  • Twp ProRes 422 clips in series with a Cross Dissolve between each
  • Advanced effects: Lumetri Color, Ultra Key, Sharpen, Gaussian Blur, Basic 3D, Directional Blur, and VR Digital Glitch.
  • Extreme effects: Lumetri Color, Ultra Key, Sharpen, Gaussian Blur, Basic 3D, Directional Blur, VR Digital Glitch, and VR De-Noise.
  • Performance is measured by exporting to ProRes 422HQ.

and a "CPU Heavy Effects" sequence using:

  • Two ProRes 422 clips in series
  • Advanced effects: Text layer with keyframed position and scale, and Lens Flare.
  • Extreme Effects: Text layer with keyframed position and scale, Dust & Scratches, Noise, and Lens Flare.
  • Performance is measured by exporting to ProRes 422HQ.

How does the scoring work?

The scoring system used in our benchmark is based on the performance relative to a reference system with the following specifications:

  • AMD Ryzen 5900X 12 Core
  • NVIDIA GeForce RTX 3080 10GB
  • 64GB of RAM
  • Samsung 960 Pro 1TB
  • Windows 10 Pro
  • Adobe Premiere Pro 2020 (ver. 14.8)

The performance in FPS for each individual task is compared to the reference result and used to calculate the Live Playback, Export, GPU, and Effects scores. For example, for these sub-scores, a score of "100" would match the reference system, while a score of "80" would indicate performance roughly equal to 80% of the reference system.

The Live Playback and Export scores are all combined into the "Standard", and "Extended" Overall scores depending on the benchmark preset you chose. Here, we multiply the scores by 10 in order to make sure the Overall scores are larger than the sub-scores (since bigger number = more important). Due to this, a score of "1000" would match the reference system, while a score of "800" would indicate performance roughly equal to 80% of the reference system.

The GPU Score is the average of the results for the GPU Effects tests as well as the H.264 export tests.

Update Log

Version 0.95.1 BETA

  • Added project files and CLI support for Premiere Pro 2021 (15.x)
  • In order to run the benchmark, you must have both the latest plugin version, and download the latest test assets so that the project files for Premiere Pro 2021 are present.

Version 0.95 BETA (Major Update)

  • Major update - Results cannot be compared to previous benchmark versions
  • Requires new project files due to significant changes to what is tested
  • Added additional failsafes for when gathering of system specs fails
  • Added spec gathering support for Apple M1 systems
  • In some cases, playback can report more dropped frames than exist in the sequence. When this happens, the playback FPS will be reported as "0"
  • Standard and Extended tests adjusted. Old test sets were too easy given recent hardware/application updates, resulting in many of the live playback tests in particular running at full FPS on most systems
  • Test changes also significantly reduced the amount of time it takes to run the benchmark
  • Scoring changed to be relative to a reference system (AMD Ryzen 5900X w/ GeForce RTX 3080)
  • Test changes:
    • Dropped half resolution Live Playback tests
    • Added 2x and 4x speed forward playback tests
    • Increased ProRes multicam test to 6 streams
    • Shortened all test sequences from 30 sec to 20 sec in length
    • Export tests now use in/out points so that we can shorten some tests (CPU effects test primarily)
    • H.264 export tests now count towards the GPU score since it uses GPU encoding by default
    • CPU & GPU Effects sequences no longer do live playback tests, and only export to ProRes. Live Playback results are often not consistent with this focused of a load, and this change should make the scoring more accurate
    • Shortened CPU Effects export test to 1/3 the length since this test can take a long time
    • GPU/CPU effects tests now have their own "Effects" category and sub-score
    • Overall score is now the average of the "Live Playback", "Export", and "Effects" sub-scores
    • Scoring now based on performance relative to a reference system (Ryzen 5900X w/ RTX 3080) rather than relative to the media FPS
    • Dropping 23.976 FPS media from Enhanced Extended tests. Extended will now only adds sequences with 8K 59.94FPS H.265 and R3D media
  • "Custom" preset is now a licensed feature and allows you to select individual tests to run. Custom preset can still be set via the CLI utility, but requires you to manually configure and save the settings at least once before running the benchmark from the command line.

Version 0.92 BETA

  • Moved to using node-wmi to gather system specs on Windows systems. This should be significantly faster and more reliable than the previous command line method
  • Added GPU driver and motherboard BIOS to the system specs for Windows systems
  • CLI utility now updates the Pr preferences so that workspaces are imported when opening a project (default behavior was changed in Pr 14.3.1)
  • Misc bug fixes

Version 0.91 BETA

  • Improved system spec gathering reliability
  • System specs on MacOS now gather properly even if the system drive's name has been changed from the default "Macintosh HD"

Version 0.9 BETA (Major Update)

  • Results are now uploaded to our online database. This is required for the free version, but opt-in if you have a commercial license.
  • Removed the temporary .csv logging from the free version now that the full results can be viewed on our benchmark listing page.
  • Complete plugin UI revamp. Added status bar/text, and improved the configuration options.
  • Improved method used to gather system specs. This should break less often on unusual or older system configurations.
  • License validation moved from the CLI utility to the plugin itself.
  • Added the ability to do a "Custom" test which does the same tests as normal, only on whatever sequences are on the root-level of the currently opened project.
  • Added ability to set the location for any disk-based tests (exporting).
  • Added tooltips for the various settings that can now be configured.
  • Status logs and configuration settings moved to "~Documents⧵PugetBench⧵Premiere Pro⧵TIMESTAMP" since we cannot log directly to the plugin folder.
  • Dropped 8K H.265 tests. This test was simply too difficult for most systems and resulted in Premiere Pro hanging more often than not.
  • Dropped ability to run tests in individual codecs. The intention is that the "Custom" test type will replace this.
  • Improved CPU and GPU effects test. Added "Advanced" and "Extreme" tests to differentiate between what someone might be doing in their own projects versus a worst-case scenario. Also dropped exporting to H.264 for these tests since we want to focus on the system's performance for processing CPU and GPU effects
  • Scoring has been adjusted based on the test changes. Due to this, the Overall Score will not be consistent with previous versions.
  • General bug fixes and stability improvements.

Version 0.88 BETA

  • Slight change in benchmark plugin folder name. Be sure to uninstall any existing "PugetBench for Premiere Pro" plugins before install the new 0.88 version.
  • Fixed issue where the benchmark would not run due to a change in the API when using confirm boxes.
  • Added "GPU Score" that is the average of the results from the "GPU Effects" tests.

Version 0.86 BETA

  • Dropped the "Benchmark Results" score screen due to Premiere Pro 2020 breaking MGRT scripting functionality
  • Adding back .csv log file support until we can get the "Benchmark Results" screen working
  • No longer generating the test sequences on the fly - switching to pre-made projects for each test codec. This greatly increases the overall stability of the benchmark
  • Due to using pre-made projects, Premiere Pro 2019 is no longer supported
  • Improved system information gathering methods. This should make it much more reliable on MacOS
  • Added option to continue the benchmark if the system information gathering does fail for any reason
  • Miscellaneous bug fixes and improvements

Version 0.8 BETA

  • Renamed benchmark to "PugetBench for Premiere Pro"
  • Added support for Premiere Pro 2020
  • Dropping the 29.97 FPS CPU and GPU effects tests. These are already somewhat artifical, so no reason to run them at both 29.97 and 59.94 FPS. This means that the Extended test scores will be slightly different than previous versions, but it shouldn't be by a huge amount
  • There is now a "Benchmark Results" screen that comes up at the end of the benchmark that displays a bunch of useful information including: benchmark version, cores, results for each individual test, and system information like CPU, RAM, OS, GPU, and Premiere Pro version
  • The benchmark also makes a PNG of the "Benchmark Results" screen for easy sharing
  • Removed .csv log file support in the free edition (log files will be a feature in the commercial use version)
  • Removed "start" .exe applications (automation will be a feature in the commercial use version)
  • More code to ensure consistency between benchmark runs
  • Miscellaneous bug fixes and improvements

Version 0.3 BETA

  • Replaced H.264 media with footage straight from a Panasonic GH5 (Thanks Neil Purcell!)
  • Replaced "Quick" preset with "Standard" preset. Changed tested media to 59.94FPS instead of 29.97FPS.
    • This was done with the intention of having a benchmark preset that is geared towards measuring the overall performance of a system in as little time as possible.
  • Separated media files into two groups: a "Standard" set and a "Full" set to make the download much more manageable for people just doing the Standard preset.
  • Due to the change in the test media, the overall scores are not interchangeable with previous benchmark versions

Version 0.2 BETA

  • First release.

Looking for an Premiere Pro Workstation?

Puget Systems offers a range of poweful and reliable systems that are tailor-made for your unique workflow.

Configure a System!

Labs Consultation Service

Our Labs team is available to provide in-depth hardware recommendations based on your workflow.

Find Out More!
Tags: Premiere Pro, Benchmark, Public, Download

Can't wait for your review for Ryzen7/9 and 3950X in future, from other reviews I saw- looks like the 3900X will be your favorite CPU- better then 9900K and even challenging 7980XE/9980XE even in ADOBE :-).

Posted on 2019-07-09 07:31:19
Spale Max

Results are completely off.
I mean 9700k is faster than 9900k in your review, is there anything else to add?

Posted on 2019-07-09 16:06:59

IDK, here another test in Pro apps- 3900X competing with 9980XE and 2950X!
So the 3950X will completely destroy Intels X299 linup in pro apps.

Posted on 2019-07-10 08:44:20

Adobe software isn't well optimized to use multiple threads and loves single threaded performance. There are plenty of lightly threaded workloads out there that actually benefit from disabling Hyper Threading(a 9700K is just a 9900K without HT) since it increases processing latency and you only start to see benefits from Hyper Threading when you have more simultaneous threads. Games, which also often aren't well optimized to use multiple threads, sometimes perform better on a 9700K(or even just a 9900K with HT manually disabled) compared to a 9900K.

Posted on 2019-07-12 13:32:34
Yariv Nachshon

A new review with Old CPUs ? Seems like the new Ryzen is all what people care for.

Posted on 2019-07-09 08:53:39

Do you mean the sample results? This is just the benchmark information/download page, not a hardware review. Those are just there to give people an idea of normal scores until we have articles published using this benchmark (like our Ryzen 3rd generation first look articles that are up)

Posted on 2019-07-09 15:32:08
Yariv Nachshon

Yes. i understand it but there is no option for it in the sample results list at all :-(
Even mentioning is with a score of zero will make it more interesting to re-examine :-)


Posted on 2019-07-09 16:59:42

Would it be possible to add a 1080p files test to the benchmark?
for slightly more modest configs...

Posted on 2019-07-10 07:38:49

We have gone back and forth on that, and ended up deciding against it for a couple of reasons:
1) 1080p is just too easy for the kinds of systems we are typically testing ourselves. If anything can do our playback tests at full FPS, then there is no measurable difference beyond exporting
2) The relative difference between hardware tends to be very similar regardless of whether you are testing 1080p or 4K media. So even if you do just work with 1080p footage, the 4K results are still pretty valid (even if they don't tell you exactly what FPS you could expect)
3) We already have way too many tests

In many ways, #3 is the main limiting factor. Nothing is really stopping us from adding 1080p, but it comes down to benchmark time vs reward.

Posted on 2019-07-10 16:48:58

Thank you for the explanation!

Posted on 2019-07-11 01:31:43

1080 Ti?

Posted on 2019-07-10 07:56:43

Great article, but where is the Ryzen 3900x Premiere Pro review? :D jk.

Posted on 2019-07-10 14:16:41
Matthew Fitz

Very generous of you to share these publicly. I am keenly interested in when the light-room benchmark becomes a public beta also as was previously mentioned. Eagerly waiting to see how Ryzen 3000 takes to Photoshop and Light-room.

Posted on 2019-07-11 02:09:18
Mark Harris

Thanks for sharing this!

Posted on 2019-07-11 19:22:49

Just downloaded it and was able to restore the archive file. When opening the Premiere project it seems there is a missing .psd file? Benchmark Setup.psd

Posted on 2019-07-12 19:03:37

Are you on Mac or PC? So far, it seems like PC can unzip it just fine , which is very odd.

Fortunately, that PSD isn't really necessary. It is just the setup instructions which are listed on this page on the "How to run the benchmark" section. Or just look at https://www.pugetsystems.co... . Delete it, mark as offline, whatever. It won't affect the benchmark at all.

Posted on 2019-07-12 19:10:07

On a mac. , I'll give it a run through, thanks.

Posted on 2019-07-12 19:28:11

It looks like the restore is missing more files than I thought. https://uploads.disquscdn.c... https://uploads.disquscdn.c...

Posted on 2019-07-12 19:41:57

the bottom list is what was unzipped.

Posted on 2019-07-12 19:42:20

So weird that it works fine on PC... I already have a plan in place to split up the zip across two files since most people aren't going to actually run the full benchmark. Hopefully that will fix it.

I'm actually out of the office right now, but I'll try to get a new zip file(s) uploaded early next week.

Posted on 2019-07-12 20:03:41

Thanks, I just wanted to let you all know, have a great weekend!

Posted on 2019-07-12 20:06:35
Ann Bens


Unzipping the movie files gives a Headers Error

Resulting in not loading up in Pr. during the Quick test

Posted on 2019-07-12 22:20:36
Scott Moore

I've tried running the benchmark several times (and selecting several different options) and nothing seems to work. I get the "copying media" notification and then nothing else happens. Logs seem to point to an error with copying some of the media https://uploads.disquscdn.c...

Posted on 2019-07-16 21:24:45

We're uploading a new set of benchmark files right now since it looks like there was some corruption in the original zip file. Check the download links in a few hours - that should resolve the issue.

Posted on 2019-07-16 21:28:04
Scott Moore

Sweet, thanks Matt! will keep an eye out for it

Posted on 2019-07-16 21:43:39
Scott Moore

Hey Matt, got it working now!
I don't think the download/zip was my issue as the new download ran into the same "some media not copied" error.
I moved the project folder to my system drive, it was previously on my media drive which is a network drive, and that seemed to get it working correctly.
Not sure if that was in any of the instructions or not but might be helpful for problem solving going forward?

Posted on 2019-07-17 03:18:27

Oh, interesting, I didn't even think about network drives. It should work fine if it is mounted to a drive letter, although I'm not completely sure how it would handle it on Mac. We're mostly using the Premiere Pro SDK, and I'm not confident the file management in it can handle things like that.

Thanks for the heads up, I'll at the very least update the instructions to mention this!

Posted on 2019-07-17 16:34:34

WHe runnning 4k CinemaRaw Light in MC there's some Error retrieving Frame instances that would make Premiere crash. What could be the reason?

Posted on 2019-07-24 06:51:21

I have never seen that issue before. If you just manually import that footage and make a sequence, does the issue still occur? If it does, that means it is a problem with your system or Premiere Pro install, not the benchmark

Posted on 2019-07-24 17:10:25

Project cant be loaded even though I have CC 2019 v13.01 :(

Posted on 2019-07-24 15:05:16

There actually isn't anything in the benchmark project except the instructions (which are on this page as well). You can just make a new project with the same name in that folder and the benchmark should run just fine.

Posted on 2019-07-24 17:11:09
Daniel Toman

A standardized Premiere benchmark is something I've wanted for a long time, thank you! Planning to try it soon to measure the impact of various system upgrades. How will it handle OpenCL vs Metal vs CUDA vs Software Only rendering?

Posted on 2019-07-30 18:50:43

Right now, the benchmark automatically sets the Mercury Playback engine, so manually changing it won't affect anything. We have to do this since it will often default down to "Software Only" mode if you open the project with a different GPU than what the project was created with (which will be the case for most people). I believe the priority goes CUDA, OpenCL (since OpenCL is faster overall than Metal on Mac), Metal, then it errors if it can only do Software Only since some of the tests require CUDA/OpenCL/Metal.

In a future version, we may add a configuration .ini file where you can specific which you want to use for the times when you want to test this kind of thing, but on this initial version we are more concerned about it working at all and being accurate than anything else.

Posted on 2019-08-05 20:48:50

Can you elaborate more on the system used with the 9900K? Running the same with 64 GB of Ram and a 2070. Both of which you have articles stating anything more provides little performance gain. Numbers are good, but you are pulling 20% higher scores on all benchmarks. Are you overclocking the CPU, or pulling performance gains out any other way?

Posted on 2019-08-10 04:33:58

We don't overclock the CPU at all, and don't use overclocked video cards unless there is no other option (this is sometimes the case with AMD GPUs). Usually, it is one of three things that cause lower than expected performance in benchmarks:

1) You are using a different version of drivers, Windows updates, motherboard BIOS, or other software/firmware than we did
2) You have applications running in the background that is eating into performance (we do our testing on very "clean" OS installs)
3) You may be hitting thermal or power limits. Might be inadequate cooling for the CPU/GPU/motherboard, or your motherboard/PSU isn't able to maintain the power states necessary to keep the CPU at the highest Turbo Boost speeds that should be possible. That doesn't necessarily mean a bad mobo/PSU, but not all boards are created equally and some have better power management than others.

You might want to do a few synthetic CPU and GPU-specific benchmarks to make sure you are hitting the performance levels you should be. Geekbench is pretty good for CPU (download at https://www.geekbench.com/ and compare scores at https://browser.geekbench.c.... For the GPU, OctaneBench is great (download at https://render.otoy.com/oct... compare scores at https://render.otoy.com/oct.... Cinebench is also good if you want to look into CPU performance a bit more - they just don't have a result browser so you will need to find reviews that use it.

Posted on 2019-08-12 18:07:33

Much obliged on your input. I have run Cinebench, but run into the exact situation you describe finding similar systems for comparison. Will look into the other benchmarking applications you reference.

I suspect background apps may be robbing a bit of power. Will disable them and rerun with premiere set to high priority for a comparison to a “clean OS” or at least as clean as it can be without wiping my system.

Keep up the great work, it’s great to see you guys sharing so much info with the masses!

Posted on 2019-08-13 15:50:04
Jim Leonard

Hi Matt, I left a longer message on another thread, but wanted to ask you what encoding parameters you used when creating the h.264/h.265 files in the benchmark -- there's something wrong with them and they don't play smoothly on the Premiere timeline, even on a system with Intel quicksync extensions working. When I make a new timeline with them, they play via software only, and don't play smoothly. If I re-encode them with identical size/framerate/depth/bitrate using Adobe Media Encoder, the resulting output is played via hardware decoding and plays fine. I'm using an I7-8700k with two GTX 1080 TIs.

Because premiere can't play these media files using hardware decoding, I'm not sure they're fair to use in the benchmark. Even if you wanted the benchmark to be software decoding only, there's something else wrong; they play choppy even though CPU usage is barely above 15%, which leads me to believe that the Long GOP is simply too long and not representative of footage produced by actual cameras. Looking forward to your thoughts on this.

Posted on 2019-08-14 02:11:13
Chris Holzmann

Hello! I always get
"Failed to install, status = -403!"
when i try to install the Benchmark.

I'm on 10.14.6, i have premiere pro cc 2019 installed
Any suggestions?
Thank you!

Posted on 2019-08-24 06:07:58
Chris Holzmann

Hello! I always get
Failed to install, status = -403!
when i try to install the Benchmark.

I'm on 10.14.6, i have premiere pro cc 2019 installed

Any suggestions?
Thank you!

Posted on 2019-08-24 06:13:54
Brandon Yen

Hi, when I try to run the benchmark it says "Error: Media Missing" and lists out the video files. I am running the standard benchmark, have downloaded the first two links, unzipped them, installed the benchmark, and opened the project. Is there something I'm doing wrong?

Posted on 2019-09-01 23:32:53

I just uploaded a new zip file with the benchmark media uploading right now that should resolve the issue. If you re-download "Download Part 2: Standard Test Media & Project Files (3GB)" it should work now.

Thanks for pointing out the problem!

Posted on 2019-09-03 18:12:23
Brandon Yen

Thanks, will report back!

Posted on 2019-09-04 04:05:08
Brandon Yen

It works, thanks!

Posted on 2019-09-04 17:17:06
Роман Михайлишин

Is any version for test Premiere pro CC 2017?

Posted on 2019-09-05 07:33:00
Mr. Leidy

I have a new build with a i9-9900k, 64 gb of ram, z390 Designare Motherboard, 2070 Super graphics card, and SSD hard drives, and I can't seem to get above 60 on the live playback portion of your benchmark. Do you have any suggestions why they may be? I saw in another one of your articles you had the 9900k benchmarked around 80. Thanks!

Posted on 2019-09-21 23:10:06

Just to let you guys know that your project folder can't be renamed! I accidentally downloaded 2 zips and deleted the first one. So the 2nd one has this (1)... It broke the extension resulting in file not found.

Posted on 2019-10-14 18:20:03
Lukas Messner

Hello, if I want to start the benchmark I get always the error that CUDA/OpenCL/Metal is not available on my system, even though I can set it on OpenCL acceleration in preferences. Drivers and PP are up to date. I have an i5 6500 and rx570 graphics card. Any suggestions what it might be?

Posted on 2019-11-09 17:19:35

Unfortunately, I have the same problem. "CUDA/OpenCL/Metal is not available on your system" all the time, although I have a supported Nvidia card. The log file always shows, that only the software renderer is being used:

15:22:5 - Premiere Pro Version: 13.1.5x47
15:22:5 - Premiere Pro Bencmark: V0.3 BETA
15:22:6 - Log Name Puget Systems Pr Benchmark V0.3 BETA (Pr CC 13.1.5x47),
15:22:6 - Changing playback resolution just so that the allow prompt comes up early in the benchmark process
15:22:6 - Running from Benchmark_Project.prproj
15:22:17 - Renderer set to SOFTWARE Only (No GPU Accel)

Any fix or help would be great! Thank you very much in advance!

Posted on 2019-11-19 20:39:59
Daniel Pape

The MAC installation is not working. The command runs and it says successful but the extension is not available once Premiere opens.
Mac 10.15.1, Premiere Pro 2020

Posted on 2019-11-13 20:36:42

We haven't updated it for Premiere Pro 2020 quite yet. We should have a new version up in a couple of weeks that will support 2020.

Posted on 2019-11-13 20:42:56
Daniel Pape

Worked well on PC. Ran the standard test and results were generated. Attempting a 2nd time on Mac. First run made it through the 4K effects tests but gave an error, something like, "playback is taking longer than expected" prior to generating final overall scores.

Posted on 2019-11-13 22:55:25
Daniel Pape

Mac running Premiere Pro 2020 completed successfully on the 2nd attempt, after a restart of system and Premiere.

Posted on 2019-11-13 23:16:56
Daniel Pape

FIXED: had to run the following command chmod u+x
On both: "Mac_Install_Benchmark.command" and "/ExManCmd_mac/Contents/MacOS/ExManCmd"

Posted on 2019-11-13 20:43:41

Oh, fun. Surprised a bit that the benchmark itself if working with PR 2020, but good to know that we are going to have to adjust the plugin installer to meet whatever new security stuff MacOS has implemented.

Thanks for the update!

Posted on 2019-11-13 20:47:00

just gave this a try, and I can’t install Mac_Install_Benchmark.command on 16” MacBook Pro. When I run the file I get The file “Mac_Install_Benchmark.command” could not be executed because you do not have appropriate access privileges.

Not sure what fie it’s talking about because I’m logged in as administrator. Anyway, opened the file in Smultron and tried pasting the command directly into terminal, with the result: sudo: ./ExManCmd_mac/Contents/MacOS/ExManCmd: command not found

I see that directory listed in the unzipped contents of the download. Not exactly sure why it won’t install or how to do it manually.

macOS 10.15.1

Posted on 2019-12-12 04:51:28

I was afraid of that. I had a ton of trouble getting the plugin installer working on Mac, but thought I had it worked out. If you run the "mac_install_benchmark.command" file from the terminal does it work properly? For some reason, I just can't figure out a good, reliable way to get ExManCmd (the utility to install plugins manually) working right on MacOS. I should probably just ask some of the big guys like BorisFX how they handle installation of their plugins on Mac.

Posted on 2019-12-12 04:59:36

I tried from the terminal as well. Here’s the results:

sudo: ./ExManCmd_mac/Contents/MacOS/ExManCmd: command not found
Waynes-16-MacBookPro:~ waynefox$

Posted on 2019-12-12 19:23:00

Alright, I'm going to give up on getting a self-installer working on Mac for now. Apparently installing plugins for Adobe products isn't as straight-forward as I thought it was. For now, I'm going to change the directions to tell people to download a ZXP installed like the one aescripts has available - https://aescripts.com/learn... . It works well and allows you to easily install and uninstall extensions.

Posted on 2019-12-12 20:54:13

I had already downloaded and used https://zxpinstaller.com, and everything work using it as well.Results attached Interestingly Premiere Pro on the new 16’ MBP has no support for the radeon 5500 card, followed this in activity monitor and only the intel UHD GPUwas used.

Posted on 2019-12-12 21:00:33

Zxpinstaller was what I was going to recommend, except it doesn't have a way to uninstall plugins from what I could find.

I honestly don't deal with laptops much, but I know there has been issues in the past with Premiere Pro not properly choosing the right GPU to use when you have dual graphics like that. Or it could just be that most of the tests (besides the Heavy GPU Effects test) really aren't using the GPU for much - just lumetri color.

Posted on 2019-12-12 21:07:51
Manuel Barros

tried the new 0.8 version with a fresh install of Adobe CC 2020.
Everything went ok, but in the end it gave me an error and could not save the screenshot! I only have the log "statuslog" file.
Is there a way to convert this?

Thanks in advance ;)

Posted on 2019-12-12 15:29:49

Can you give some more information? What was the actual error? Do you have any plugins installed? And can you toss me the status log file so u can see what was going on? You can email it to Labs@pugetsystems.com

Posted on 2019-12-12 15:57:38
Manuel Barros

I will run it again "the standard" one and screenshot everytime I get an error ;)
Check the email, I just sent it!

Posted on 2019-12-12 16:16:05
Manuel Barros

This 2nd time it gave me the screenshot, but no standard results. It's strange because I only downloaded the stardard pack (3gb) and it gave me the extended overall.
I'm using an AERO 15 OLED XA, i7-9750h, 16gb ram, RTX 2070 maxQ.


Posted on 2019-12-12 17:05:20
Manuel Barros

ok I now saw the 3rd point in the description of the latest version. It´s normal these results.
But are they good? comparing to the latest 0.2BETA?

Posted on 2019-12-12 17:30:34

We don't do much testing with laptops, but that seems about right as far was what I would expect to see with those specs.

Posted on 2019-12-12 17:46:44

Just like Manuel, I get an error every time. The previous version of the benchmark ran just fine.

Run Script Error: Unterminated String Constant
Then it says: Result screenshot saved to undefined

The last few lines of the statuslog has:

1:4:32 - All Media deleted - compiling scores
1:4:32 - Starting score compile process
1:4:32 - Individual scores parsed
1:4:32 - Overall scores parsed
1:4:32 - Scores all parsed
1:4:32 - Skipping writing results to log file
1:4:32 - Creating Score UI

So it looks like it crashed while or just after creating the final score?

Posted on 2019-12-18 15:55:18

Hi, I am trying to Run the test but I receive errors right away. "Could not find system info, Could not find GPU info, Could not find OS info" and second window right after first "Could not parse system information"

I am pretty sure I made all the steps written in instruction.

Any suggestions ?

Posted on 2019-12-18 18:53:21

Can you give some more information? System specs, OS version, Premiere Pro version, etc. And can you attach/link a copy of the statuslog.txt file?

Posted on 2019-12-18 21:58:20

Osx Mojave V. 10.14.6
MacBook Pro Retina 2017
2.8 Ghz, 16 GB, Radeon 555
I installed for tests 2020 but later also was trying to use 2019. The same window errors.

Posted on 2019-12-19 10:24:24

Could you run a couple of commands from terminal and screenshot the outputs?

1) system_profiler SPHardwareDataType
2) system_profiler SPDisplayDataType
3) swvers

That is what the benchmark uses to pull system information, but I wonder if it is missing one of the expected outputs on your specific model of MacBook.

Posted on 2019-12-19 20:17:17

I am getting the same issue, running a
Mac Pro 5,1
OSX High Sierra 10.13.6
EVGA 1070 ti FTW2 edition

I am having issues with Premiere Pro 2019 (ver 13.1.5) and 2020 (ver 14.0) with the errors as the Original Poster mentioned. It gives me one window with the following messages "Error #3 - Could not find system info, Error # 3 - Could not find GPU info, Error # 3 - Could not find OS info", it then gives me the error message "Error: Could not parse system information. Try re-running the benchmark"

Also, in your previous reply, there were some errors in your terminal commands you asked for. There were syntax errors in your two of your terminal commands. # 2 and # 3 were incorrect, and below you will find the corrections.

Command # 2 should be:

system_profiler SPDisplaysDataType


system_profiler SPDisplayDataType (Display was missing the 's' to make it plural)

Command # 3 should be:



swvers (you missed the underscore between the 'w' and the 'v')

What I had for the outputs:

1) Hardware:

Hardware Overview:

Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.06 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 24 GB
Boot ROM Version:
SMC Version (system): 1.39f5
SMC Version (processor tray): 1.39f5

2) Graphics/Displays:

NVIDIA GeForce GTX 1070 Ti: Chipset Model: NVIDIA GeForce GTX 1070 Ti
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Dynamic, Max): 8191 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x1b82
Revision ID: 0x00a1
ROM Revision: VBIOS 86.04.8d.00.70
Metal: Supported, feature set macOS GPUFamily1 v3


LED Cinema Display:
Display Type: LCD
Resolution: 1920 x 1200 (WUXGA - Widescreen Ultra eXtended Graphics Array)
UI Looks like: 1920 x 1200
Framebuffer Depth: 24-Bit Color (ARGB8888)
Display Serial Number: ********* (keeping this secret)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Connection Type: DisplayPort

3) sw_vers

ProductName: Mac OS X
ProductVersion: 10.13.6
BuildVersion: 17G10021

Looking forward to your solution as I have already spent a couple of hours just installing the zxp file with issues which are now solved, but I can not get any benchmark to run without the benchmark giving me an error that

Posted on 2020-01-08 00:41:31


I was running your benchmark test for premiere pro. But when i run the script i end up having an error on the heavy GPU test. But when i perform the GPU test as a single test it will run.

I can provide the log file if needed.



Posted on 2019-12-20 16:46:08

Hi Matt, could you take a look why we get this error when running the benchmark? I can't do a full benchmark now.

Posted on 2020-01-21 19:55:30

That is (unfortunately) pretty normal. We are not sure exactly what is going on, but when you stress Premiere like our benchmark does, it sometimes just... stops working right. We're experimenting with different methods to try to get it to be more reliable, but for now, some systems simply cause Premiere Pro to give random errors.

Posted on 2020-01-21 22:16:44

Thanks for the reply. We'll wait for the next version then. Btw your after effects and Photoshop benchmarks run without any problems.

Posted on 2020-01-22 17:43:45

Premiere Pro and Lightroom Classic are definitely way more... finicky. Lightroom because we have to do a lot of things through an external script rather than the built-in API, but I really don't know why Premiere Pro is giving us so much trouble. Honestly though, for all of these apps we are making them run in a way they are not designed for, so it is understandable that there are going to be some issues to work through. I'm hopeful we can get it 100% stable (or close to that) soon though!

Posted on 2020-01-22 17:47:10
Ethan Hallbeyer

Hi Matt do you know if you can run Davinci Resolve in a VM with GPU passs through?

Posted on 2020-01-23 14:53:03

There should be possible. The hardest thing is going to be getting the GPU to be passed through like you mentioned. The last time I tried something like that, you had to use an NVIDIA Quadro/Grid or AMD Radeon (I think Pro?). I believe I have seen something about getting GeForce to work in some VM applications, but not all of them. Again, it has been several years since I last did anything with that, but I do remember it being a huge pain to setup and get working. It might be easier now though.

Good luck if you decide to try!

Posted on 2020-01-23 20:32:38

Keep getting this error: https://uploads.disquscdn.c...

Posted on 2019-12-23 17:52:21

I am also getting this error.

Posted on 2020-01-07 20:58:57
George Winchell

Hello, I have run benchmarks multiple times, both standard, extended and a few individual and get no results. similar to other post I get message that results are saved to undefined. Status Log shows 13:6:52 - All Media deleted - compiling scores
13:6:52 - Starting score compile process
13:6:52 - Individual scores parsed
13:6:52 - Overall scores parsed
13:6:52 - Scores all parsed
13:6:52 - Skipping writing results to log file
13:6:52 - Creating Score UI
Other than that everything seems to run normal. This is on Windows 10 64 pp2020

Posted on 2020-01-06 01:34:06

Downloaded the benchmark twice. The first time it would not work with Adobe Premiere 2019, it gave an error stating that the benchmark was made with a newer version of Adobe Premiere.

Downloaded a second time, installed a fresh copy of OS X High Sierra and fully updated it on to a spare drive, installed Adobe Premiere 2019 and now the ZXP installer is telling me that there is "no application compatible with PugetPRBenchmark.zxp was found on your computer"

Posted on 2020-01-07 23:31:43

Please review the "How to run the benchmark" section: https://www.pugetsystems.co... . Both of those issues are addressed in the text (and partially in the video).

Posted on 2020-01-07 23:39:11

Hi Matt,

I did get it to work with Premiere 2020 (Ver 14.0).

Everything works up until I run the test, and then I get this trifecta error message window with the following messages "Error #3 - Could not find system info, Error # 3 - Could not find GPU info, Error # 3 - Could not find OS info", it then gives me the error message "Error: Could not parse system information. Try re-running the benchmark"

I copied my reply to your reply to a previous post regarding getting system information to assist:

High Sierra 10.13.6
EVGA 1070 ti FTW 2
MacPro 5,1

Also, in your previous reply, there were some errors in your terminal commands you asked for. There were syntax errors in your two of your terminal commands. # 2 and # 3 were incorrect, and below you will find the corrections.

Command # 2 should be:

system_profiler SPDisplaysDataType


system_profiler SPDisplayDataType (Display was missing the 's' to make it plural)

Command # 3 should be:



swvers (you missed the underscore between the 'w' and the 'v')

What I had for the outputs:

1) Hardware:

Hardware Overview:

Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3.06 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Memory: 24 GB
Boot ROM Version:
SMC Version (system): 1.39f5
SMC Version (processor tray): 1.39f5

2) Graphics/Displays:

NVIDIA GeForce GTX 1070 Ti: Chipset Model: NVIDIA GeForce GTX 1070 Ti
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Dynamic, Max): 8191 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x1b82
Revision ID: 0x00a1
ROM Revision: VBIOS 86.04.8d.00.70
Metal: Supported, feature set macOS GPUFamily1 v3


LED Cinema Display:
Display Type: LCD
Resolution: 1920 x 1200 (WUXGA - Widescreen Ultra eXtended Graphics Array)
UI Looks like: 1920 x 1200
Framebuffer Depth: 24-Bit Color (ARGB8888)
Display Serial Number: ********* (keeping this secret)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Connection Type: DisplayPort

3) sw_vers

ProductName: Mac OS X
ProductVersion: 10.13.6
BuildVersion: 17G10021

Looking forward to your solution as I have already spent a couple of hours just installing the zxp file with issues which are now solved, but I can not get any benchmark to run without the benchmark giving me an error that

Posted on 2020-01-08 01:16:36

Has there been any follow up to what the error was in this instance?


Posted on 2020-01-25 20:12:04

Hi Matt,

Has there been any follow up Or a better understanding as to what the error was in the instance below?


Posted on 2020-01-25 20:14:25
AL de Zilva

Hello, i am receiving the same errors as some of the other people when running the latest Benchmark with PP 2020.

A bunch of "Run Script Error: Unterminated String Constant"
Then it says: Result screenshot saved to undefined

I'm running the benchmark, with the files off the system drive

Any ideas on what could be wrong?

Dell Preceision 5820 Tower X-Series
Intel Core i9-9960X CPU @ 3.10GHZ
64.0GB RAM
Windows 10 enterprise v1903
System Drive: PC400 NVMe SK hynix 512GB SSD
Cache/Data Drive: NVMe PM981 NVMe Samsung SCSI Drive 2TB
StoreNext SAN connected via Fiber

Running PPro 2020 v.14 Build 572
Red Giant Magic Bullet 13 Suite
Red Giant Universe
Trapcode v15 Suite
RSMB Pro v6

FRAME.io extension

Posted on 2020-01-09 19:27:07
AL de Zilva

Hello... just checking in to see if there are any ideas or help...


Posted on 2020-01-14 19:34:04
Jason Tighe

Hoping for a reply, I have this exact issue!

Posted on 2020-01-28 19:30:45
James Anderson

I ran PugetBench for Premiere Pro 0.8 twice and it did not create the results PNG like the dialog says it did.

Posted on 2020-01-13 17:14:23
Jason Osterday

Receiving the same error as Mr AL de Zilva:

"Run Script Error: Unterminated String Constant"
"Result screenshot saved to undefined"

This occurred in both CC '19 and '20. Happening on all machines so far - fresh Win10 installs, some with/without plugins, some completely vanilla from factory and only have PR installed.Testing on Local Disks only.


Posted on 2020-01-15 03:00:14

We recently moved to the score screen being generated from a motion graphics template, so my guess is that it relates to that in some way. I never had any issues in my testing, however, so I'm not sure what might be causing it. Do you have AE installed as well? (It shouldn't need it, but maybe it is causing some issue?) And you have Pr/Windows in English?

Any chance you could toss the "statuslog_TIME.txt" file in an email to mattbach@pugetsystems.com? That might have some information in it that can help me replicate.

Posted on 2020-01-15 17:34:56
Jason Osterday

Thanks Matt. I'll send over an email with the file.

- PR/Win10 is set to English. AE is installed. I'm wondering if there's a permissions issue from the scripting attempting to write to a local drive without admin access? I'm conducting the test as an admin, and the AE version writes just fine, so I'm not sure. I'll test on a machine without PR installed just to remove variables.

Posted on 2020-01-15 23:28:34

It shouldn't be a permission issue since it is essentially just exporting a single frame to use as the screenshot. Since it isn't even bringing up the score screen, it must be some problem with actually loading the motion graphics template. Hopefully there will be some nugget of info in the log file that will point me in the right direction.

One thing that isn't logged currently that would be helpful is knowing the full path to the benchmark location. Like "D:\downloads\Benchmark" . I know I am accounting for things like spaces right now, but it is possible some sort of special character is messing stuff up.

Posted on 2020-01-15 23:37:55

I keep getting an error message "Something went wrong with the playback testing for 4K CinemaRaw Light 10 Bit (59.94FPS)" when I'm running the extended test. I've tried running that specific benchmark on its own and it works perfectly.

Posted on 2020-01-21 18:41:40

That is (unfortunately) pretty normal. We are not sure exactly what is going on, but when you stress Premiere like our benchmark does, it sometimes just... stops working right. We're experimenting with different methods to try to get it to be more reliable, but for now, we haven't found a completely solid way to do the extended version of the benchmark. Standard seems to be OK, but the more tests you tell it to run in sequence, the worse it gets.

Posted on 2020-01-21 18:49:39

Just thought I'd follow up, seems to be fixed in 0.86, thanks!

Posted on 2020-01-31 16:24:33

Great! Thanks for letting us know!

Posted on 2020-01-31 19:10:45

I have run it several times, but why were the scores all 00.00?

Posted on 2020-01-21 18:59:07

I've run the test twice, both times it gave me empty results. Any idea what I'm doing wrong?

Posted on 2020-01-22 16:38:05

I've had a few reports of this, but not sure what is going on. I'm making quite a few other changes for the next update, so I'm hoping one of those also resolves this issue.

Posted on 2020-01-22 17:37:13
Paul Knepper

Are versions 0.3 BETA and 0.8 BETA results comparable for Premiere Pro benchmarks?

Posted on 2020-01-28 14:58:24

Individual codec tests and the "Standard" preset should be the same. The "Extended" preset will be a little different since we dropped the 29.97 FPS CPU and GPU effects tests. This means that the Extended test scores will be slightly different than previous versions, but it shouldn't be by a huge amount

Posted on 2020-01-28 17:41:26
m c

Hi, I am receiving the same errors as some of the other people when running the latest Benchmark with PP 2020.
It complains : Error#3: Could not find system info Error #3: Could not find GPU Info Error#3: Could not find OS info.
I've been noodling around for days trying to get through this. This is an iMac Pro. Mac OS = 10.15.2

Is there a workaround for this, or are we waiting for a fix? I'd be happy to help try out another beta version and provide feedback if you want help.
This suite of tools is really helpful, and I hope that this issue can get worked out, as PrePro is our main app, and with new apple hardware around now, this bench marking becomes even more useful.

Posted on 2020-01-31 18:51:43

Have you tried Version 0.86 BETA that went up yesterday evening? That should have the fix for that issue.

Posted on 2020-01-31 19:09:43

Very interesting!
So today after writing that post this morning, I downloaded fresh from your site onto a different iMac Pro and it worked fine the first time!
On a macbook pro with the download from a few days ago it worked fine as well...
I will go back to the first iMac Pro I was working with and get a fresh download and try again. I will only post if I have trouble. thanks!

Posted on 2020-01-31 23:36:12
Chi Chong Cheong

Newest Version 0.86 said error: not all files are duplicated from standard/ProRes422_4K_59.94FPS
I've make sure files are not corrupted from extract the zip

Posted on 2020-02-01 12:47:29

The benchmark makes a bunch of copies of the test media to keep the download size reasonable. Is your drive full? You probably need around 100GB free - not sure on the exact amount off the top of my head

Posted on 2020-02-01 14:53:50
Chi Chong Cheong

I had 30GB left, I will clean it up and try again thanks.
I might only have 90GB left after cleaning because of the small laptop SSD, hope it will work.

Posted on 2020-02-01 18:23:25
Chi Chong Cheong

This time I got successfully run however the score screen didn't show up and no scoring picture is produced.
Is there any solution? Thank you

Posted on 2020-02-02 05:27:23
Chi Chong Cheong

I got an error say "Error could not find sequence named Benchmark_MultiCam in 4K_H264_59.prproj"

Posted on 2020-02-02 05:28:37

i'm getting the same error. Have you been able to find a resolution?

Posted on 2020-02-09 13:21:36

You no might want to re-download the benchmark, it may have not downloaded fully, or unzipping didn't complete.

You can also open that project manually to make sure that sequence is present, reinstall the benchmark plugin, and try everything listed in the troubleshooting section.

Posted on 2020-02-09 16:04:50

There is no score screen in the latest version. Pr 2020 broke scripting for motion graphics templates, so the full results are currently being saved to a CSV log file in the benchmark folder.

Posted on 2020-02-02 05:47:56
Jason Tighe

The latest version 0.86, Premiere Pro 2019

The script cannot open the "4K_H264_59.prproj" file as it was created in a newer version of premiere (2020)

Can I just delete this file and create a PrPro 2019 file under the same name? Or is their another workaround?

Excited to get this working ahead of a lot of hardware conversations here. Thanks again Matt.

Posted on 2020-02-03 22:30:32

No, Premiere Pro 2019 is not supported in the latest version. We switched to using pre-made project files for each codec tested and only made them for Premiere Pro 2020. Technically you should be able to use one of the "version downgrader" utilities that are out there on each project, but I suggest just installing Premiere Pro 2020 side-by-side with 2019 and running the benchmark straight from Pr 2020. That way, it wont affect your current projects, but you can still run the benchmark.

Posted on 2020-02-03 22:38:49
Jason Tighe

Thank you Matt,

We are however limited to PrPro 2019 only. As deployed by our corporate IT department, we are on an outdated version of Windows 10. I believe this is a standard approach in regards to cyber security.

If this utility remains on the latest version of premiere pro as it is updated, you may be limiting participation from larger corporate customers in this way. I was looking forward to benchmarking our existing Puget systems.

Hoping for an update on our OS before these files outpace is again...

Thank you again for the help Matt.

Posted on 2020-02-03 22:50:46

Ah, that definitely makes sense. Once he hit full launch we plan on supporting multiple versions, but in the current beta iteration it just isn't worth the time to get it working (and making sure it is working) on multiple versions. But long terms we do want to support multiple versions whenever possible even just so we can do performance comparisons whenever Adobe launches an update.

Posted on 2020-02-03 22:56:06
Hannes Werks

Getting a "Script Alert" at the beginning "ERROR - CUDA/Metal/OpenCL is not available on this System. Performance may be lower than expected", its a i9-9900K with a 2070 Super with the newest driver 442.19 and CUDA installed. Is there a known problem/solution?

Posted on 2020-02-04 23:41:01

Are you able to manually set the Mercury Playback Engine to CUDA? It is in Project Settings -> Renderer . If you can, that must be some new bug I've never encountered before. If you do not have any option beyond "Software Only", that means that Premiere is not able to utilize your GPU. Common fixes are clearing the Premiere Pro preferences, cache, reinstalling the GPU driver (with DDU driver cleaner in-between uninstall/reinstall), or re-installing Premiere Pro.

Posted on 2020-02-04 23:50:58
Hannes Werks

Thank you for the ultrafast reply! I can switch manually between CUDA OpenCL and Software. PC is freshly installed with Win10pro 64, the AdobeCloud and the newest drivers and firmware for every component. Nothing else is on the system.

Posted on 2020-02-04 23:57:52

Huh, if you can switch then I'm not sure why the API isn't reporting CUDA or OpenCL as an option. As long as you have it set, it should be just fine to run the benchmark. I'm pretty sure that is an error that allows you to continue.

Posted on 2020-02-05 00:03:26
Hannes Werks

yeah, really strange. the test is running, but its really strange how the pc is using its resources. Is there somewhere a result list of how my system should perform approximately?

Posted on 2020-02-05 00:21:24

For now, the best thing is to compare your results to one of our recent articles: https://www.pugetsystems.co... . With your GPU, I would expect a Overall Score of about 700 points with either the Extended or Standard preset.

Posted on 2020-02-05 00:23:50
Hannes Werks

apart from the error at the beginning and that the system performed very strangely in the monitoring, the overall score is 808, LPS 90 and SES 71.6, which looks like normal results for this setup.
thanks again for the quick answer! your company and homepage is by far the best and most competent source of information in the whole sector. hats off!

Posted on 2020-02-05 00:37:47
Simon Kipfer

I just did the 39+ min Premiere test on my Workstation. It worked all through and said it successfully finished but all scores are set to 0. :(

What am I doing wrong?

Win10 Pro 10.0.18363
Premiere 2020 14.0.1 B71
32GB Ram
GeForce Nvidia GTX Titan X
m.2 hdds

Posted on 2020-02-06 13:33:14

Download the latest version of the benchmark (0.86 Beta). Premiere Pro 2020 broke the API for motion graphics templates, so we had to switch over to a .CSV log file.

Posted on 2020-02-06 15:31:12

Is there any page like "cpubenchmark [dot] net" for PugetBench for Premiere Pro, so we could compare our results with them?

Posted on 2020-02-12 10:11:24

Not yet, but that is planned for once we get to full release!

Posted on 2020-02-12 15:26:40
David Farkas

Hmm. I've run the benchmark before on another system in my office. Built a new TR 3960X system and wanted to test it out. Downloaded the latest V0.86B, installed the plug-in as Administrator, and everything looks fine. I click the button to run the standard tests and.... nothing happens. No error, just nothing. If I click the Extended test button, a pop-up error comes up alerting me to the missing media files. Any ideas?

Posted on 2020-02-21 21:07:57

Can you provide the statuslog files? And did you go through everything in the Troubleshooting section? https://www.pugetsystems.co...

Posted on 2020-02-21 21:19:06
David Farkas

Yes. I followed the troubleshooting guide. No change. Here's the latest log.

16:40:28 - timestamp: 2-21-16-40
16:40:28 - starttime: 2/21/2020 16:40
16:40:28 - Media Path: /C/Users/David/Downloads/PugetBench%20for%20Premiere%20Pro/
16:40:28 - Media Copy Path: C:\Users\David\Downloads\PugetBench for Premiere Pro\
16:40:28 - Which tests should we run?
16:40:28 - Enabling runtest for 4K H.264 150Mbps 8bit (59.94FPS)
16:40:28 - Enabling runtest for 4K ProRes 422 (59.94FPS)
16:40:28 - Enabling runtest for 4K RED (59.94FPS)
16:40:28 - Enabling runtest for 4K Heavy GPU Effects (59.94FPS)
16:40:28 - Enabling runtest for 4K Heavy CPU Effects (59.94FPS)
16:40:28 - Premiere Pro Version: 14.0.2x104
16:40:28 - Premiere Pro Benchmark: V0.86 BETA
16:40:28 - Benchmark Name PugetBench for Premiere Pro V0.86 BETA (Pr 14.0.2x104)
16:40:28 - Running from Benchmark_Project.prproj
16:40:28 - Checking that all media files are present

Posted on 2020-02-21 21:44:15

Huh... No idea why it could possibly be breaking in that manner. I'll jot down a bug report and see if I can replicate. Thanks for reporting!

Posted on 2020-02-21 21:54:16
David Farkas

Any further thoughts on the hangup?

Posted on 2020-02-27 04:17:39

Sorry, I haven't been able to really look into it quite yet. I'm in the middle of a pretty big update to all the benchmarks, and whatever the issue is, it will likely be fixed when I finish the update.

Posted on 2020-02-27 17:07:57
Victor Yavchunovskiy

But where can I get version 0.88? Seems that only 0.86 is available for download, and it cant show start dialog an run tests on my pc...

Posted on 2020-03-09 01:32:47

Oops, I forgot to update the download button text. Fixed now.

Posted on 2020-03-09 15:32:10
Victor Yavchunovskiy

Oh, really, and I just mixed up the archives in my downloads. Thanks! 0.88 starts fine. Some difficulties with CUDA and generating results screen are more likely on my side, cyrillic characters in user name already worked like that in other programs.

Posted on 2020-03-09 18:48:02
Victor Yavchunovskiy

Now the benchmark successfully performs individual tests, but crashes from the complete one at the end with an error. Could you please tell what could be wrong? Logs

Posted on 2020-03-10 13:37:51

It looks like that test isn't able to play correctly when part of the overall run. Honestly, it isn't all that uncommon for issues like that to pop up. I see Premiere Pro crashing or otherwise having issues with about 1/3 of the benchmark runs I perform - and that is all on completely modern hardware. I'm constantly trying new things to increase the stability, but something like what you are seeing is not really a benchmark problem, it is a Premiere one as far as I can tell.

Posted on 2020-03-10 16:14:14

Hi guys, love your benchmarking system and I swear by your site's reviews and benchmarks when I consider what parts to buy. I'm trying to run this test on my iMac running 10.15.3 and when I first open it up, I'm getting three pop-up windows:

1) Error: Could not get system information from //Volumes//Macintosh HD/usr/sbin/system_profiler SPHardwareDataType . Continuing the benchmark, but will not be able to accurately log system specs.

2) Error: Could not get system information from //Volumes//Macintosh HD/usr/sbin/system_profiler SPDisplaysDataType . Continuing the benchmark, but will not be able to accurately log system specs.

3) Error: Could not get system information from //Volumes//Macintosh HD/usr/sw_vers . Continuing the benchmark, but will not be able to accurately log system specs.

I made sure to add Premiere to the Accessibility area as per the instructions. Any clue what might be causing this? I'm running this benchmark to compare the performance of Premiere on MacOS vs in Windows 10. I use MacOS for Final Cut Pro projects but Premiere is my daily driver and I'm curious which OS will give me better performance out of premiere with my existing hardware.

Posted on 2020-04-01 21:35:59

I should add. Obviously, I'm just fooling around with this. I'm just wondering if those error messages up top are skewing my results in favor of Mac. While totally possible, it's just weird to me because the Geekbench 5 score is higher on the Windows side. Either way, not super urgent but if anyone knows what I'm doing wrong, help me out! Thank you!

Posted on 2020-04-01 21:44:06

We have a new benchmark version coming out soon that hopefully will resolve those issues. They shouldn't affect the results at all, that is all just to get the system's specs for logging purposes.

As for your results vs Geekbench, that honestly doesn't mean anything. Different applications simply utilize hardware and software APIs differently, so it isn't unusual at all for one application to be faster on Mac while another is faster on Windows. That even happens fairly often withing the Adobe ecosystem.

Posted on 2020-04-02 16:35:51

Wow, I had no idea. That's a pretty big difference. Thank you so much for replying. I hope you and your team are staying safe!

Posted on 2020-04-03 16:21:00
Steve Smith

Just downloaded the benchmark (link says 0.88, version on PP shows 0.90, and the same type of problem occurs on the standard and extended benchmarks. I'm on a 2019 Mac Pro, running Catalina 10.15.4, latest and up to date Premiere Pro 2020. Multiple copies of the video files are created at the start of the benchmark, and the first 3 files, _b _c _d, are created properly. copies beyond this are not created and the location it shows is a Windows file path, which of course wouldn't be possible on a Mac system. Any ideas?

Posted on 2020-04-07 00:09:24

You must have caught us right in the middle of updating the benchmarks. Can you elaborate a bit more on what the file path is that it is trying to use? Creating copies of the media is in a pretty simple loop where the path never changes (just the file name), so I can't see how it could possibly work for a handful of the copies but not the others. Are you sure you have enough free disk space? Some of these files are pretty big, so making a dozen copies can take up 50GB+ in some cases.

Edit: I just re-installed the plugin from the download on the 2019 Mac Pro I have and it looks like it is copying the media OK. In addition to what I said before, you might also try clearing your preferences and make sure Premiere Pro is added to the accessibility settings.

Posted on 2020-04-07 00:14:40
Steve Smith

Hi Matt,

It's a fresh new install of the OS, 500GB internal SSD, new install of PP 2020, up to date. If I wait for the dialog screen (which is attached) to come up, I can manually copy files _e - _j, locate the files, and the benchmark will continue and complete. You can see on the dialog that the benchmark is trying to locate them on an impossible Windows path. The blog won't let me upload an image, even though I'm signed in to disqus and puget. Here's a dropbox link: https://www.dropbox.com/s/4...

Posted on 2020-04-07 02:56:22

That's odd... from everything I've seen, opening projects through the API like we are never has the "media offline" window come up. When we open the project, one of the first things the benchmark does is re-link the media according to where you have the project files on your system. Disregarding Mac and PC paths, we don't know where people are going to have the files on their system, so we have to re-link the media every time no matter what.

The fact that it is able to re-link a couple of them, but not the others is very odd - especially since it isn't giving you an error message. Just to confirm, are the copies of the media being made at all, or are you saying you are manually making them?

What is also strange is that this is not the first codec that is tested, so the benchmark was able to successfully make copies of the media and re-link them at least once already. in "Documents\PugetBench\Premiere Pro" there should be a series of timestamped folders. Would you mind grabbing the "Status.log" file from one of the failed runs and emailing it to me at mattbach@pugetsystems.com? I might be able to figure out what is going on from that.

Posted on 2020-04-07 15:13:40

Premiere Pro crashes every time I try and run the benchmark... 0.88 worked but not 0.9...

Posted on 2020-04-21 04:21:08

Are there download links to older versions of the benchmark?

Posted on 2020-04-21 04:22:42

Nvm found the problem - Win10 1909 Cumulative Updates: April 14th, 2020 seemed to be the culprit

Posted on 2020-04-21 05:36:56

Yea, Premiere Pro can definitely be less stable than everyone would like... We actually have our benchmark runs set to re-launch the benchmark up to three times if Premiere Pro happens to crash simply because it happens often enough to be a problem. In fact, that is one of the features we built into the paid version's command line utility since it is so common.

Posted on 2020-04-23 22:58:22

Unfortunately, this isn't an intermittent crash. It is crashing every time test 1 runs. Thanks to graphisn, I'll try removing recent Win10 updates, but we really need this working with the latest updates. I have a commercial license and setting the re-run CLI parameter doesn't help. Any suggestions?

Posted on 2020-05-12 12:28:43

I think I have it figured out - it is a bug in the Premiere Pro API that is specific to version 14.1. I added a warning below the benchmark download links, but it is a problem with the "qe.project.getActiveSequence()" hook which causes Premiere Pro to crash. This issue appears to be isolated to this one version and is not present in previous versions of Premiere Pro (14.0.4, etc.) or the public beta (14.3.x). We recommend installing a different version of Premiere Pro if you want to run this benchmark.

Posted on 2020-05-12 18:24:42

FYI, this appears to also be resolved in the 14.2.0 release that Adobe pushed out today.

Posted on 2020-05-19 20:01:17

Yep! I was just checking that myself! I'll update the warning box. Thanks for checking it as well!

Posted on 2020-05-19 20:14:28
Katalytic Kuya

Keeps crashing after starting the benchmark. Doesn't seem very useful, or at least there's no helpful error reporting. No generated crash log from Premiere that I can see..

Posted on 2020-04-29 05:54:49
Richard Knight

Just tried the extended benchmark 0.9 on the latest Permiere beta, and the program crashes out without any error messages about half way through. Premiere was fine.

Posted on 2020-05-12 12:22:15

The beta 14.3.0 Build 12 (which I assume matches your is working okay for me with version 0.9 of the benchmark. As Matt explained above, there is an issue with 14.1, though.

Posted on 2020-05-13 13:51:35
Richard Knight

My system runs the standard bench mark but not the extended, it falls over when loading the 4K H264 150Mb/s 10 bit files which I assume is the start of the extended tests. I have deleted the extended media from the Puget folder and then re-added from the zip download but it still crashes.

Posted on 2020-05-13 18:19:01
Richard Knight

Now I find the benchmark does not run at all on 14.2 or Beta. The start button changes colour when pressed but nothing happens. I have re-installed both Premiere versions running the cleaner after the uninstall. I have also reinstalled the ZXP plugin. Any thoughts?

Posted on 2020-05-22 10:47:34

It is possible we had a non-release version of the plugin uploaded for a couple of minutes that you may have had really unfortunate timing and downloaded. There was an issue with Google Drive and their versioning system that took a couple of minutes to resolve. I don't want to make you have to re-download the full 3GB of files, so download and try this version of the plugin: https://drive.google.com/op...

Posted on 2020-05-22 18:12:21
Richard Knight

Just tried that new download and all seems to work now, many thanks.

Posted on 2020-05-22 21:03:34

I tried running the v0.9beta benchmark on my 2010 Mac Pro, running 10.14.6 & Radeon VII, and both the Standard and Extended Benchmark test always crashes with a "Sorry, a serious error occurred that requires Adobe Premiere Pro to shut down" at the beginning of the first playback test (Premiere 2020, Metal enabled in project settings)

Posted on 2020-05-17 05:27:47

What version of Premiere Pro? 14.1.0 has a bug in the API that we have noted right under the benchmark download button. You can either install the beta, or go back to a slightly older version of Premiere Pro to run the benchmark.

Posted on 2020-05-18 16:19:29

Can I Download Download PugetBench for Premiere Pro 2019 or PugetBench_PR.zxp for 2019?

Posted on 2020-06-02 20:36:43

Right now, the benchmark is only compatible with Premiere Pro 2020. Once we get out of beta, we will try to keep it working with at least one or two previous versions, but there is still a good amount of development to do, and supporting multiple versions would simply add too much work at the moment.

Posted on 2020-06-02 20:52:41

I have a dual Mac Pro 5,1 with a 1070 Ti... with regards to completing the test, it only shows it as a single core system. Is this an error?

I recently ran two tests with the 3.06 GHz x5675 Xeon cpus but it keeps showing one processor.

Posted on 2020-06-26 06:02:52

I think that is a bug. I don't have easy access to a Mac with dual CPUs at the moment, but any chance you could download this version of the plugin and see what it reports? https://drive.google.com/fi... . When you click "Run Benchmark", it will gather the system specs and give you an alert box of what the CPU is, but not run the full benchmark.

Hopefully you should see "2x 6-Core Intel Xeon @ 3.06 GHz"

Posted on 2020-06-26 16:23:50

Hi Matt,

Upon running the benchmark as you described, I received a JavaScript alert, and it reads:

"CPU: 2x 6-Core Intel Xeon @ 3.06 GHz"

Posted on 2020-06-26 21:27:18

Perfect! I'll make sure that gets included in the next update. Thanks a ton for verifying that it worked.

Posted on 2020-06-26 21:49:08

Hi Matt, no worries and thank you!

I wanted to ask one more thing.

I was attempting to do a comparison with a team red card that I have and use (AMD Sapphire Toxic R9 280X) but the test froze about 3/4 of the way through and froze the whole system.

Would it be safe to assume that the R9 280X is overtaxed with PugetBench, considering the minimum requirements state at least a 4GB or greater GPU?


Posted on 2020-06-27 14:07:39

Yea, that is probably what is going on. We're still trying to work out ways to have tests fail more gracefully, but if the hardware is taxed to the point that the whole system freezes or Premiere Pro crashes, there really isn't a whole lot we can do about that.

Posted on 2020-07-06 22:31:14

This is great benchmark. Thanks Matt for all the hardware in preparing this and sharing it.

I am very curious to see that most of the MacBook pros all score very highly on "Live Playback Performance" and yet other systems which are much more costly and higher specified typically all perform worse on live playback.

So what's reason MacBooks are performing so well with Live Playback? What's the MacBook Pros secret sauce?

Posted on 2020-06-30 09:09:45

I was surprised to see my High Sierra Hackintosh 8700K (OC to 5.1Ghz) 64GB @3000Mhz with GTX 1080 only score 400 in Pugetbench for Premiere Pro... It does much better in Pugetbench for After Effects; scoring 700. Any theories why? Am I suffering from outdated Nvidia drivers on High Sierra and need to update to AMD GPU and more recent OSX and drivers? Or am I simply suffering from a lack of cores with my 8700K?

Posted on 2020-07-02 17:47:31

Interestingly I decided to test Pugetbench for Premiere on Windows and got a score of 460 with the same setup. Then with an overclock on the video card i got to 572.... so it's something to do with Mac OSX/software optomization I guess.

Posted on 2020-07-05 14:44:02
Madhavi Rao

Hi, can you please explain below queries :
How are the standard score calculated ?
which framework does this benchmark use ?
how can we run individual test case in this benchmark ?

Posted on 2020-08-06 08:33:13
Zoe Earnshaw

I've just done the Premiere benchmark (which is great- thank you so much) on a new, just out the box MacBook Pro 16 (late 2019) 8-Core Intel Core i9 @ 2.4 GHz 64 GB, Intel UHD Graphics 630, AMD Radeon Pro 5500M, Mac OS X (10.15.6) - clean machine, updated OS and AE freshly installed, no other software running, memory preferences and GPU settings as suggested- but score of 449- this seems much lower than other MacBook Pros of same spec- any ideas to improve? Also what do you suggest doing with location of disk cache when only 1 drive on the laptop...? Have run Geek Bench and Cinebench and they seem better- i.e. comparable to other same spec MCPs? Any suggestions gratefully received....

Posted on 2020-09-21 21:44:20

There have actually only been a handful of MacBook Pros results uploaded for the Premiere Pro benchmark, and your score is the highest one so far. On the result browser, are you making sure that you are looking at the results for just Premiere Pro? The different benchmarks (Pr, Ae, Ps, etc.) all have different scores so they can't be compared against each other.

Posted on 2020-09-21 23:38:00
Charles Clover

Hi. I am having issues with the premiere pro benchmark on both Mojave and Catalina. Getting a javascript error regarding live playback. Also the after effects version fails at the end on the 3D tracking section. Any ideas?

Posted on 2020-10-07 12:12:29

Usually, those kinds of problems are due to either some corrupt preferences or installs of the Adobe app. Make sure you go through everything in the troubleshooting section, and if you continue to have issues you may have a problem either with your OS or a hardware problem.

Posted on 2020-10-07 15:49:53
Charles Clover

Thanks Matt. Got the premiere pro benchmark working. AE comeswup with a server connection issue, I'll give it a fresh install and have another go.

Posted on 2020-10-08 07:31:44

Hey guys, LOVE your benchmark test. My computer is a dual boot. One side is MacOS (Hackintosh) and the other is Windows 10. I used your Premiere Pro bench easy peasy on the MacOS side but on the Windows 10 side, no luck. The ZXP installers (I've tried multiple ones) haven't worked and my Extensions menu is greyed out. Any ideas?

Posted on 2020-12-05 04:21:59

Update. Eventually, it worked on the Windows side. I shut down Premiere Pro and walked away to do something else and later on when I came back, I tested it out of curiosity and the extension showed up. I had restarted it before. No idea what happened. Interesting results to say the least. While the overall score is higher on the Windows side (570 vs 533) and the export score is also higher on the Windows side (61.5 vs 39). The live playback score is higher on the MacOS side (67.6 vs 52.5) as is (54.6 vs 36). Is this a Metal vs Open CL thing?

Posted on 2020-12-05 14:56:41
Pierre Buys Films

Hi guys your PugetBench for Premiere Pro give me a H264 error each time in a row even after resetting premiere preferences.
My Premiere version is 14.7.0 of Premiere Pro 2020.
System us a Asus Tuff B550M plus with Ryzen 5 3600 with 64 gb ram and a GTX 750Ti.

Posted on 2020-12-18 16:42:07

The GTX 750 Ti is a pretty old GPU at this point - I wouldn't be surprised if it doesn't full support Premiere Pro's hardware decoding/encoding. Depending on which 750 Ti you have, you might also not meet the minimum requirements for Premiere Pro (2GB of VRAM, although you really should have 4GB if you even want to attempt running the benchmark).

You could try disabling hardware decoding and encoding in "Preferences -> Media" and that might allow it to complete, but that will probably result in lower performance.

Posted on 2020-12-18 18:50:24
Brad Foster

When i open the "Benchmark_Project.prproj" my extension tab is greyed out, when i open PP, then add the project its ok, plugin opens, but when i click run, it doesnt do anyhting. do i need a key, is it not a free test?

Posted on 2020-12-30 08:07:29

Weird issues like that are generally caused by some preferences setting (either something you changed that we aren't aware of that can cause issues, or corrupt preferences). Clearing the Adobe preferences as well as cache files tends to resolve those types of problems.

Posted on 2020-12-30 18:13:29

Can we download the ZXP file somewhere else than Adobe Cloud ?
It would be very convenient.
Thanks :)

Posted on 2021-01-29 09:40:49

We keep ZXP packages for licenses users since reviewers and such often need to keep systems off the internet or need to make sure the benchmark version doesn't change. But, they aren't behind a login wall or anything, so you can use them as well if you want to: https://www.pugetsystems.co...

Posted on 2021-01-29 18:11:26


I downloaded the latest version of Adobe Premiere for MacOS and your Adobe Premiere benchmark test files.

Both were downloaded on Sept 23, 2021.

The benchmark runs through the test almost flawlessly.

Upon completion of the benchmark, the score is blank due to one of the tests being blank/unable to score.

Is this a new bug?

I see some other results that have recently been uploaded are also showing blank scores in your results list.

Posted on 2021-09-24 16:19:03

To clarify, I am using Premiere Pro Version 15.4.1 (build 6) and macOS BigSur 11.3. I have also ran the test using the other project file, which ends up being converted and run in to the same results. It will not generate a final score/tally because one of the tests failed.

Test: 4K H.264 150 Mbps 8bit

Setting: 4x Forward - Live Playback (Full Res)

Result: 0.00

I get every other result shown with the RAW Results, but that one test seems to cause an issue.

System specs:

6 Core Xeon 5680
32GB 1333MHz ECC Ram
GPU - Radeon Vega Frontier 16GB

Could this be a setting glitch somewhere, as the hardware should not have an issue. Thank you :)

Posted on 2021-09-27 22:51:40

Your system is really old (the CPU was released more than 11 years ago), and H.264 is a really difficult codec to work with without hardware acceleration - especially things like 4x playback. I think your system is simply not able to run that test, which is why it isn't able to generate a final score.

Posted on 2021-09-28 16:37:56
Marc LaGana

I'm trying to run this on Premiere Pro 2021, Version 15.4.1 (Build 6) on Windows 10 -- 5950x, RTX 3090, 64GB RAM.

It keeps getting stuck on "Gathering System Specs"

I installed the plug-in successfully through Creative Cloud and downloaded the latest project.

Opened Benchmark_Project_15, click Run Benchmark, and click OK on the confirmation. It says "Gathering System Specs" and then just sits there. No progress bar advancement or any other sign of it actually doing anything. I've left it sitting for 10 minutes at a time, nothing. I can click Cancel and quit Premiere without any issues.

So far I've tried disabling Windows Defender Real Time virus protection, and re-installing the plug-in. Didn't seem to change anything.

Posted on 2021-10-05 21:38:55

If you haven't give your system a reboot. Possible there is an existing task running that didn't end properly that is preventing the specs from gathering.

Posted on 2021-10-05 22:04:39
Marc LaGana

Hey Matt, thanks for the quick response. Rebooting didn't seem to do anything...

Posted on 2021-10-05 22:25:13