VP17 HEVC decoding - read this!

bitman wrote on 8/7/2019, 1:32 AM

I was first excited to see quite a few of the new features on Vegas 17 matching my whish list, like improved color correction and nested timelines, and above all added HW decoding. Then I got very disappointed as it did not seem to work with NVDEC - so it seemed at first - I set the preference to NVIDEA as usual (why QSV was default it is beyond me). Playing a UHD 50p HVEC clip from my Gopro 6 on the time line did not show on windows resource monitor:

Playing the same clip on Magix Video Pro X did show decode (notice also the large memory usage!)

Fortunatly I noticed a magix comment on another issue about enabling the NVIDEA HW decode in the preference under IO-file, a setting which I was not expecting I had to enable this explicitly for this new VP17 feature, (if I recall this was set to QSV by default, so why again set to the lesser capability by default?). Personally I think many people will be missing out to have this default set to QSV if their system has a really good video card (like my RTX 2080ti) present. Although having the flexibility to separate decode enable from general video hw acceleration enable seperatly is a good thing, but having HW acceleration settings spread around tabs is not user friendly and I guarantee it will generate much frustration and many forum post in the future. For future releases: please group all HW acceleration enable/disable GUI settings in one place...

Here is the same clip with VPX17 and NVDEC enabled, and now it shows decode...

Comments

Peter_P wrote on 8/7/2019, 1:37 AM

Personnaly I think many people will be missing out to have this default set to QSV if their system has a really good video card (like my RTX 2080ti) present.

I assume you main monitor is connected to the Intel port and this is used for the default.

bitman wrote on 8/7/2019, 1:44 AM

@Peter_P

No, my monitor (I have only one) is connected to the videocard via the display port. I do have the same monitor physically also connected via HDMI on the Intel (but the HDMI is not selected in the monitor menu itself).

Peter_P wrote on 8/7/2019, 2:21 AM

And which one is quoted 'Optimal -' ?

On my i7-8700k with AMD RX570 I could change the default ('Optimal -') setting form Intel to AMD by just having the only monitor connected to the AMD card. QSV was still available for Vp17.

j-v wrote on 8/7/2019, 3:01 AM

@bitman

(if I recall this was set to QSV by default, so why again set to the lesser capability by default?).

I saw exactly the same and after I changed it in that Preference setting I ask myself also why the weaker option automatic becomes choosen by the program.

bitman wrote on 8/7/2019, 3:14 AM

@Peter_P the nvidea card was quoted "optimal", and still QSV was default selected.

pierre-k wrote on 8/7/2019, 3:39 AM

GPU preferences are very confusing. There's something in General. Something in Video and now in I / O. It is completely confusing for a new user.

Here is a suggestion in the next update.

Thanks to Magix Team.

Peter_P wrote on 8/7/2019, 4:10 AM

@Peter_P the nvidea card was quoted "optimal", and still QSV was default selected.

So this is the same as on mine. And in the 'File-I/O' : 'Enabe Hardware Decoding ... ' AMD is not listed but the QSV and NVDEC, the later is not available on my system. However I can play UHDp30 HEVC (Vp17 AMD QSV rendered) in 1920x1080 internal preview with Best(Full) with full framerate 29.97fps (Loads : CPU 14%, Intel UHD 630 54%, AMD RX570 23%).