Vegas 15 GPU Acceleration Testing - Page 1
Forum section: electronics / general

author: EEVblog
author_rank: Unknown
timestamp: November 21, 2017, 03:11:46 am
content: Tests for quality differences:Using the NVENC engine and nothttps://en.wikipedia.org/wiki/Nvidia_NVENCAll in 1080p50 12Mbit/28MbitResults:NVencoder HQ : 1min 47sec 179MBNVencoder LQ Default : 1min 43sec 180MBMainConcept : 2min 41sec 192MB

author: cdev
author_rank: Super Contributor
timestamp: November 21, 2017, 03:27:59 am
content: On the GPU acceleration video, the audio sounds horrible through my Sony MDR-v6 headphones.

author: EEVblog
author_rank: Unknown
timestamp: November 21, 2017, 10:13:49 pm
content: Quote from: cdev on November 21, 2017, 03:27:59 amI can't hear any difference on my reference monitors or headphones.

author: cdev
author_rank: Super Contributor
timestamp: November 21, 2017, 10:37:29 pm
content: It seems to me as if its just the beginning part of first video "Vegas 15 GPU Acceleration Testing" that has a kind of raspiness in my headphones. The later part sounds okay, not raspy but it does sound as if you equalized it using a U shaped curve - it sounds "thin" in the middle, it maybe needs a bit more "presence" it might sound better with more of the middle frequencies, the ear is the most sensitive to sounds around 1 khz?The others sound okay.If you had a particular audio clip that you could use for testing at a set level, then you could analyze its spectral content to see if its spectral content looks out of the ordinary in any way.It may well just be me.These programs are all really cool in their own ways, and have the capability to analyze the spectral content of audio..http://www.sonicvisualiser.org/which is extremely sophisticated and has all sorts of plugins available for itBaudline.http://www.baudline.com/index.htmland Speclabhttp://www.qsl.net/dl4yhfwhich you can also use as a VLF receiver.

author: EEVblog
author_rank: Unknown
timestamp: November 30, 2017, 06:33:36 am
content: So I installed a GTX-1050 card with the latest NVIDIA chipset and NVENC encoder and I gotzero differencein the render time compared to the GTX750Ti using Vegas 5 that supports the NVENC encoder.Very surprising!

author: cdev
author_rank: Super Contributor
timestamp: November 30, 2017, 03:00:05 pm
content: Strange. Is there any chance that its not using either GPU at all!???

author: dr.diesel
author_rank: Super Contributor
timestamp: November 30, 2017, 03:12:01 pm
content: I suspect it's not utilizing the GPU at all. I don't know how to do it on Windows, but I'm sure there is a utility to view GPU processes/usage in real time, and an idle GPU card here would explain it.

author: thm_w
author_rank: Super Contributor
timestamp: November 30, 2017, 10:42:22 pm
content: Thats quite surprising, 1050 Ti peak power consumption might be a few watts lower than 750Ti but its not much.Although, you can use the 1050 Ti to mine ethereum at ~13MH/s, 750 is less than half of that.Quote from: dr.diesel on November 30, 2017, 03:12:01 pmWatch the previous video at the top of this thread, he monitored GPU usage and it was at 100%. When using cpu it was below 20%. So I'd be very surprised if he put in a new card and it was any different.edit: didn't realize its a 1050 not a 1050 Ti, which is a terrible card (you could see the passmark was almost the same as 750ti). Although not sure if it matters for GPU rendering.

author: SparkyFX
author_rank: Frequent Contributor
timestamp: December 01, 2017, 01:44:47 pm
content: GPU accelerated video rendering is a hot mess since years. As far as i understood it NVEnc is a nVidia only thing will only utilize GPU, but not the CPU. Handbrake H.264, FFmpeg, and according toWikipediaallegedly MAGIX Vegas too, support OpenCL and could theoretically utilize CPU and GPU (even onnVidia GPUs with latest drivers), but no idea if the encoder can or does select that.The thing is, the libx264 (used in handbrake and ffmpeg,...) doessome lookaheadsvia OpenCL, but not the main encoding cause they did not want to rewrite the whole code. So it won´t drastically benefit from it. Handbrake can move scaling to OpenCL, ffmpeg can filter with it, but itself can not beat libx264 to fully use OpenCL. So "support for OpenCL" is to be taken with caution, although thelist of encoders with OpenCL support is long.Handbrake andffmpeghowever also support NVEnc. Why mention ffmpeg? Because it always represents a good state of open source support for these things and is actively developed.AMD allegedly worked on a fork/version of h.264 that uses OpenCL, but nothing is to be found except some interviews and an old anandtech article.