No render template in Vegas Pro 18 MAGIX AVC/AAC MP4 with Intel QSV

GerY wrote on 10/2/2020, 12:36 AM

Hi I did not see any render templates with Intel QSV in the templates of MAGIX AVC / AAC MP4. I do see them in Magix HEVC / AAC MP4. I have already done a reset but this had no result. The PC also has VP17 and I see that they are there. I am using the same settings as in VP17. See the attachment. I am using the latest GPU and CPU drivers.

Comments

wiel-gulpen wrote on 10/2/2020, 1:04 AM

The same here.

I have not acces to the render templaten with QSV in the templates of Magix AVC/AAC MP4.

In Vegas Pro 16 I have!

Greetings,

Wiel

Camera: Panasonic GH7, Gopro Hero 10, Zoom H2n, software Vegas Pro 16, 18 en 22 Suite, several Boris FX Continuum units 2020.5, Mercalli 6, Pinnacle Studio 22 Ult, IMGBurn, VdG 12, Blufftitler 17, Paintshop Pro 2018, Aquasoft Videovision 13. PC: Asus ROG Strix 390-E mobo, 9900K, 32Gb.intern, Asus Strix 2060S graphics, 2 M2 SSD,1 SATA SSD en 2 SATA HD.

j-v wrote on 10/2/2020, 3:50 AM

I am seeing the same in VPro 18 as you see for both when I switch off my Intel CPU in the taskmanager,

but do not see what you see in VPro 17.
With me also in 17 no QSV templates with that Intel CPU switched off.
Looks to me something is blocking the right working of the Intel CPU In your VPro 18 installation. No idea what it could be.😏
 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

j-v wrote on 10/2/2020, 6:20 AM

@GerY & @wiel-gulpen
Are you both able to show here a screenshot of your Help/Check for Driver Updates...?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

GerY wrote on 10/2/2020, 7:14 AM

@GerY & @wiel-gulpen
Are you both able to show here a screenshot of your Help/Check for Driver Updates...?


j-v wrote on 10/2/2020, 7:58 AM

Exactly the same as mine

Very strange what happens to you both.
Hopefully someone else or a developmentmember can jump in...

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Musicvid wrote on 10/2/2020, 1:02 PM

I see your point; however, it's a pig in a poke.

Once you use an encoder that exposes the limited h.264 QSV controls (Voukoder), and the ungodly file sizes needed to come anywhere near to software x264 quality (2x?). you will surely ask yourself, "Why?"

It's simply unusable. And that's a really good reason for a software developer to leave them out.

john_dennis wrote on 10/2/2020, 1:58 PM

@GerY

Do you have a monitor attached to the intel adapter?

It could be worse. You could have QSV offered on a system that doesn't have the hardware at all.

https://www.vegascreativesoftware.info/us/forum/qsv-on-an-i7-6850--119174/

wwaag wrote on 10/2/2020, 2:58 PM

No problem here with use of QuickSync render templates. Intel i7-8750K.

 

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.

wiel-gulpen wrote on 10/2/2020, 3:27 PM

Hi there,

My AVC-settings on the screenshots with brand new Vegas Pro 18. No standard settings changed.

 

Greetings,

 

Wiel

Last changed by wiel-gulpen on 10/2/2020, 3:28 PM, changed a total of 1 times.

Camera: Panasonic GH7, Gopro Hero 10, Zoom H2n, software Vegas Pro 16, 18 en 22 Suite, several Boris FX Continuum units 2020.5, Mercalli 6, Pinnacle Studio 22 Ult, IMGBurn, VdG 12, Blufftitler 17, Paintshop Pro 2018, Aquasoft Videovision 13. PC: Asus ROG Strix 390-E mobo, 9900K, 32Gb.intern, Asus Strix 2060S graphics, 2 M2 SSD,1 SATA SSD en 2 SATA HD.

wiel-gulpen wrote on 10/2/2020, 3:31 PM

My Magix HEVC templates (with QSV-option!

Camera: Panasonic GH7, Gopro Hero 10, Zoom H2n, software Vegas Pro 16, 18 en 22 Suite, several Boris FX Continuum units 2020.5, Mercalli 6, Pinnacle Studio 22 Ult, IMGBurn, VdG 12, Blufftitler 17, Paintshop Pro 2018, Aquasoft Videovision 13. PC: Asus ROG Strix 390-E mobo, 9900K, 32Gb.intern, Asus Strix 2060S graphics, 2 M2 SSD,1 SATA SSD en 2 SATA HD.

wiel-gulpen wrote on 10/2/2020, 3:40 PM

Before installing in Vegas Pro 16 (!) the QSV-templates in Magix AVC templates were there.

Also yesterday when I read this post and checking Vegas Pro 16 after installing Vegas Pro 18.

To find a solution I set and unset 'AVC Legacy decoding'.

Then I updated the Intel Graphics 630 driver to 27.20.100.8783 from 27.20.100.7990. See other screenshot.

After unsetting (see i/o file above), the AVC QSV templates are also not avaiable in Vegas Pro 16 anymore.

Also I see that the preview on my second monitor (HDMI from Nvidia 2060S card) is less smooth then yesterday!

Then I did a full reset (CTRL+SHIFT+ icon Vegas Pro 18) of Vegas Pro 18 and after restart it was as smooth as yesterday.

Very strange behaviour.

 

Greetings,

Wiel

(My main monitor is 4K connected to Intel GPU 630 mainboard mini-DP, my preview monitor is 2K.connected to 2060S graphics - HDMI )

Last changed by wiel-gulpen on 10/3/2020, 3:24 PM, changed a total of 7 times.

Camera: Panasonic GH7, Gopro Hero 10, Zoom H2n, software Vegas Pro 16, 18 en 22 Suite, several Boris FX Continuum units 2020.5, Mercalli 6, Pinnacle Studio 22 Ult, IMGBurn, VdG 12, Blufftitler 17, Paintshop Pro 2018, Aquasoft Videovision 13. PC: Asus ROG Strix 390-E mobo, 9900K, 32Gb.intern, Asus Strix 2060S graphics, 2 M2 SSD,1 SATA SSD en 2 SATA HD.

Robert Johnston wrote on 10/2/2020, 5:01 PM

I have the QSV templates for Magix AVC in Vegas Pro 18, but there's a problem with the rendered results - lots of artifacts. Now I just use the Sony AVC templates with QSV that I created in Sony Vegas Pro 12 for video 1920x1080 or less. And I don't have a separate GPU card, just integrated Intel HD 2500.

Intel Core i7 10700K CPU @ 3.80GHz (to 4.65GHz), NVIDIA GeForce RTX 2060 SUPER 8GBytes. Memory 32 GBytes DDR4. Also Intel UHD Graphics 630. Mainboard: Dell Inc. PCI-Express 3.0 (8.0 GT/s) Comet Lake. Bench CPU Multi Thread: 5500.5 per CPU-Z.

Vegas Pro 21.0 (Build 108) with Mocha Vegas

Windows 11 not pro

wiel-gulpen wrote on 10/3/2020, 3:22 PM

How can I reach the Vegas development team to pay attention to this lack of templates?

Wiel

Camera: Panasonic GH7, Gopro Hero 10, Zoom H2n, software Vegas Pro 16, 18 en 22 Suite, several Boris FX Continuum units 2020.5, Mercalli 6, Pinnacle Studio 22 Ult, IMGBurn, VdG 12, Blufftitler 17, Paintshop Pro 2018, Aquasoft Videovision 13. PC: Asus ROG Strix 390-E mobo, 9900K, 32Gb.intern, Asus Strix 2060S graphics, 2 M2 SSD,1 SATA SSD en 2 SATA HD.

Musicvid wrote on 10/3/2020, 9:45 PM

there's a problem with the rendered results - lots of artifacts.

Yup. "Unusable" is the term I used above.

Howard-Vigorita wrote on 10/4/2020, 12:17 AM

I've had problems with Intel drivers of the years, depending on where they originated. Intel has been in the habit of not including the opencl api except for vendor/clients that request it. I found that for instance, Intel drivers obtained from Asus whose motherboards I use come with the opencl api but in the past I've experienced getting a driver update via Windows that blasted it. You can check using the gpu-z utility from TechPowerUp. Make sure there's a checkmark in the opencl box.

Fwiw, that Intel driver version came via Vegas 18 driver update. But I got the previous driver from the Asus support page for my motherboard which originally installed the opencl api and the update via Vegas did not overwrite it. I'm not sure v18 still depends on the Intel opencl api but I know that older versions of Vegas do.

GerY wrote on 10/4/2020, 2:27 AM

So reading that I miss nothing with that QSV encoder. Still it remains strange, but I can miss him. Thank you for your support

turboBB73 wrote on 10/31/2020, 11:00 PM

Copying below the last reply from this thread related to this problem. I noticed that I lost the ability to render in QSV since I updated to the DCH drivers... Hopefully Magix will update VP18 or future version to utilize it again since QSV is still great on laptops that support it for quick edits not requiring high quality.

=======

Intel has verified the problem with the following response. Intel either needs to be pressured by larger companies or Magix needs to offer an update for Vegas Pro 15 to get quicksync functionality working again! FYI: I did let Intel know this is an unacceptable position!

Ronald_Intel (Intel)

Hello everyone,

Thank you for your patience on this one. After checking in with our devs it was determined that the affected applications need to be rebuild using an updated Intel® Media SDK. I know this is not the easiest approach but with the massive shift to DCH some portions of the driver code cannot work the same anymore. We won't be making DCH drivers backwards compatible so our recommendation is to wait for the affected applications to get updated (per example just like Handbrake 1.2.2 did).

Best Regards,
Ronald M.