Conversely, the RTX 2080 Ti gives us a look at top-end performance with an NVIDIA gaming GPU. The GTX 1660 Ti was included as it’s the top-end non-RTX GeForce based on Turing, while the RTX 2060 was included because it’s the lowest-end RTX GeForce based on Turing. Some gaming GPUs were tossed in for expanded testing, with specific reasons for each. NVIDIA GeForce & TITAN: Creative Ready 419.67īecause this article focuses on performance of a workstation application, all relevant CPUs and GPUs (that we have) are included for testing here. Here’s the basic specs of our test rigs and chosen processors:ĪMD Ryzen Threadripper 2990WX (32-core 3.0 GHz)ĪMD Ryzen Threadripper 2970WX (24-core 3.0 GHz)ĪMD Ryzen Threadripper 2950X (16-core 3.5 GHz)ĪMD Ryzen Threadripper 2920X (12-core 3.5 GHz)ĪMD X470: ASUS ROG CROSSHAIR VII HERO Wi-Fi MAGIX Vegas Pro 16 - Median Filter Project
The Median test continues on to our CPU encode tests. To then get the GPU to do real work, two more projects are used: one with a LUT filter, and another with Median. To gauge basic AVC and HEVC encode performance, an identical scene is encoded to both on all GPUs. We use a few different projects for both our encode and playback tests. The fact that performance is decent on GeForce but abysmal on Quadro and TITAN by default suggests a basic fix shouldn’t be that difficult.
We’re not well-versed enough in MAGIX’s or NVIDIA’s software designs to comment much more, but we feel like the ultimate fix has to come by way of an update to NVIDIA’s driver. An encode that might have been 2m 30s originally, for example, would become 2m 36s. This was consistent across multiple GPUs. After adding the profile, our LUT and playback performance improved, but every other encode suffered a small drop in performance. Given this bizarre behavior, it seems like it might make sense to have NVIDIA automatically add Vegas as a profile, and it probably should… but adding this profile actually comes with a caveat. The kicker? You can keep every single setting in this new profile as “Use global setting”. Encode times of 900 seconds dropped to 300, and 5 FPS playback changed to 60 FPS. We hate to show a “broken” performance graph, but it’s important to highlight because the issue continues to survive.Īfter simply adding the Vegas profile to the NVIDIA Control Panel, the issue of poor LUT performance disappeared. We continued to talk with both companies multiple times since December, but nothing improved on the performance front.Īfter putting twenty graphics cards through the gauntlet of revised tests, more was revealed about the issue. Something seemed broken, so we reached out to MAGIX and NVIDIA to figure out what was going on. Instead of 60 FPS playback with a LUT FX filter, we instead saw 1~5 FPS. We overhauled our test scripts, and got back to work on performance testing – only to run into an immediate roadblock.įrom the get-go, AMD Radeon GPUs had no problems in our testing, but the story was different for NVIDIA. Work on this article began in December, following publication of our Radeon Pro WX 8200 review and a some good feedback from the community. We conducted follow-up testing with this version, and have found that the issues detailed here continue to persist. Considerations & Potential Performance RoadblocksĪpril 30 Addendum: One day after this article was published, MAGIX released the fifth major update to Vegas Pro 16, build 424. If you have suggestions on further improving our Vegas tests, please leave a comment. We benchmark with about 25 pieces of software, and we’re masters of very few. We’re not going to claim that the performance testing seen on this page is the best it can be, but it’s improving over time, as we become more familiar with the software.