To give a rough idea of how performance can be impacted with these new optimizations, MAGIX gave us an in-house test result that saw 1.6 FPS boost to 11.5 FPS in an HDR 10 / 32-bit project, using Preview/Full as the quality setting, when compared to Vegas Pro 16’s most up-to-date build. Intel’s HEVC decoding has also been given some polish, and should offer some performance improvements in both encode and playback. On a similar topic, MAGIX has improved HDR / ACES workflows and uses the GPU to accelerate the OpenColorIO code. We have more comments on this in the playback performance section. The ultimate goal here is improved playback performance. That means if you have NVIDIA, you will need to hit-up the File I/O tab in the settings and change to the appropriate setting in the drop-down menu at the bottom. MAGIX told us that its development timeline didn’t align with AMD’s this go-around, but adding support is a current top priority.īy default, VP17 will select Intel QSV for its decoder, even if it doesn’t exist in the system.
Speaking of AMD, it’s important to note that AMD’s Radeon ‘Navi’ RX 5700-series GPUs are officially unsupported for the moment, but like AMD’s decoder, Navi support is also being worked on. We’d expect the next software update to add support for AMD’s decoder.
Another addition to this version is GPU-accelerated decoding for AVC and HEVC, although at the current time, this implementation only works with Intel QSV and NVIDIA NVDEC. There are a couple of specific performance-related changes that should be noted in VP17. In addition to performance polish and lots of under-the-hood tweaks, MAGIX also introduces a number of useful features, such as Nested Timeline, a unified color-grading workflow, HLG HDR color support, 8K resolution and high-DPI support, and a lot more that can be explored on the product comparison page. Earlier this month, MAGIX released the latest major version of its popular video editor: Vegas Pro 17.
0 kommentar(er)
