{"id":14637,"date":"2023-11-02T10:12:02","date_gmt":"2023-11-02T17:12:02","guid":{"rendered":"https:\/\/www.pugetsystems.com\/?post_type=pugetbench_landing&#038;p=14637"},"modified":"2026-01-07T11:54:11","modified_gmt":"2026-01-07T19:54:11","slug":"premiere-pro","status":"publish","type":"pugetbench_landing","link":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/","title":{"rendered":"Puget Bench for Premiere Pro"},"content":{"rendered":"\n<div class=\"wp-block-cover full-width-no-gap\" style=\"min-height:361px;aspect-ratio:unset;\"><img loading=\"lazy\" decoding=\"async\" width=\"2560\" height=\"800\" class=\"wp-block-cover__image-background wp-image-15797\" alt=\"Video Editing Workflow Page Header\" src=\"https:\/\/wp-cdn.pugetsystems.com\/2022\/08\/Video-Editing-Header.png\" style=\"object-position:10% 50%\" data-object-fit=\"cover\" data-object-position=\"10% 50%\"\/><span aria-hidden=\"true\" class=\"wp-block-cover__background has-background-dim-0 has-background-dim\"><\/span><div class=\"wp-block-cover__inner-container is-layout-flow wp-block-cover-is-layout-flow\"><div class=\"wp-bootstrap-blocks-container container mb-2 px-4\">\n\t\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-9d6595d7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:61%\">\n<h1 class=\"wp-block-heading has-text-align-left puget-header-shadow text-left\" id=\"h-puget-bench-for-premiere-pro\">Puget Bench for Premiere Pro<\/h1>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"has-text-align-left puget-header-shadow\"><strong>Our benchmarks are designed in partnership with hardware and software industry leaders, as well as end users and influencers who use Premiere Pro daily, to ensure that they are representative of real-world workflows.<\/strong><\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-buttons is-content-justification-left is-layout-flex wp-container-core-buttons-is-layout-fdcfc74e wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link has-black-color has-white-background-color has-text-color has-background wp-element-button\" href=\"\/pugetbench\/creators\/#download-section\" target=\"_blank\" rel=\"noreferrer noopener\"><strong>Download Now<\/strong><\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:39%\"><\/div>\n<\/div>\n\n<\/div>\n<\/div><\/div>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"has-text-align-center border rounded p-2 has-background\" style=\"background-color:#f2f2f2\"><strong>Quickly Jump To: <a href=\"#h-key-features\">Key Features<\/a> \u2022 <a href=\"#h-hardware-requirements\">Hardware Requirements<\/a> \u2022 <a href=\"#h-test-breakdown\">Test Breakdown<\/a> \u2022 <a href=\"#h-how-does-the-scoring-work\">Scoring<\/a> \u2022 <a href=\"#h-benchmark-update-log\">Update Log<\/a> \u2022 <a href=\"#h-legacy-benchmark-versions\">Legacy &amp; Beta Versions<\/a><\/strong><\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>Puget Bench for Premiere Pro runs on top of your installed copy of Adobe Premiere Pro, providing benchmark data directly from the application. Our benchmarks are designed in partnership with hardware and software industry leaders, as well as end users and influencers who use Premiere Pro daily, to ensure that they are representative of real-world workflows.<\/p>\n\n\n<div class=\"alert alert-danger border border-danger rounded puget-wp-alert\" role=\"alert\">\n\t<p>Premiere Pro 25.3 has blocked the ability to export to HEVC via scripting, which prevents our benchmark from completing. We are working on a new version (currently 2.0.5-beta), which is available for licensed users. For more information, please review the <a href=\"#h-beta-benchmark-branch\">Beta Benchmark Branch notes<\/a>.<\/p><\/div>\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-9d6595d7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-top-cpu-results\">Top CPU Results<\/h2>\n\n\n\n<p class=\"has-text-align-center\"><a href=\"https:\/\/www.pugetsystems.com\/pugetbench\/results\/compare\/Puget%20Bench%20for%20Premiere%20Pro\/\">Compare other CPUs<\/a><\/p>\n\n\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-top-gpu-results\">Top GPU Results<\/h2>\n\n\n\n<p class=\"has-text-align-center\"><a href=\"https:\/\/www.pugetsystems.com\/pugetbench\/results\/compare\/Puget%20Bench%20for%20Premiere%20Pro\/\">Compare other GPUs<\/a><\/p>\n\n\n<\/div>\n<\/div>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-key-features\">Key Features<\/h2>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-9d6595d7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column p-1 is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:33.33%\"><div class=\"wp-block-image\">\n<figure class=\"aligncenter size-thumbnail is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"150\" height=\"150\" src=\"https:\/\/wp-cdn.pugetsystems.com\/2022\/08\/Adobe-Premiere-Pro-CC-Icon.png\" alt=\"Adobe Premiere Pro CC Icon\" class=\"wp-image-14357\" style=\"object-fit:cover;width:100px;height:100px\"\/><\/figure><\/div>\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-center\" id=\"h-realistic-testing\">Realistic Testing<\/h3>\n\n\n\n<div style=\"height:10px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"has-text-align-center\">Interfaces with Adobe Premiere Pro and benchmarks real-world codecs &amp; effects.<\/p>\n<\/div>\n\n\n\n<div class=\"wp-block-column p-1 is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:33.34%\"><div class=\"wp-block-image\">\n<figure class=\"aligncenter size-thumbnail is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"150\" height=\"150\" src=\"https:\/\/wp-cdn.pugetsystems.com\/2023\/05\/Checklist.png\" alt=\"Checklist Icon in Puget Colors\" class=\"wp-image-14540\" style=\"object-fit:cover;width:100px;height:100px\"\/><\/figure><\/div>\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-center\" id=\"h-comprehensive\">Comprehensive<\/h3>\n\n\n\n<div style=\"height:10px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"has-text-align-center\">Provides a detailed analysis of results across multiple tests <a href=\"#h-test-breakdown\">outlined below<\/a>.<\/p>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:33.33%\"><div class=\"wp-block-image\">\n<figure class=\"aligncenter size-thumbnail is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"150\" height=\"150\" src=\"https:\/\/wp-cdn.pugetsystems.com\/2022\/08\/screen-icon.png\" alt=\"Computer Screen Icon in Puget Systems Colors\" class=\"wp-image-12656\" style=\"object-fit:cover;width:100px;height:100px\"\/><\/figure><\/div>\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading has-text-align-center\" id=\"h-public-database\">Public Database<\/h3>\n\n\n\n<div style=\"height:10px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"has-text-align-center\">Compare your scores to thousands of other <a href=\"\/pugetbench\/results\/compare\/Puget%20Bench%20for%20Premiere%20Pro\/\">user-submitted results<\/a>.<\/p>\n<\/div>\n<\/div>\n\n\n\n<div style=\"height:10px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-cover is-light full-width\" style=\"min-height:350px;aspect-ratio:unset;\"><span aria-hidden=\"true\" class=\"wp-block-cover__background has-background-dim-100 has-background-dim\" style=\"background-color:#f2f2f2\"><\/span><div class=\"wp-block-cover__inner-container is-layout-flow wp-block-cover-is-layout-flow\"><div class=\"wp-bootstrap-blocks-container container mb-2 px-4\">\n\t\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-center has-text-color\" id=\"h-hardware-requirements\" style=\"color:#130c64\">Hardware Requirements<\/h2>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<div class=\"wp-block-columns is-layout-flex wp-container-core-columns-is-layout-9d6595d7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<h3 class=\"wp-block-heading has-text-color\" id=\"h-windows\" style=\"color:#130c64\">Windows<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Adobe Premiere Pro 23.3-25.2<\/li>\n\n\n\n<li>Intel, AMD, or ARM CPU meeting the <a href=\"https:\/\/helpx.adobe.com\/premiere-pro\/system-requirements.html\">System Requirements for Premiere Pro<\/a><\/li>\n\n\n\n<li>32GB of RAM recommended \u2013 you are likely to receive a lower than normal score with lower amounts of RAM<\/li>\n\n\n\n<li>Discrete GPU with &gt;4GB of VRAM (Standard preset) or &gt;8GB of VRAM (Extended preset)<\/li>\n\n\n\n<li>Compatible with both Windows 10 &amp; 11<\/li>\n\n\n\n<li>Premiere Pro\/OS language must be set to English<\/li>\n<\/ul>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-layout-flow wp-block-column-is-layout-flow\">\n<h3 class=\"wp-block-heading has-text-color\" id=\"h-macos\" style=\"color:#130c64\">MacOS<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Adobe Premiere Pro version 23.3-25.x<\/li>\n\n\n\n<li>32GB of RAM recommended \u2013 you are likely to receive a lower than normal score with lower amounts of RAM<\/li>\n\n\n\n<li>MacOS 13<\/li>\n\n\n\n<li>Premiere Pro\/OS language must be set to English<\/li>\n<\/ul>\n<\/div>\n<\/div>\n\n<\/div>\n<\/div><\/div>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-test-breakdown\">Test Breakdown<\/h2>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>Our Premiere Pro benchmark is broken down into three categories:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Encoding &#8211; performance when exporting to various codecs<\/li>\n\n\n\n<li>Processing &#8211; performance when working with different types of source media<\/li>\n\n\n\n<li>GPU Effects &#8211; performance for the most common GPU-accelerated effects in Premiere Pro<\/li>\n<\/ol>\n\n\n\n<p>Currently, we are using the export\/render process in Premiere Pro as a basis for all of our tests. In the past, we include Live Playback directly, but it is too inconsistent to use as a basis for a benchmark. For all tests, the measured FPS is calculated based on the number of frames rendered, divided by the render time as recorded in the Premiere Pro log file.<\/p>\n\n\n\n<p>The breakdown for each test below includes a &#8220;Processing Type&#8221; entry that indicates what hardware is the primary contributor to performance (Hardware Encoding\/Decoding, CPU, and GPU). This was determined by comparing results between an Intel Core i5 and Core i9 CPU, as well as an NVIDIA RTX __60 and RTX __80 GPU.<\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-encoding-tests\">Encoding Tests<\/h3>\n\n\n\n<p>For evaluating the performance of your system when exporting to various codecs, our benchmark is designed to make the encoding portion of a render as big of a bottleneck as possible.<\/p>\n\n\n\n<p>To do this, we are using a source DNxHR LB 480&#215;270 clip, scaled up into a UHD (3840&#215;2160) timeline. DNxHR LB is a very easy codec to process (especially at this low of a resolution), and doesn&#8217;t have hardware decoding support on any platform, making it a good baseline codec to use. In order to make sure that each pixel is unique and prevent codecs like H.264 or HEVC from getting too &#8220;smart&#8221;, we are also applying a simple fractal noise PNG image (NOT the fractal noise effect) on top of the clip to ensure that we do not have any repeating pixels.<\/p>\n\n\n\n<p>From this UHD timeline, we export to the range of codecs we want to test encoding performance for and calculate the FPS based on how long it takes relative to the number of frames rendered. While not a 100% pure encoding test (some resources are still being used to process the DNxHR clip, scale it, and process the noise overlay), this is about as close as a pure encoding test that we can do in Premiere Pro without getting into highly artificial setups.<\/p>\n\n\n\n<p>In total, we are currently testing the following export codecs:<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><thead><tr><th>Test Name<\/th><th>Codec Type<\/th><th>Benchmark Preset<\/th><th>Processing Type<\/th><th>Export Settings<\/th><\/tr><\/thead><tbody><tr><td><strong>H.264 50Mbps 8-bit UHD<\/strong><\/td><td>LongGOP<\/td><td>Standard, Extended<\/td><td>Hardware Encoder*<\/td><td>Format: H.264<br>Frame Size: UHD (3840 x 2160)<br>Performance: Hardware Encoding<br>Profile: High<br>Level: 5.2<br>Bitrate Encoding: VBR, 1 Pass<br>Target Bitrate [Mbps]: 50<\/td><\/tr><tr><td><strong>HEVC 50Mbps 8-bit UHD<\/strong><\/td><td>LongGOP<\/td><td>Standard, Extended<\/td><td>Hardware Encoder*<\/td><td>Format: HEVC (H.265)<br>Frame Size: UHD (3840 x 2160)<br>Performance: Hardware Encoding<br>Profile: Main<br>Level: 5.2<br>Tier: Main<br>Bitrate Encoding: VBR, 1 Pass<br>Target Bitrate [Mbps]: 50<br>Quality: Good<\/td><\/tr><tr><td><strong>HEVC 60Mbps 10-bit UHD<\/strong><\/td><td>LongGOP<\/td><td>Extended<\/td><td>Hardware Encoder*<\/td><td>Format: HEVC (H.265)<br>Frame Size: UHD (3840 x 2160)<br>Performance: Hardware Encoding<br>Profile: Main 10<br>Level: 5.2<br>Tier: Main<br>Bitrate Encoding: VBR, 1 Pass<br>Target Bitrate [Mbps]: 60<br>Quality: Good<\/td><\/tr><tr><td><strong>H.264 50Mbps 8-bit<\/strong><br><strong>(Software Encoding) UHD<\/strong><\/td><td>LongGOP<\/td><td>Standard, Extended<\/td><td>CPU<\/td><td>Format: H.264<br>Frame Size: UHD (3840 x 2160)<br>Performance: Software Encoding<br>Profile: High<br>Level: 5.2<br>Bitrate Encoding: VBR, 1 Pass<br>Target Bitrate [Mbps]: 50<\/td><\/tr><tr><td><strong>HEVC 50Mbps 8-bit<\/strong><br><strong>(Software Encoding) UHD<\/strong><\/td><td>LongGOP<\/td><td>Standard, Extended<\/td><td>CPU<\/td><td>Format: HEVC (H.265)<br>Frame Size: UHD (3840 x 2160)<br>Performance: Software Encoding<br>Profile: Main<br>Level: 5.2<br>Tier: Main<br>Bitrate Encoding: VBR, 1 Pass<br>Target Bitrate [Mbps]: 50<br>Quality: Good<\/td><\/tr><tr><td><strong>HEVC 60Mbps 10-bit<\/strong><br><strong>(Software Encoding) UHD<\/strong><\/td><td>LongGOP<\/td><td>Extended<\/td><td>CPU<\/td><td>Format: HEVC (H.265)<br>Frame Size: UHD (3840 x 2160)<br>Performance: Software Encoding<br>Profile: Main 10<br>Level: 5.2<br>Tier: Main<br>Bitrate Encoding: VBR, 1 Pass<br>Target Bitrate [Mbps]: 60<br>Quality: Good<\/td><\/tr><tr><td><strong>DNxHR LB UHD<\/strong><\/td><td>IntraFrame<\/td><td>Standard, Extended<\/td><td>CPU<\/td><td>Format: DNxHR\/DNxHD MXF OP1a<br>Resolution: DNxHR LB 8-bit<br>Frame Size: UHD (3840 x 2160)<\/td><\/tr><tr><td><strong>DNxHR SQ UHD<\/strong><\/td><td>IntraFrame<\/td><td>Standard, Extended<\/td><td>CPU<\/td><td>Format: DNxHR\/DNxHD MXF OP1a<br>Resolution: DNxHR SQ 8-bit<br>Frame Size: UHD (3840 x 2160)<\/td><\/tr><tr><td><strong>DNxHR HQX UHD<\/strong><\/td><td>IntraFrame<\/td><td>Extended<\/td><td>CPU<\/td><td>Format: DNxHR\/DNxHD MXF OP1a<br>Resolution: DNxHR HQX 10-bit<br>Frame Size: UHD (3840 x 2160)<\/td><\/tr><tr><td><strong>ProRes 422 Proxy UHD<\/strong><\/td><td>IntraFrame<\/td><td>Standard, Extended<\/td><td>CPU<\/td><td>Format: QuickTime<br>Video Codec: Apple ProRes 422 Proxy<br>Frame Size: UHD (3840 x 2160)<br>Depth: 8-bpc<\/td><\/tr><tr><td><strong>ProRes 422HQ UHD<\/strong><\/td><td>IntraFrame<\/td><td>Standard, Extended<\/td><td>CPU<\/td><td>Format: QuickTime<br>Video Codec: Apple ProRes 422 HQ<br>Frame Size: UHD (3840 x 2160)<br>Depth: 8-bpc<\/td><\/tr><tr><td><strong>ProRes 4444 UHD<\/strong><\/td><td>IntraFrame<\/td><td>Extended<\/td><td>CPU<\/td><td>Format: QuickTime<br>Video Codec: Apple ProRes 4444<br>Frame Size: UHD (3840 x 2160)<br>Depth: 16-bpc<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\"><em>* If available. Falls back to CPU if not.<\/em><\/figcaption><\/figure>\n\n\n\n<p>If you wish to examine the settings in more detail, you can download the <a href=\"https:\/\/download.pugetsystems.com\/pugetbench\/misc\/PugetBench_Premiere_Pro_098_Export_Presets.zip\">export presets here<\/a>.<\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-processing-tests\">Processing Tests<\/h3>\n\n\n\n<p>On the opposite side of encoding, we are also evaluating how fast your system is able to decode different codecs in Premiere Pro. Unfortunately, the best way to test this in a real-world manner is to use live playback, which we can&#8217;t currently do for reasons explained in our Puget Bench for <a href=\"https:\/\/www.pugetsystems.com\/blog\/2023\/05\/04\/pugetbench-for-premiere-pro-0-98-testing-methodology\/\">Premiere Pro 0.98 Testing Methodology<\/a> post .<\/p>\n\n\n\n<p>For these processing tests, we use a wide range of codecs at different resolutions; creating a timeline at the clip&#8217;s native resolution. We then export each timeline to DNxHR LB at HD (1920&#215;1080) resolution. Similar to the encoding tests, we standardized on DNxHR LB for the export codec as it is a very easy codec to process and doesn&#8217;t have hardware decoding support on any platform.<\/p>\n\n\n\n<p>The only additional thing we do is disable the <code>ImporterMPEG.UseSWDecodeWhileEncoding<\/code> setting, which in the recent versions of Premiere Pro disables hardware decoding when exporting. This setting exists to address stability issues when using hardware decoding and encoding at the same time (which our benchmark is <em>not <\/em>doing). However, since we want to specifically test how good the system is at handling certain media with hardware decoding support, we are disabling it when running our tests. It is automatically set back to the default when the tests are finished.<\/p>\n\n\n\n<p>This method&#8217;s benchmark results are highly consistent and accurately reflect the relative performance between two systems when working with different codecs. The raw FPS results do tend to be higher than what you will see during live playback or preview since it does not include all the additional steps required for Premiere Pro to show the video in the preview monitor, but we found that the relative performance between two CPUs or GPUs largely aligns with relative performance during live playback.<\/p>\n\n\n\n<p>The base media we are currently testing is:<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><thead><tr><th>Test Name<\/th><th>Codec Type<\/th><th>Benchmark Preset<\/th><th>Processing Type<\/th><\/tr><\/thead><tbody><tr><td><strong>4K H.264 150Mbps 4:2:0 8-bit<\/strong><\/td><td>LongGOP<\/td><td>Standard, Extended<\/td><td>Hardware Decoder*<\/td><\/tr><tr><td><strong>4K HEVC 100Mbps 4:2:2 10-bit<\/strong><\/td><td>LongGOP<\/td><td>Extended<\/td><td>Hardware Decoder*<\/td><\/tr><tr><td><strong>8K HEVC 100Mbps 4:2:0 8-bit<\/strong><\/td><td>LongGOP<\/td><td>Extended<\/td><td>Hardware Decoder*<\/td><\/tr><tr><td><strong>4K ProRes 422 Proxy<\/strong><\/td><td>IntraFrame<\/td><td>Standard, Extended<\/td><td>CPU<\/td><\/tr><tr><td><strong>4K ProRes 422<\/strong><\/td><td>IntraFrame<\/td><td>Standard, Extended<\/td><td>CPU<\/td><\/tr><tr><td><strong>4K DNxHR LB<\/strong><\/td><td>IntraFrame<\/td><td>Standard, Extended<\/td><td>CPU<\/td><\/tr><tr><td><strong>4K DNxHR SQ<\/strong><\/td><td>IntraFrame<\/td><td>Standard, Extended<\/td><td>CPU<\/td><\/tr><tr><td><strong>4K Cinema RAW Light ST<\/strong><\/td><td>RAW<\/td><td>Extended<\/td><td>CPU<\/td><\/tr><tr><td><strong>4K ARRIRAW<\/strong><\/td><td>RAW<\/td><td>Extended<\/td><td>GPU<\/td><\/tr><tr><td><strong>5K Sony X-OCN<\/strong><\/td><td>RAW<\/td><td>Extended<\/td><td>CPU<\/td><\/tr><tr><td><strong>4K RED<\/strong><\/td><td>RAW<\/td><td>Standard, Extended<\/td><td>GPU<\/td><\/tr><tr><td><strong>8K RED<\/strong><\/td><td>RAW<\/td><td>Extended<\/td><td>GPU<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\"><em>* If available. Falls back to CPU if not.<\/em><\/figcaption><\/figure>\n\n\n<div class=\"alert alert-info border border-info rounded puget-wp-alert\" role=\"alert\">\n\t<p>Special thanks to those who have helped us by providing test clips!<\/p>\n<ul>\n<li><a href=\"https:\/\/web.archive.org\/web\/20230112014451\/https:\/\/www.linusmediagroup.com\/\"><strong>Linus Media Group<\/strong><\/a> for the 4K and 8K RED clips which were also transcoded to create the HEVC, and ProRes clips.<\/li>\n<li><strong><a href=\"https:\/\/web.archive.org\/web\/20230112014451\/http:\/\/neilpurcell.co.uk\/\">Neil Purcell (Lighting Cameraman \/ Camera Operator)<\/a><\/strong> for the 4K H.264 clips from his Panasonic GH5.<\/li>\n<\/ul><\/div>\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-gpu-effects-tests\">GPU Effects Tests<\/h3>\n\n\n\n<p>The last category of tests looks at performance for GPU-accelerated effects. Many of the effects in Premiere Pro are relatively easy to process singularly, so applying just a single instance isn&#8217;t going to stress even a low-end GPU. To address this, we apply each effect anywhere from four, to forty, times.<\/p>\n\n\n\n<p>As a base, we are using a DNxHR LB UHD (3840&#215;2160) clip, and export to DNxHR LB HD (1920&#215;1080) &#8211; just like the &#8220;4K DNxHR LB&#8221; processing test. The difference here is that we also apply the following effects for each test:<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-stripes\"><table><thead><tr><th>Test Name<\/th><th>Benchmark Preset<\/th><th>Processing Type<\/th><\/tr><\/thead><tbody><tr><td><strong>Lumetri Color x40<\/strong><\/td><td>Standard, Extended<\/td><td>GPU<\/td><\/tr><tr><td><strong>Gaussian Blur x40<\/strong><\/td><td>Standard, Extended<\/td><td>GPU<\/td><\/tr><tr><td><strong>Sharpen x40<\/strong><\/td><td>Standard, Extended<\/td><td>GPU<\/td><\/tr><tr><td><strong>VR Digital Glitch x20<\/strong><\/td><td>Extended<\/td><td>GPU<\/td><\/tr><tr><td><strong>VR De-Noise x4<\/strong><\/td><td>Extended<\/td><td>GPU<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\"><em>* If available. Falls back to CPU if not.<\/em><\/figcaption><\/figure>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-how-does-the-scoring-work\">How does the Scoring Work?<\/h2>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>All of the scores in our Premiere Pro benchmark are calculated using geometric means rather than averages or performance relative to a reference result. This helps to normalize the scores so that larger or small results are not unfairly weighted. It also allows for the benchmark to be more flexible and better able to handle large performance shifts due to either application optimizations or the launch of more powerful hardware.<\/p>\n\n\n\n<p>For the actual score calculations, we start by dividing the tests by codec and whether it is an encoding- or processing-based test. A score is generated for each group by taking the geometric mean of all the test results. This score is not logged, and is only used behind the scenes to calculate the major scores.<\/p>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-test-group-scores-not-logged\">Test Group Scores (not logged)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>LongGOP Encoding Score = geomean (LongGOP Encoding test1, LongGOP Encoding test2, ...)\nLongGOP Processing Score = geomean (LongGOP Processing test1, LongGOP Processing test2, ...)\nIntraFrame Encoding Score = geomean (IntraFrame Encoding test1, IntraFrame Encoding test2, ...)\nIntraFrame Processing Score = geomean (IntraFrame Processing test1, IntraFrame Processing test2, ...)\nRAW Processing Score = geomean (RAW Processing test1, RAW Processing test2, ...)\nGPU Effects Processing Score = geomean (GPU test1, GPU test2, ...)<\/code><\/pre>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-major-scores\">Major Scores<\/h3>\n\n\n\n<p>The group scores are combined into the LongGOP, IntraFrame, RAW, and GPU Effects scores. For LongGOP and IntraFrame, this is done by calculating the geometric mean of the encoding and processing scores. RAW and GPU Effects scores, however, are used as-is since there are no encoding-based tests for RAW or GPU Effects. Each score is multiplied by a different scoring coefficient to bring the scores across all our benchmarks roughly in line with each other.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>LongGOP Score = geomean (LongGOP Encoding Score, LongGOP Processing Score) * 0.95\nIntraFrame Score = geomean (IntraFrame Encoding Score, IntraFrame Processing Score) * 0.91\nRAW Score = RAW Processing Score * 2.12\nGPU Effects Score = GPU Effects Processing Score * 1.18<\/code><\/pre>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-overall-score\">Overall Score<\/h3>\n\n\n\n<p>These major scores are then combined into the Overall Score using a geometric mean and multiplied by 100 to differentiate the Overall Score from the Major Scores. Currently, we do not weigh any of the major scores more than any of the others, so each contributes equally to the Overall Score.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Overall Score = geomean (LongGOP Score, IntraFrame Score, RAW Score, GPU Effects Score) * 100<\/code><\/pre>\n\n\n\n<p>This method results in an Overall Score with a typical run-to-run variance of about 1-2%, and Major Scores with a variance of about 5%. Assuming there is no thermal or other performance throttling occurring on the system.<\/p>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-benchmark-groups\">Benchmark Groups<\/h2>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>Results in the <a href=\"https:\/\/www.pugetsystems.com\/pugetbench\/results\/compare\/PugetBench%20for%20Premiere%20Pro\/\">Puget Bench public benchmark database<\/a> are grouped according to the benchmark and application version in order to maintain a balance of performance consistency and sample size. For example, if we are forced to change our benchmark to add, remove, or change a test, we do not want to group the results with those from a different benchmark version. More commonly, however, is that there is a change in the host application (Premiere Pro, Photoshop, etc.) that affects performance. This could be an update that improves GPU usage or changes how effects are processed, which can throw off comparisons.<\/p>\n\n\n\n<p>At the same time, we try not to split results into too many small groups. Having more results in each group makes the data more useful\u2014it smooths out odd scores and gives you a better idea of how different hardware stacks up.<\/p>\n\n\n\n<p>Currently, for Premiere Pro, we have the following score groups:<\/p>\n\n\n\n<p><strong>Premiere Pro 25.1-25.2 | Puget Bench for Premiere Pro 1.0.0-1.1.1<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In Premiere Pro 25.1, Adobe changed the behaviour for selecting the device to use for hardware decoding of H.264 media. In the past, Intel GPUs were given priority over NVIDIA and AMD. In 25.1, however, this was changed to NVIDIA given top priority, followed by AMD, then Intel.<\/li>\n\n\n\n<li>Since this can greatly affect the H.264 processing tests (especially on systems with NVIDIA Blackwell GPUs), a new benchmark group was determined to be required.<\/li>\n\n\n\n<li>HEVC hardware decoding is still Intel &gt; NVIDIA &gt; AMD.<\/li>\n\n\n\n<li>Encoding is similarly unchanged, and for both&nbsp;H.264 and HEVC is still NVIDIA &gt; AMD &gt; Intel.<\/li>\n<\/ul>\n\n\n\n<p><strong>Premiere Pro 23.0-25.0 | Puget Bench for Premiere Pro 1.0.0-1.1.1<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Initial Premiere Pro support<\/li>\n\n\n\n<li>No changes were made between Premiere Pro 23.0 and 25.0 that resulted in significant changes to system performance for the tasks our Premiere Pro benchmark examines.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-benchmark-update-log\">Benchmark Update Log<\/h2>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 1.1.1<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Set the supported Creators app version to 1.3.0-1.3.99<\/li>\n\n\n\n<li>No changes to the tests or scoring<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 1.1.0<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Added support for Premiere Pro 25.0-25.9<\/li>\n\n\n\n<li>No changes to the tests or scoring<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 1.0.1<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Set the supported Creators app version to 1.2.0-1.2.99<\/li>\n\n\n\n<li>Updates to support the new Creators app version<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 1.0.0 (Major Update)<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Major update \u2013 Results cannot be compared to previous benchmark versions.<\/li>\n\n\n\n<li>Increased scoring coefficient for the Overall Score to differentiate the score from previous benchmark versions.<\/li>\n\n\n\n<li>Added scoring coefficient modifiers to bring the Overall Score in-line with other 1.x PugetBench benchmarks.<\/li>\n\n\n\n<li>Added support for Premiere Pro 24.x<\/li>\n\n\n\n<li>Integrated into &#8220;PugetBench for Creators&#8221; benchmark application. The Premiere Pro benchmark is no longer available as a stand-alone Premiere Pro plugin.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.98.0 BETA (Major Update)<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Major update \u2013 Results cannot be compared to previous benchmark versions<\/li>\n\n\n\n<li>Minimum application support changed to Premiere Pro 23.3 due to changes in the internal API and significant application performance optimizations.<\/li>\n\n\n\n<li>Dropping live playback tests due to significant issues with run-to-run variation.<\/li>\n\n\n\n<li>Dropping &#8220;CPU Effects&#8221; tests as the majority of commonly used effects are now gpu-accelerated.<\/li>\n\n\n\n<li>No longer necessary for the Preview Window to be in a specific quadrant on Windows.<\/li>\n\n\n\n<li>No longer necessary to change Security &amp; Privacy settings on MacOS or allow Premiere Pro to control system events.<\/li>\n\n\n\n<li>Changing the &#8220;Export&#8221; tests to a new &#8220;Encoding&#8221; test set.\n<ul class=\"wp-block-list\">\n<li>These new tests focus on the encoding portion of an export.<\/li>\n\n\n\n<li>The tests are based on a DNxHR LB 480&#215;270 clip upscaled to UHD with an image overlay to ensure each pixel is unique.<\/li>\n\n\n\n<li>Timeline is exported to a range of codecs at UHD. <\/li>\n\n\n\n<li>Current export codecs include variations of H.264\/HEVC (with both software and hardware encoding), DNxHR, and ProRes.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Adding new &#8220;Processing&#8221; tests. These are intended to measure how good the system is at processing (decoding) different types of codecs.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>Tests are based on a timeline with a range of codecs at their native resolution with no effects.<\/li>\n\n\n\n<li>Timelines are exported to DNxHR LB at 1920&#215;1080. This allows the export to be primarily bottlenecked by how fast Premiere Pro is able to decode the source media.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Current source codecs include variations of H.264, HEVC, DNxHR, ProRes, RED, Cinema RAW Light, ARRIRAW, and X-OCN.<\/li>\n\n\n\n<li>Note: This test is indicative of how good your system is at working with these codecs, but the FPS results tend to be higher than what you will see during live playback \/ preview since it does not include all the additional steps required for Premiere Pro to show the video in the preview monitor.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Disabling &#8220;ImporterMPEG.UseSWDecodeWhileEncoding&#8221; setting for the Processing tests. This flag disables hardware decoding when exporting due to current stability issues in Premiere Pro when using hardware encoding and decoding at the same time. We are not doing this, so the issues are not a concern, and this makes our tests more in-line with behavior when playing media in the preview window.<\/li>\n\n\n\n<li>Adjusting export FPS measurements to be based on the export time recorded in the Premiere Pro log files. This should be a more &#8220;pure&#8221; measurement than simply timing how long the export functions in the plugin API take.\n<ul class=\"wp-block-list\">\n<li>This does require us to enable Premiere Pro logging, which we prompt the user to allow, and requires Premiere Pro to restart.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Adjusting GPU Effects tests to isolate specific effects rather than applying a melting pot of effects to a single clip. This doesn&#8217;t affect the relative scores for GPUs significantly, but allows us to drill down on specific effects during benchmark analysis.<\/li>\n\n\n\n<li>Changing the major scores (Live Playback, Export, Effects) to be based primarily on the codec being tested rather than the type of test, as that is what most often dictates what type of hardware will be best for different workflows. New major scores:\n<ul class=\"wp-block-list\">\n<li>LongGOP (H.264\/HEVC)<\/li>\n\n\n\n<li>IntraFrame (DNxHR\/ProRes)<\/li>\n\n\n\n<li>RAW (RED\/Cinema RAW Light\/ARRIRAW\/X-OCN)<\/li>\n\n\n\n<li>GPU Effects<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Changing all scores to be based on the geometric mean of the individual results (or major scores in the case of the Overall Score). This method helps to normalize the scores so that larger or small results are not unfairly weighted.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.95.7 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Updated CLI utility to support changes to plugin paths when installing via Creative Cloud<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.95.6 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Added plugin and CLI support for Premiere Pro 23.0<\/li>\n\n\n\n<li>Updated project files to support Premiere Pro 23.0<\/li>\n\n\n\n<li>Updated benchmark upload\/view URLs to match web hosting changes<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.95.5 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Added filter to remove \u201c(C)\u201d, \u201c(R)\u201d, and \u201c(TM)\u201d strings from the systems specifications<\/li>\n\n\n\n<li>Added additional granularity to the \u201cCustom\u201d preset. You can now select individual tests to run rather than only being limited to specific groups of tests.<\/li>\n\n\n\n<li>Added the ability to specify which tests to run with the \u201cCustom\u201d preset when using the CLI\n<ul class=\"wp-block-list\">\n<li>Include the \u201c\/custom_tests\u201d argument when launching the CLI along with a comma-separated list of test numbers.<\/li>\n\n\n\n<li>The test number associated with each test can be seen if you launch the benchmark plugin manually. It will be shown before the name of each selectable test.<\/li>\n\n\n\n<li>Example: \/custom_tests \u201c8,21\u201d<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Added \u201c\/cooldown\u201d CLI argument to specify how many seconds to wait at the end of the benchmark run to allow the system to cool down. By default, the CLI waits for 20 seconds\n<ul class=\"wp-block-list\">\n<li>Example: \/cooldown 60<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Added the ability to launch custom .bat files at various points during the benchmark run. This was requested multiple times in order to automate additional logging using utilities such as Windows Performance Recorder.\n<ul class=\"wp-block-list\">\n<li>If running the benchmark manually, there is now a \u201cRun custom commands\u201d checkbox in the automation settings<\/li>\n\n\n\n<li>If using the CLI, include the command line argument of \u201c\/custom_tests\u201d<\/li>\n\n\n\n<li>Four different .bat files are launched at the start\/end of the benchmark, and at the start\/end of each individual test.<\/li>\n\n\n\n<li>More information on how to make the .bat files, where to save them, and a sample set of files is available in the user guide<\/li>\n\n\n\n<li>Note that if the commands require admin privileges, you will need to launch the application or CLI as admin.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Required application information for the CLI moved to an .ini file that resides alongside the CLI in the plugin folder. This information was previously baked into the CLI itself, but by having it in an editable file, end users can add support for things like beta and pre-release versions of Premiere Pro. The .ini requires the following entries:\n<ul class=\"wp-block-list\">\n<li>Main section title: The major version of Premiere Pro. This is used by the CLI for the \u201c\/app_version\u201d argument<\/li>\n\n\n\n<li>prefLoc: Location of the application preferences folder<\/li>\n\n\n\n<li>prefFile: In many cases, this is the same as prefLoc, but some benchmarks need a specific preferences file defined<\/li>\n\n\n\n<li>appLoc: Path to the Premiere Pro application<\/li>\n\n\n\n<li>appEXE: Name of the Premiere Pro .exe when it has been launched<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.95.4 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Remade Benchmark_Project_22.prproj file in order to fix bug with Apple M1 devices.<\/li>\n\n\n\n<li>Fixed issue with \u201cBenchmark Complete\u201d dialog box showing the Standard Overall Score when the Extended preset is run.<\/li>\n\n\n\n<li>Updated spec gathering to include GPU core count for M1 devices.<\/li>\n\n\n\n<li>Fixed bug that prevented the benchmark from being run multiple times (we still highly recommend restarting Premiere Pro between benchmark runs, however).<\/li>\n\n\n\n<li>Switching to \u201cqe.project.getActiveSequence().player.totalFrames\u201d to get the number of total frames processed for Live Playback tests. Previously we just used the total number of frames in the sequence, but Pr 22.0 at times will process a frame multiple times. Especially on low-end systems, this can throw off the results since it makes it possible for Pr to drop a single frame more than once.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.95.3 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Added project files and CLI support for Premiere Pro version 22.x<\/li>\n\n\n\n<li>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 22.x are present.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.95.1 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Added project files and CLI support for Premiere Pro 2021 (15.x)<\/li>\n\n\n\n<li>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.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.95 BETA (Major Update)<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Major update \u2013 Results cannot be compared to previous benchmark versions<\/li>\n\n\n\n<li>Requires new project files due to significant changes to what is tested<\/li>\n\n\n\n<li>Added additional failsafes for when gathering of system specs fails<\/li>\n\n\n\n<li>Added spec gathering support for Apple M1 systems<\/li>\n\n\n\n<li>In some cases, playback can report more dropped frames than exist in the sequence. When this happens, the playback FPS will be reported as \u201c0\u201d<\/li>\n\n\n\n<li>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<\/li>\n\n\n\n<li>Test changes also significantly reduced the amount of time it takes to run the benchmark<\/li>\n\n\n\n<li>Scoring changed to be relative to a reference system (AMD Ryzen 5900X w\/ GeForce RTX 3080)<\/li>\n\n\n\n<li>Test changes:\n<ul class=\"wp-block-list\">\n<li>Dropped half resolution Live Playback tests<\/li>\n\n\n\n<li>Added 2x and 4x speed forward playback tests<\/li>\n\n\n\n<li>Increased ProRes multicam test to 6 streams<\/li>\n\n\n\n<li>Shortened all test sequences from 30 sec to 20 sec in length<\/li>\n\n\n\n<li>Export tests now use in\/out points so that we can shorten some tests (CPU effects test primarily)<\/li>\n\n\n\n<li>H.264 export tests now count towards the GPU score since it uses GPU encoding by default<\/li>\n\n\n\n<li>CPU &amp; 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<\/li>\n\n\n\n<li>Shortened CPU Effects export test to 1\/3 the length since this test can take a long time<\/li>\n\n\n\n<li>GPU\/CPU effects tests now have their own \u201cEffects\u201d category and sub-score<\/li>\n\n\n\n<li>Overall score is now the average of the \u201cLive Playback\u201d, \u201cExport\u201d, and \u201cEffects\u201d sub-scores<\/li>\n\n\n\n<li>Scoring now based on performance relative to a reference system (Ryzen 5900X w\/ RTX 3080) rather than relative to the media FPS<\/li>\n\n\n\n<li>Dropping 23.976 FPS media from Enhanced Extended tests. Extended will now only adds sequences with 8K 59.94FPS H.265 and R3D media<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>\u201cCustom\u201d 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.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p> <strong>Version 0.92 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>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<\/li>\n\n\n\n<li>Added GPU driver and motherboard BIOS to the system specs for Windows systems<\/li>\n\n\n\n<li>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)<\/li>\n\n\n\n<li>Misc bug fixes<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.91 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Improved system spec gathering reliability<\/li>\n\n\n\n<li>System specs on MacOS now gather properly even if the system drive\u2019s name has been changed from the default \u201cMacintosh HD\u201d<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.9 BETA (Major Update)<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Results are now uploaded to our&nbsp;<a href=\"https:\/\/www.pugetsystems.com\/benchmarks\/index.php\">online database<\/a>. This is required for the free version, but opt-in if you have a commercial license.<\/li>\n\n\n\n<li>Removed the temporary .csv logging from the free version now that the full results can be viewed on our benchmark listing page.<\/li>\n\n\n\n<li>Complete plugin UI revamp. Added status bar\/text, and improved the configuration options.<\/li>\n\n\n\n<li>Improved method used to gather system specs. This should break less often on unusual or older system configurations.<\/li>\n\n\n\n<li>License validation moved from the CLI utility to the plugin itself.<\/li>\n\n\n\n<li>Added the ability to do a \u201cCustom\u201d test which does the same tests as normal, only on whatever sequences are on the root-level of the currently opened project.<\/li>\n\n\n\n<li>Added ability to set the location for any disk-based tests (exporting).<\/li>\n\n\n\n<li>Added tooltips for the various settings that can now be configured.<\/li>\n\n\n\n<li>Status logs and configuration settings moved to \u201c~Documents\u29f5PugetBench\u29f5Premiere Pro\u29f5TIMESTAMP\u201d since we cannot log directly to the plugin folder.<\/li>\n\n\n\n<li>Dropped 8K H.265 tests. This test was simply too difficult for most systems and resulted in Premiere Pro hanging more often than not.<\/li>\n\n\n\n<li>Dropped ability to run tests in individual codecs. The intention is that the \u201cCustom\u201d test type will replace this.<\/li>\n\n\n\n<li>Improved CPU and GPU effects test. Added \u201cAdvanced\u201d and \u201cExtreme\u201d 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\u2019s performance for processing CPU and GPU effects<\/li>\n\n\n\n<li>Scoring has been adjusted based on the test changes. Due to this, the Overall Score will not be consistent with previous versions.<\/li>\n\n\n\n<li>General bug fixes and stability improvements.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.88 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Slight change in benchmark plugin folder name.<strong>&nbsp;Be sure to uninstall any existing \u201cPugetBench for Premiere Pro\u201d plugins before install the new 0.88 version.<\/strong><\/li>\n\n\n\n<li>Fixed issue where the benchmark would not run due to a change in the API when using confirm boxes.<\/li>\n\n\n\n<li>Added \u201cGPU Score\u201d that is the average of the results from the \u201cGPU Effects\u201d tests.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.86 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dropped the \u201cBenchmark Results\u201d score screen due to Premiere Pro 2020 breaking MGRT scripting functionality<\/li>\n\n\n\n<li>Adding back .csv log file support until we can get the \u201cBenchmark Results\u201d screen working<\/li>\n\n\n\n<li>No longer generating the test sequences on the fly \u2013 switching to pre-made projects for each test codec. This greatly increases the overall stability of the benchmark<\/li>\n\n\n\n<li>Due to using pre-made projects, Premiere Pro 2019 is no longer supported<\/li>\n\n\n\n<li>Improved system information gathering methods. This should make it much more reliable on MacOS<\/li>\n\n\n\n<li>Added option to continue the benchmark if the system information gathering does fail for any reason<\/li>\n\n\n\n<li>Miscellaneous bug fixes and improvements<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.8 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Renamed benchmark to \u201cPugetBench for Premiere Pro\u201d<\/li>\n\n\n\n<li>Added support for Premiere Pro 2020<\/li>\n\n\n\n<li>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\u2019t be by a huge amount<\/li>\n\n\n\n<li>There is now a \u201cBenchmark Results\u201d 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<\/li>\n\n\n\n<li>The benchmark also makes a PNG of the \u201cBenchmark Results\u201d screen for easy sharing<\/li>\n\n\n\n<li>Removed .csv log file support in the free edition (log files will be a feature in the commercial use version)<\/li>\n\n\n\n<li>Removed \u201cstart\u201d .exe applications (automation will be a feature in the commercial use version)<\/li>\n\n\n\n<li>More code to ensure consistency between benchmark runs<\/li>\n\n\n\n<li>Miscellaneous bug fixes and improvements<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.3 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Replaced H.264 media with footage straight from a Panasonic GH5 (Thanks&nbsp;<a href=\"http:\/\/neilpurcell.co.uk\/\">Neil Purcell<\/a>!)<\/li>\n\n\n\n<li>Replaced \u201cQuick\u201d preset with \u201cStandard\u201d preset. Changed tested media to 59.94FPS instead of 29.97FPS.\n<ul class=\"wp-block-list\">\n<li>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.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Separated media files into two groups: a \u201cStandard\u201d set and a \u201cFull\u201d set to make the download much more manageable for people just doing the Standard preset.<\/li>\n\n\n\n<li>Due to the change in the test media, the overall scores are not interchangeable with previous benchmark versions<\/li>\n<\/ul>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><strong>Version 0.2 BETA<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>First release.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-legacy-benchmark-versions\">Legacy Benchmark Versions<\/h2>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>Modern versions of our Premiere Pro benchmark are available via the Puget Bench for Creators application. However, older versions of the benchmark are available via ZXP plugins. Note that these versions may not have support for recent versions of Premiere Pro.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ver. 0.98.0 | <a href=\"https:\/\/download.pugetsystems.com\/PugetBench_PR_0.98.0.zip\">ZXP Plugin<\/a> | <a href=\"https:\/\/download.pugetsystems.com\/PugetBench_for_Premiere_Pro_0.98.zip\">Test Assets<\/a><\/li>\n\n\n\n<li>Ver. 0.95.6 | <a href=\"https:\/\/download.pugetsystems.com\/PugetBench_PR_0.95.6.zip\">ZXP Plugin<\/a> | <a href=\"https:\/\/download.pugetsystems.com\/PugetBench%20for%20Premiere%20Pro%200.95.6.zip\">Test Assets<\/a><\/li>\n\n\n\n<li>Ver. 0.95.5 |&nbsp;<a href=\"https:\/\/download.pugetsystems.com\/PugetBench_PR_0.95.5.zip\">ZXP Plugin<\/a>&nbsp;|&nbsp;<a href=\"https:\/\/download.pugetsystems.com\/PugetBench%20for%20Premiere%20Pro%200.95.4.zip\">Test Assets<\/a><\/li>\n\n\n\n<li>Ver. 0.95.4 |&nbsp;<a href=\"https:\/\/download.pugetsystems.com\/PugetBench_PR_Ver0.95.4.zip\">ZXP Plugin<\/a>&nbsp;|&nbsp;<a href=\"https:\/\/download.pugetsystems.com\/PugetBench%20for%20Premiere%20Pro%200.95.4.zip\">Test Assets<\/a><\/li>\n\n\n\n<li>Ver. 0.95.3 |&nbsp;<a href=\"https:\/\/download.pugetsystems.com\/PugetBench_PR_0.95.3.zip\">ZXP Plugin<\/a>&nbsp;|&nbsp;<a href=\"https:\/\/download.pugetsystems.com\/PugetBench%20for%20Premiere%20Pro%200.95.4.zip\">Test Assets<\/a><\/li>\n\n\n\n<li>Ver. 0.95.1 |&nbsp;<a href=\"https:\/\/www.mediafire.com\/file\/e64jrcq7iphxf1g\/PugetBench_PR_0.95.1.zip\/file\">ZXP Plugin<\/a>&nbsp;|&nbsp;<a href=\"https:\/\/www.mediafire.com\/file\/nsmfe6p3ovay8vc\/PugetBench_for_Premiere_Pro_0.95.1.zip\/file\">Test Assets<\/a><\/li>\n\n\n\n<li>Ver. 0.95 |&nbsp;<a href=\"http:\/\/https\/\/www.mediafire.com\/file\/tkr1sqrhvmwuwg1\/PugetBench_PR_0950.zip\/file\">ZXP Plugin<\/a>&nbsp;|&nbsp;<a href=\"https:\/\/www.mediafire.com\/file\/8fqgwjxvsj0fekl\/PugetBench_for_Premiere_Pro_0.95.0.zip\/file\">Test Assets<\/a><\/li>\n\n\n\n<li>Ver. 0.92 |&nbsp;<a href=\"https:\/\/www.mediafire.com\/file\/2v0347ar6oy7mg1\/PugetBench_for_Premiere_Pro.zip\/file\">ZXP Plugin + Standard Assets<\/a>&nbsp;|&nbsp;<a href=\"https:\/\/drive.google.com\/file\/d\/1_yVRYv2YB_tRUSGQG0hyplDWwKsFjDMY\/view?usp=sharing\">Extended Assets<\/a><\/li>\n<\/ul>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading has-text-align-center\" id=\"h-beta-benchmark-branch\">Beta Benchmark Branch<\/h2>\n\n\n\n<div style=\"height:20px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p>In addition to the main benchmark versions, licensed users also have access to a beta branch. This is where we trial tests, often to take advantage of new features added to the base applications. Beta branches are also where we add preliminary support for beta versions of Premiere Pro. <\/p>\n\n\n\n<p>These benchmark builds may include different tests and can have differences in how the scoring is calculated, so we recommend reading the update notes carefully to see if they can be used alongside the release versions of the benchmark.<\/p>\n\n\n\n<p>Current notes on the beta branch:<\/p>\n\n\n\n<p><strong>Version 2.0.5-beta<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Requirements:\n<ul class=\"wp-block-list\">\n<li>Premiere Pro 25.6.1 or newer<\/li>\n\n\n\n<li>Puget Bench for Creators 1.4.19 or newer<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Added a number of new tests to take advantage of new features in Premiere Pro, as well as to test multistream workflows\n<ul class=\"wp-block-list\">\n<li>Processing\n<ul class=\"wp-block-list\">\n<li>4K Nikon N-RAW<\/li>\n\n\n\n<li>4K H.264 150Mbps 420 8-bit 4x MultiStream<\/li>\n\n\n\n<li>4K HEVC 100Mbps 422 10-bit 4x MultiStream<\/li>\n\n\n\n<li>4K ProRes 422 4x MultiStream<\/li>\n\n\n\n<li>4K RED R3D 4x MultiStream<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Encoding\n<ul class=\"wp-block-list\">\n<li>H.264 10Mbps 8-bit HD<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>GPU Effects\n<ul class=\"wp-block-list\">\n<li>Echo Glow x3<\/li>\n\n\n\n<li>Bokeh Blur x2<\/li>\n\n\n\n<li>Edge Glow x3<\/li>\n\n\n\n<li>Wonder Glow x3<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Updated Tests\n<ul class=\"wp-block-list\">\n<li>All &#8220;Processing&#8221; and &#8220;GPU Effects&#8221; changed to utilize the Null Encoder at 3840&#215;2160 rather than exporting to DNxHR LB at 1920&#215;1080. This removes the encoding and writing to disk portion of the export, making it more accurate overall and closer analog to live playback performance. This changes the performance of these tests, so the results cannot be compared to the same tests in previous versions of the benchmark.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Adjusted Benchmark Presets\n<ul class=\"wp-block-list\">\n<li>Added &#8220;Processing &#8211; 4K Canon RAW&#8221; to the Standard preset (previously was only on Extended)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Dropped Tests\n<ul class=\"wp-block-list\">\n<li>Encoding\n<ul class=\"wp-block-list\">\n<li>HEVC 50Mbps 8-bit UHD (due to Premiere Pro no longer supporting exporting to HEVC via scripting)<\/li>\n\n\n\n<li>HEVC 60Mbps 10-bit UHD (due to Premiere Pro no longer supporting exporting to HEVC via scripting)<\/li>\n\n\n\n<li>H.264 50Mbps 8-bit (Software Encoding) UHD<\/li>\n\n\n\n<li>HEVC 50Mbps 8-bit (Software Encoding) UHD<\/li>\n\n\n\n<li>HEVC 60Mbps 10-bit (Software Encoding) UHD<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>GPU Effects\n<ul class=\"wp-block-list\">\n<li>Lumetri Color x40<\/li>\n\n\n\n<li>Gaussian Blur x40<\/li>\n\n\n\n<li>Sharpen x40<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Scoring Adjustments\n<ul class=\"wp-block-list\">\n<li>&#8220;Overall Score&#8221; modifier changed from 100 to 1000 in order to clearly differentiate the 2.x benchmark from previous versions.<\/li>\n\n\n\n<li>Subscores are now grouped according to the codec (H.264, HEVC, ProRes, etc.) rather than the test type (Processing, Encodings, etc.)<\/li>\n\n\n\n<li>&#8220;GPU Effects&#8221; subscore modifier changed to 7.6<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p><strong>Version 2.0.0-beta<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Due to a change by Adobe in Premiere Pro 25.3 and newer versions, all \u201cEncoding: HEVC [\u2026]\u201d tests have been removed. Details are further outlined in this post: <strong><a href=\"https:\/\/www.pugetsystems.com\/blog\/2025\/05\/21\/why-pugetbench-for-premiere-pro-is-dropping-hevc-encoding-tests\/\">Why PugetBench for Premiere Pro is Dropping HEVC Encoding Tests<\/a><\/strong><\/li>\n\n\n\n<li>Compatible with Premiere Pro 25.1 and newer.<\/li>\n\n\n\n<li>Because this significantly affects the tests and scoring, the major version has been changed from&#8221;1.x&#8221; to &#8220;2.x&#8221;.<\/li>\n\n\n\n<li>Since tests\/scoring is being forced to change, we are taking this opportunity to perform additional test adjustments:\n<ul class=\"wp-block-list\">\n<li>Dropped H.264 software encoding tests (we no longer hear anyone asking about this).<\/li>\n\n\n\n<li>Updated Cinema RAW Light and ARRIRAW export preset to better match the source framerate. This does not significantly change the relative performance of CPUs\/GPUs, but does change the raw result. <\/li>\n\n\n\n<li>Increased Overall Score modifier by 10x so that the scores are obviously different between 1.x and 2.x versions of the benchmark. A &#8220;typical&#8221; score will now be in the &#8220;100,000&#8221; range.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Note: The LongGOP Score in this beta build will be heavily skewed toward the performance of the remaining H.264 encoding test, since the codec type scores are currently based on a 50\/50 split between encoding and processing. We do not believe this accurately reflects real-world performance for users working with LongGOP media, and we are actively exploring alternate test\/scoring solutions that will be implemented in a future update.<\/li>\n\n\n\n<li>Additional benchmark changes are in process. If long-term score stability is desired, we do NOT recommend using this benchmark version.<\/li>\n<\/ul>\n\n\n\n<div style=\"height:40px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Puget Bench for Premiere Pro runs on top of your installed copy of Adobe Premiere Pro, providing benchmark data directly from the application.<\/p>\n","protected":false},"author":124,"featured_media":32856,"parent":14167,"menu_order":0,"template":"","meta":{"_acf_changed":false,"content-type":"","classic-editor-remember":"","legacy_id":"","redirect_url":[],"expire_date":"","alert_message":"","alert_link":[],"configure_ids":"","system_grid_title":"","system_grid_ids":"","footnotes":""},"coauthors":[9040],"class_list":["post-14637","pugetbench_landing","type-pugetbench_landing","status-publish","has-post-thumbnail","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.7 (Yoast SEO v26.7) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Puget Bench for Premiere Pro | Puget Systems<\/title>\n<meta name=\"description\" content=\"Puget Bench for Premiere Pro runs on top of your installed copy of Adobe Premiere Pro, providing benchmark data directly from the application.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Puget Bench for Premiere Pro\" \/>\n<meta property=\"og:description\" content=\"Puget Bench for Premiere Pro runs on top of your installed copy of Adobe Premiere Pro, providing benchmark data directly from the application.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/\" \/>\n<meta property=\"og:site_name\" content=\"Puget Systems\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/PugetSystems\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-07T19:54:11+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/wp-cdn.pugetsystems.com\/2024\/12\/PugetBench-for-Premiere-Pro-16_9.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1540\" \/>\n\t<meta property=\"og:image:height\" content=\"867\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:site\" content=\"@PugetSystems\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"24 minutes\" \/>\n\t<meta name=\"twitter:label2\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data2\" content=\"Matt Bach\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/\",\"url\":\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/\",\"name\":\"Puget Bench for Premiere Pro | Puget Systems\",\"isPartOf\":{\"@id\":\"https:\/\/www.pugetsystems.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/wp-cdn.pugetsystems.com\/2024\/12\/PugetBench-for-Premiere-Pro-16_9.png\",\"datePublished\":\"2023-11-02T17:12:02+00:00\",\"dateModified\":\"2026-01-07T19:54:11+00:00\",\"description\":\"Puget Bench for Premiere Pro runs on top of your installed copy of Adobe Premiere Pro, providing benchmark data directly from the application.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#primaryimage\",\"url\":\"https:\/\/wp-cdn.pugetsystems.com\/2024\/12\/PugetBench-for-Premiere-Pro-16_9.png\",\"contentUrl\":\"https:\/\/wp-cdn.pugetsystems.com\/2024\/12\/PugetBench-for-Premiere-Pro-16_9.png\",\"width\":1540,\"height\":867,\"caption\":\"PugetBench for Premiere Pro 16_9\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.pugetsystems.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Puget Bench\",\"item\":\"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Puget Bench for Premiere Pro\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.pugetsystems.com\/#website\",\"url\":\"https:\/\/www.pugetsystems.com\/\",\"name\":\"Puget Systems\",\"description\":\"Workstations for creators.\",\"publisher\":{\"@id\":\"https:\/\/www.pugetsystems.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.pugetsystems.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.pugetsystems.com\/#organization\",\"name\":\"Puget Systems\",\"url\":\"https:\/\/www.pugetsystems.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.pugetsystems.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.pugetsystems.com\/wp-content\/uploads\/2022\/08\/Puget-Systems-2020-logo-color-full.png\",\"contentUrl\":\"https:\/\/www.pugetsystems.com\/wp-content\/uploads\/2022\/08\/Puget-Systems-2020-logo-color-full.png\",\"width\":2560,\"height\":363,\"caption\":\"Puget Systems\"},\"image\":{\"@id\":\"https:\/\/www.pugetsystems.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/PugetSystems\",\"https:\/\/x.com\/PugetSystems\",\"https:\/\/www.instagram.com\/pugetsystems\/\",\"https:\/\/www.linkedin.com\/company\/puget-systems\",\"https:\/\/www.youtube.com\/user\/pugetsys\",\"https:\/\/en.wikipedia.org\/wiki\/Puget_Systems\"],\"telephone\":\"(425) 458-0273\",\"legalName\":\"Puget Sound Systems, Inc.\",\"foundingDate\":\"2000-12-01\",\"duns\":\"128267585\",\"naics\":\"334111\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Puget Bench for Premiere Pro | Puget Systems","description":"Puget Bench for Premiere Pro runs on top of your installed copy of Adobe Premiere Pro, providing benchmark data directly from the application.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/","og_locale":"en_US","og_type":"article","og_title":"Puget Bench for Premiere Pro","og_description":"Puget Bench for Premiere Pro runs on top of your installed copy of Adobe Premiere Pro, providing benchmark data directly from the application.","og_url":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/","og_site_name":"Puget Systems","article_publisher":"https:\/\/www.facebook.com\/PugetSystems","article_modified_time":"2026-01-07T19:54:11+00:00","og_image":[{"width":1540,"height":867,"url":"https:\/\/wp-cdn.pugetsystems.com\/2024\/12\/PugetBench-for-Premiere-Pro-16_9.png","type":"image\/png"}],"twitter_card":"summary_large_image","twitter_site":"@PugetSystems","twitter_misc":{"Est. reading time":"24 minutes","Written by":"Matt Bach"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/","url":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/","name":"Puget Bench for Premiere Pro | Puget Systems","isPartOf":{"@id":"https:\/\/www.pugetsystems.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#primaryimage"},"image":{"@id":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#primaryimage"},"thumbnailUrl":"https:\/\/wp-cdn.pugetsystems.com\/2024\/12\/PugetBench-for-Premiere-Pro-16_9.png","datePublished":"2023-11-02T17:12:02+00:00","dateModified":"2026-01-07T19:54:11+00:00","description":"Puget Bench for Premiere Pro runs on top of your installed copy of Adobe Premiere Pro, providing benchmark data directly from the application.","breadcrumb":{"@id":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#primaryimage","url":"https:\/\/wp-cdn.pugetsystems.com\/2024\/12\/PugetBench-for-Premiere-Pro-16_9.png","contentUrl":"https:\/\/wp-cdn.pugetsystems.com\/2024\/12\/PugetBench-for-Premiere-Pro-16_9.png","width":1540,"height":867,"caption":"PugetBench for Premiere Pro 16_9"},{"@type":"BreadcrumbList","@id":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/premiere-pro\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.pugetsystems.com\/"},{"@type":"ListItem","position":2,"name":"Puget Bench","item":"https:\/\/www.pugetsystems.com\/pugetbench\/creators\/"},{"@type":"ListItem","position":3,"name":"Puget Bench for Premiere Pro"}]},{"@type":"WebSite","@id":"https:\/\/www.pugetsystems.com\/#website","url":"https:\/\/www.pugetsystems.com\/","name":"Puget Systems","description":"Workstations for creators.","publisher":{"@id":"https:\/\/www.pugetsystems.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.pugetsystems.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.pugetsystems.com\/#organization","name":"Puget Systems","url":"https:\/\/www.pugetsystems.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.pugetsystems.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.pugetsystems.com\/wp-content\/uploads\/2022\/08\/Puget-Systems-2020-logo-color-full.png","contentUrl":"https:\/\/www.pugetsystems.com\/wp-content\/uploads\/2022\/08\/Puget-Systems-2020-logo-color-full.png","width":2560,"height":363,"caption":"Puget Systems"},"image":{"@id":"https:\/\/www.pugetsystems.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/PugetSystems","https:\/\/x.com\/PugetSystems","https:\/\/www.instagram.com\/pugetsystems\/","https:\/\/www.linkedin.com\/company\/puget-systems","https:\/\/www.youtube.com\/user\/pugetsys","https:\/\/en.wikipedia.org\/wiki\/Puget_Systems"],"telephone":"(425) 458-0273","legalName":"Puget Sound Systems, Inc.","foundingDate":"2000-12-01","duns":"128267585","naics":"334111"}]}},"_links":{"self":[{"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/pugetbench_landing\/14637","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/pugetbench_landing"}],"about":[{"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/types\/pugetbench_landing"}],"author":[{"embeddable":true,"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/users\/124"}],"version-history":[{"count":3,"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/pugetbench_landing\/14637\/revisions"}],"predecessor-version":[{"id":42818,"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/pugetbench_landing\/14637\/revisions\/42818"}],"up":[{"embeddable":true,"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/pugetbench_landing\/14167"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/media\/32856"}],"wp:attachment":[{"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/media?parent=14637"}],"wp:term":[{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.pugetsystems.com\/wp-json\/wp\/v2\/coauthors?post=14637"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}