Comments

fr0sty wrote on 5/5/2018, 4:38 AM

Are you using QSV on the 15 version, GPU, or CPU only?

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Vliegvisser wrote on 5/5/2018, 5:12 AM

How and where can I see and use all those settings ?

Vliegvisser wrote on 5/5/2018, 12:05 PM

Here is the solution of the riddle.
My comparison was a kind of a joke, because I can do the same in VPro 15 without any change in settings of that program, so it must be a bug or something that Magix should warn for before to use that option.
Maybe the developpers can build this option into that Intell HEVC codec.

The only thing I have to change is the setting for my videocard in Windows Device Management to disable my Nvidia videocard.

This video also shows my laptop which has more possibilities for making this very fast rendering possible in the option which GPU has to be choosed for starting a program.

See this video for the two different renders with the same codec without making in the program any change.

fr0sty wrote on 5/5/2018, 10:17 PM

Be sure you click that "customize template" button and make sure that the settings inside the preset are all the same... That is where you choose if you are using your GPU, intel quicksync, or CPU only. Quicksync runs off the CPU (built in GPU to some Intel CPUs, more accurately), which is why I was asking if somehow that may have been enabled in Vegas 15, as that was a feature they added to version 15 that was supposed to speed up encoding of HEVC and H264 files. That said, I wouldn't put it past it just being a bug. If so, good catch.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

NickHope wrote on 5/6/2018, 4:20 AM

@fr0sty I don't believe you have any such "Encode mode" choices in the "Custom Settings - Intel HEVC" dialog (unlike in the various AVC dialogs). Vegas should just use QSV if it's available. See this comment from a Vegas developer.

There are some weird and complex things going on in recent VP15 builds with regard to QSV and NVENC. Hopefully they will be resolved in the next update.

Vliegvisser wrote on 5/6/2018, 5:08 AM

See this comment from a Vegas developer.

In the following comments that developper asked about 10 bits HEVC rendering.
With me, both graphics allowed and very slow rendering it is no problem to render 10 bits Intel HEVC.
But with only the Intel GPU allowed I get an error trying to render to 10 bits.

Therefore I think the difference in this topic is caused by my impression that in my normal situation ( both GPU's available) the Intel GPU not is being used, but the rendering to Intel HEVC is all by the Intell CPU and in that case Vegas don't uses QSV.

 

bitman wrote on 5/6/2018, 6:10 AM

@Vliegvisser This is all meaningless if you do not have a monitor connected to your motherboards' interface (to be able to use INTEL QSV for HVEC, and obviously have it enabled in BIOS, and have an INTEL processor with GPU inside not all INTEL CPU's have this).

If you use a laptop chances are big you can use it for obvious reasons (a screen is usually build in 😀). If you are on a desktop with a very big ultra wide screen, I have no space on my desk left for a second screen. I am not going to castrate my video computing power from my nvidea 1080 ti to the INTEL GPU just for encoding. Connecting my screen to the intel just for encoding is in my particular case also a practical nightmare as the peculiar way I have build my own PC for the airflow and the way it barely fits in my desk's wood cabinet.

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

Vliegvisser wrote on 5/6/2018, 7:19 AM

@ bitman
Both no problem for me on laptop where I showed it from as on my desktop where I have also more possibilities.
There normally my second monitor is connected by HDMI to the motherboard and after disabled the Nvidia my first monitor (HDMI connected with Nvidia Graphic card)goes black and I proceed the rendering on the second monitor where there is now my desktop with Vegas activated. Very fast rendering now with the Intel GPU.
I' m also able to connect both to my first monitor on HDMI 1 and 2 and do I have to switch my (first and only) screen to HDMI 2.

Another question may be if I normally want to use this codec.
My answer is sometimes, mostly I use Vegas2Handbrake to let render by Handbrake to HEVC. My reason for that is far beyond this topic.