Vegas Performance vrs Quality

Howard-Vigorita wrote on 9/20/2022, 5:51 PM

Since one of the developers let it drop that there's a new hevc decoder in the works, I decided to get ready by doing a bunch of transcodes with Vegas 19 to use as a basis of comparison. My results so far are in a google sheet here:

https://docs.google.com/spreadsheets/d/1dc7RIX4nKP1HfY2NFajQXEKxLxHj3Mfs/edit?usp=sharing&ouid=104047049686489929918&rtpof=true&sd=true

I used a lossless hevc clip I shot with my a ZcamE2 as the source for all the transcodes and quality comparisons. I used the ffmetrics tool to take all the measurements listing all 3 of the metrics it reports. For consistency with vmaf measurements I've done in the past, I used the latest N4.4 release version of ffmpeg from BtbN to power ffmetrics. Since the decoder is the root of all quality, I ran a bunch of different encodes for analysis. Looking forward to repeating these with vp20 as soon as the new decoder gets here. In the meanwhile, some of the results I got unexpectedly go against common wisdom.

Comments

DrinkyBird wrote on 9/20/2022, 8:25 PM

I believe the "new" encoder has been here a while... if you read the rest of the thread linked then it's evident the developer was talking about disabling the "Enable legacy HEVC decoding" in the File IO settings by default. So do that and enjoy the HEVC encoder in question.

OS: Windows 10 20H2
CPU: Ryzen 7 2700X
RAM: 32GB DDR4-3000
GPU: NVIDIA GeForce RTX 3060 Ti Founders Edition 8GB
Storage: Samsung 970 EVO Plus 1TB, Samsung SSD 870 QVO 2TB, Seagate FireCuda 2TB, Seagate BarraCuda 4TB
Sound: Creative Sound Blaster Z SE

RogerS wrote on 9/20/2022, 8:35 PM

The thread was about significant developments to the "new" HEVC decoder so it could become the default. I hope that happens soon as neither option today is great.

Quick read of these results suggests it's worse for quality than legacy HEVC and performance is similar.

I'm puzzling over how the legacy decoder with Mainconcept encoding is faster than the new decoder with Mainconcept and also faster than encoding with VCE or QSV. Why would that be?

Howard-Vigorita wrote on 9/20/2022, 9:03 PM

I'm puzzling over how the legacy decoder with Mainconcept encoding is faster than the new decoder with Mainconcept and also faster than encoding with VCE or QSV. Why would that be?

Keep in might I've only done the tests with vp19 so far. So unless they updated the decoder some time ago, it's probably not reflected in these charts.

I'm mystified about the MainConcept performance too. I did notice a large amount of copy utilization in the Amd gpu and figure that might be speeding things up and lowering the quality.

todd-b wrote on 9/20/2022, 11:44 PM

@Howard-Vigorita are you able to upload that file, or re-link it if it's the same one you were using for testing a while ago?

Howard-Vigorita wrote on 9/21/2022, 7:14 AM

It's the same one... linked at the bottom of my signature.

todd-b wrote on 9/21/2022, 7:07 PM

@Howard-Vigorita Your file breaks the Vegas GPU decoder like no other file I"ve seen when I play on timeline FULL/BEST. Do you see the same with your decoders with Vegas, when you compare with another NLE or a media player. Vegas looks to be using 40% of my rtx3080 doing nothing, looks to be a product of the broken GPU decoding. Throwing away 40% of the GPU processing power effectively downrating the GPU to a rtx3060

 

 

Howard-Vigorita wrote on 9/21/2022, 7:48 PM

Ha, ha, I wouldn't try to play it without a proxy. I occasionally shoot zraw and it's the only lossless format output by the zcam converter that Vegas can decode. Which it actually handles pretty well. If you want to blow up Vegas and just about any other player, try feeding it near-lossless avc. I only use that clip to evaluate decoders and encoders.

todd-b wrote on 9/21/2022, 7:57 PM

It's a good file for the Vegas Staff to test their new decoder with.

Gid wrote on 9/21/2022, 9:48 PM

I see you've put a comment in the Suggestions For Ways VEGAS Can Improve post, 👍

This is what it did to my PC, It never really played more than 1 or 2 frames per minute (not fps) even tho it said 29.97 the image wasn't moving,

Adobe AE cached as quick as any other file & played flawlessly.

Vegas Pro 20
Vegas Pro/Post 19 (Latest build), HitFilm Pro,  
Magix Movie Studio Platinum 2023 - from 2004-ish - Latest version,
Magix VPX14
Adobe After Effects
Boris Continuum & Sapphire, 
Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, 
Boris Optics,
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans

I'm 54, I've been a UK joiner for 38yrs, apprentice trained & time served, I make videos about my work & post them on Youtube so that i can share what I've learnt over the yrs,
https://www.youtube.com/c/Gidjoiner

At the moment my filming is done with a Samsung Galaxy S21 Ultra 5G
 

todd-b wrote on 9/22/2022, 1:12 AM

@Gid Same playback, usual problem, single thread GPU decoding, BUT, unlike most HEVC files Vegas uses multi-threaded decoding for encoding, In a way @Howard-Vigorita this is a bad file to be testing with as it doesn't represent the behavior of the usual HEVC file in Vegas with GPU decoding

The other unusual thing is how much CPU it's using for an NVENC encode. Resolve uses 13% CPU and encodes at 67fps, but Vegas uses 75% CPU for 42fps . I guess that means even if they just fix this GPU decoder to allow multithreaded GPU decoding on playback as long as the user has enough CPU this 30fps file would play smoothly

 

Howard-Vigorita wrote on 9/22/2022, 3:13 PM

@todd-b You also need to look at quality when comparing Vegas to Resolve. I'm no Resolve expert but I could not find a data-element size setting in Resolve anything like Vegas' 8-bit integer and 32-bit float options... not sure it has one or what it is. I do know that the transcodes I tried with Resolve Studio using it's various codecs including Voukoder all come in significantly lower in quality than with Vegas.

todd-b wrote on 9/22/2022, 5:58 PM

I think the reason Resolve is so low in CPU is because it contains all frames and processing within the GPU Vram, which is very efficient but it means a lack of Vram is a very real problem, while Vegas , Premiere and most other NLE's don't do that, and the high bitrate of this file punishes CPU.

This is an NVENC encode in Premiere, doesn't list fps, but encode time 23.6 seconds. As strange as it sounds my hardware encode of a transcode is constrained by CPU. @Gid would likely get a faster hardware encode in Premiere due to having more CPU cores.

So actually for this file Vegas encodes faster (22s vs 23.6s) and uses less CPU doing it. A very interesting file giving unexpected results

EDIT: I only just noticed Premiere does not support GPU decoding for this file, while Vegas and Resolve does.

Howard-Vigorita wrote on 10/1/2022, 11:42 PM
I'm puzzling over how the legacy decoder with Mainconcept encoding is faster than the new decoder with Mainconcept and also faster than encoding with VCE or QSV. Why would that be?


@RogerS After update to Win11 22h2 and graphics driver updates from amd and intel, the MainConcept render and quality looks more sensible on the 11900k. I just re-ran everything and replaced the spreadsheet on google. Also dropped an Arc into my 9900k system and put in numbers for that. Looks to be a slight bit slower decoding than the uhd630 but qsv renders are somewhat higher in quality.