New findings, Using intel graphics.

Josh_Grid21 wrote on 3/7/2016, 2:45 AM
Hello, I recently have been trying out Intel Quick Sync for Open Broadcaster Software. But in the process I found that Vegas Pro 13 also supports quick sync, and while at the moment I can't get the setting in my render settings for AVC/MVC .MP4 to work. I did play with GPU acceleration on Preview.

Here are my findings.
GPU acceration preview with GTX 960 enabled, 44 minutes, 25% load. 1080p. Render setting: Render using GPU if able

GPU acceration preview with Intel 4600 enabled, 43 minutes, 25% load. 1080p. Render setting: Render using GPU if able

GPU acceration preview with Intel 4600 enabled, 38 minutes, 26% load. 1080p. Render setting: automatic.

I get the idea of how you can use your GPU for preview, but the render part is where it still stumps me. If GPU acceleration is on in Preview, does that help the rendering process? my iGPU is enabled, but after following this video here. I am still unable to allow the computer to use iGPU aka Quick Sync to work, yet OBS is able to use it no problem.

Can someone please kindle explain the science of this concept I am trying to understand.

Please and thank you.
Josh.

Comments

musicvid10 wrote on 3/7/2016, 6:45 AM
GPU acceleration and Intel QSV are not the same thing.

QSV rendering is not yet available in Vegas AFAIK.
john_dennis wrote on 3/7/2016, 10:24 AM
There is a good 20,000 foot overview of quick sync here. I have enabled Quick Sync when recording in OBS and encoding in Handbrake, but, so far, I use CPU only when encoding in Vegas Pro.
wwaag wrote on 3/7/2016, 10:36 AM
Quick sync in Vegas does work, but only for Sony AVC 720 60P renders. Sony AVC 1080 60P renders do not work for whatever reason. To use QS in Vegas, you must have it drive at least one of your displays.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

NormanPCN wrote on 3/7/2016, 2:00 PM
Here is a link that documents how to enable the Intel graphics subsystem without having it connected to a display, The reason for that is if you have an AMD/Nvidia GPU but would like to be able to use Quicksync. In Vegas that would be via Sony AVC.

https://mirillis.com/en/products/tutorials/action-tutorial-intel-quick-sync-setup_for_desktops.html

"If GPU acceleration is on in Preview, does that help the rendering process?"

GPU accel in Video prefs controls GPU use for the video engine in Vegas. The video engine is ALWAYS used. Preview and encoding a file. Additionally a file encoder ("render as") might have GPU support and if they do they have their own options to control that. This option is for encoding the file and is independent of generating(rendering) the video stream.
john_dennis wrote on 3/7/2016, 6:08 PM
I revisited Quick Sync on the HD 4000 in my i7-3770(k) and came to the same conclusion that I reached some years ago. If you can frameserve from Vegas Pro and encode in Handbrake, the result and the speed will be better than using Quick Sync and the Sony AVC/MVC encoder.

Source: 1280x720-59.94p video 04:52.35 long.

Render in Vegas Pro 13 using QSV (Quality) with the Sony AVC/MVC Internet encoder
CPU = 36%, GPU=17%, elapsed time=04:14

Frameserve from Vegas Pro 13 to Handbrake 1280x720-59.94p Quality - 20
CPU = 80%, GPU = 26%, elapsed time = 03:35
NormanPCN wrote on 3/7/2016, 7:30 PM
That is why I bailed on using Quicksync via Sony AVC in Vegas when I set it up long ago. Frameserving to x264 was a better solution. In my case I frameserved directly to ffmpeg.
musicvid10 wrote on 3/29/2016, 9:18 AM
I've been reading some after John Stebbins' comments, and it seems Vegas' utilization of QSV would be independent of Sony AVC or other software encoders. IOW is it not a dedicated hardware solution?

What are the settings in Pro 13 to enable QSV?
What does MediaInfo say about the output encoder?
[large]"[large]

NormanPCN wrote on 3/29/2016, 11:07 AM
What are the settings in Pro 13 to enable QSV?



Sony AVC is not necessarily a software encoder only. It is whatever Sony wants it to be. It is just a selection in the render as dialog. They could have created a separate "quicksync" render as template but they just chose to put their Quicksync AVC support into their own AVC encoder.

The Render As Sony AVC has multiple code paths from what I can see.
Pure CPU.
CPU encode with IMO motion estimation done via OpenCL GPU
CPU encode with IMO motion estimation done via CUDA GPU
Intel Quicksync

Quicksync is its own self contained encoder for the AVC stream. Just like x264 does not do audio or any muxing. Vegas will do the audio and muxing of the two data streams.

It has been years since I had Quicksync installed (aka Intel video drivers). I don't have any files lying around that were encoded with it but as I remember they were just normal MP4 AVC files. As for metadata, since Vegas is doing the muxing they can put whatever they want in there.
john_dennis wrote on 3/29/2016, 3:25 PM
"[I]What does MediaInfo say about the output encoder?[/I]"

Here is a project that I ran on the i7 3770(k). The project, source file, rendered output for CPU Only, QSV Quality and QSV Speed are in the folders.

Quality isn't.