I was afraid of that. Until then, suggestions and other thoughts are welcomed as always. I might only have 90GB left after cleaning because of the small laptop SSD, hope it will work. This is on Windows 10 64 pp2020. 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... Just tried that new download and all seems to work now, many thanks. The more you look at these results, the more there is to learn. I was just checking that myself! On the AMD side, it’s only a few models that managed to see an improvement, with most of them showing a slight degradation in performance instead. Thanks a ton for verifying that it worked. That is (unfortunately) pretty normal. 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. Is there a workaround for this, or are we waiting for a fix? With this 14.2 release, we revisited all 21 GPUs we just finished testing for our latest Radeon Pro review, and added a bunch more on top to help paint a better overall picture. Nvidia GeForce RTX 2060 Super – Best graphics card for gaming and video editing. 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. for slightly more modest configs... 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. The parts of the line that are Red, the video card's GPU could be handling. 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 has two tests of GPU Acceleration. Some of these files are pretty big, so making a dozen copies can take up 50GB+ in some cases. 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. If you are on MacOS and have renamed your drive, the benchmark will not be able to get your system specs. If I click the Extended test button, a pop-up error comes up alerting me to the missing media files. Overall Premiere Pro Performance Analysis . Nothing is really stopping us from adding 1080p, but it comes down to benchmark time vs reward. Eventually, it worked on the Windows side. 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. 2) Error: Could not get system information from //Volumes//Macintosh HD/usr/sbin/system_profiler SPDisplaysDataType . Built a new TR 3960X system and wanted to test it out. 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. One side is MacOS (Hackintosh) and the other is Windows 10. Right now, the benchmark is only compatible with Premiere Pro 2020. Have run Geek Bench and Cinebench and they seem better- i.e. Wow, I had no idea. This means Premiere will use the GPU for tasks like rendering, transcoding, and exporting; thus speeding up your system. We are however limited to PrPro 2019 only. No generated crash log from Premiere that I can see.. Just tried the extended benchmark 0.9 on the latest Permiere beta, 14.3.0.12 and the program crashes out without any error messages about half way through. system_profiler SPDisplayDataType (Display was missing the 's' to make it plural), swvers (you missed the underscore between the 'w' and the 'v'), 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: 144.0.0.0.0 SMC Version (system): 1.39f5 SMC Version (processor tray): 1.39f5, 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, ProductName: Mac OS XProductVersion: 10.13.6BuildVersion: 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. 3) Error: Could not get system information from //Volumes//Macintosh HD/usr/sw_vers . Also what do you suggest doing with location of disk cache when only 1 drive on the laptop...? The same applies to that lowbie WX 4100 sitting at the bottom – even if saw decent gains. Is there something I'm doing wrong? Due to the change in the test media, the overall scores are not interchangeable with previous benchmark versions. Using software encoding also provides more granularity in the options you can use, since options like two-pass encoding can not be used with GPU encoders. … Is this an error? If you see a result that seems a little strange, you can rest assured that it’s one we retested, because we can’t stomach being unsure about our test results. For accelerated rendering, select the Adobe rendering option for the Mercury … Hey guys, LOVE your benchmark test. Because premiere can't play these media files using hardware decoding, I'm not sure they're fair to use in the benchmark. Benchmark Results: Adobe Premiere Pro CS5 Page 1: GeForce GTX 580 Goes To Eleven Page 2: GF110: Nvidia Gives Fermi A Facelift Page 3: GeForce GTX 580: Similar Dimensions, Improved … The hardest thing is going to be getting the GPU to be passed through like you mentioned. As mentioned before, we plan to expand our Premiere Pro testing over time, and also plan to eventually move all of our tests to NVMe storage in lieu of SATA, and then possibly expand to make them a bit beefier, in hopes of seeing more interesting scaling. 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. There is no score screen in the latest version. There’s certainly no “one” way to measure Premiere Pro or Media Encoder performance. Here's a dropbox link: https://www.dropbox.com/s/4... That's odd... from everything I've seen, opening projects through the API like we are never has the "media offline" window come up. 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. I see that directory listed in the unzipped contents of the download. Can you give some more information? Hello! And can you toss me the status log file so u can see what was going on? Apparently installing plugins for Adobe products isn't as straight-forward as I thought it was. Advanced effects: Lumetri Color, Ultra Key, Sharpen, Gaussian Blur, Basic 3D, Directional Blur, and VR Digital Glitch. For each type of test media, we look at two test sequences: These tests are all used for live playback performance testing at Full and Half playback resolution. 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. It is in Project Settings -> Renderer . 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. Background . Thanks Matt. The last time I tried something like that, you had to use an NVIDIA Quadro/Grid or AMD Radeon (I think Pro?). Interesting results to say the least. 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 :-). Graphics card with at … Can you elaborate more on the system used with the 9900K? just gave this a try, and I can’t install Mac_Install_Benchmark.command on 16” MacBook Pro. Thanks, I just wanted to let you all know, have a great weekend! You can get a fuller look at the updates on Adobe’s official blog. ok I now saw the 3rd point in the description of the latest version. This should break less often on unusual or older system configurations. 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. 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). In other words, this unlocks the potential for a huge performance … Hi Matt, could you take a look why we get this error when running the benchmark? For a list of recommended graphic cards, see Recommended graphics cards for Adobe Premiere Pro… GPU-accelerated effect performance enhancements This tutorial shows how to identify accelerated effects, and to activate GPU support. 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. 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. Just to let you guys know that your project folder can't be renamed! Adobe Premiere Pro and Adobe Media Encoder can take advantage of available GPUs on your system to distribute the processing load between the CPU and the GPU to get better performance. This means that the Extended test scores will be slightly different than previous versions, but it shouldn't be by a huge amount, 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. Likewise, if it can only play back at half the FPS, the score would be "50". Support our efforts! I'm wondering if there's a permissions issue from the scripting attempting to write to a local drive without admin access? Premiere Pro is engineered to take advantage of the GPU. Just thought I'd follow up, seems to be fixed in 0.86, thanks! 16:40:28 - timestamp: 2-21-16-4016:40:28 - starttime: 2/21/2020 16:4016: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.2x10416:40:28 - Premiere Pro Benchmark: V0.86 BETA16:40:28 - Benchmark Name PugetBench for Premiere Pro V0.86 BETA (Pr 14.0.2x104)16:40:28 - Running from Benchmark_Project.prproj16:40:28 - Checking that all media files are present. Added "GPU Score" that is the average of the results from the "GPU Effects" tests. I have re-installed both Premiere versions running the cleaner after the uninstall. The overall numbers are modest considering the length of the clip isn’t too impressive, but at the same time, it’s nice to see most cards have done much better than real-time at both resolutions. in "Documents\PugetBench\Premiere Pro" there should be a series of timestamped folders. 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. I just uploaded a new zip file with the benchmark media uploading right now that should resolve the issue. What's the MacBook Pros secret sauce? Any theories why? Puget Systems is based in the Seattle suburb of Auburn, WA, and specializes in high-performance… Just to confirm, are the copies of the media being made at all, or are you saying you are manually making them? Neil Purcell (Lighting Cameraman / Camera Operator) for the 4K H.254 clips from his Panasonic GH5. comparing to the latest 0.2BETA? 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. When opening the Premiere project it seems there is a missing .psd file? A standardized Premiere benchmark is something I've wanted for a long time, thank you! 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. That will matter when your encode takes tens of minutes, or hours. The different benchmarks (Pr, Ae, Ps, etc.) We’re planning to explore additional performance angles in the future, including, of course, playback performance. Hi, can you please explain below queries :How are the standard score calculated ?which framework does this benchmark use ? Benchmark Setup.psd. 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. For now, here’s a quick look at our workstation PC specs and tested graphics cards: When we started exploring performance in Premiere Pro and Media Encoder 14.2, we felt compelled to do a special test using four different encoding configurations, but using the same hardware. The same window errors. I'll make sure that gets included in the next update. I'll jot down a bug report and see if I can replicate. 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.