@Former user what is your current intel driver version? I can see in your signature your driver version for your PC and laptop, but it may be different now after your update.
my driver version for the 630 is 25.20.100.6444, I am on windows 10 version 1809.
@bitman I’ll be able to check in about an hour, but it doesn’t change usualy, very likely still as in profile. Win 10 1809 both, latest updates. Just checked, as signature, no change.
I redid using oldsmokes test clips. By changing the Project frame rate to 25 from 29.97, all playback was slower, which is what I wanted. Proxies not used. Three pieces used with an overlap croosfade.
I observed the peak values as it played in a loop and also did a screen grab for each of 3 different HW Acc. settings … None, Intel and Nvidia.
HW Acc.
None .. Max playback fps .. 17 Cpu max 100% 630 Max 55% Nvidia Max 21%
Intel .. Max playback fps .. 13 Cpu max 100% 630 Max 52% Nvidia Max 21%
Nvidia .. Max playback fps .. 14 Cpu max 100% 630 Max 41% Nvidia Max 13%
None
Intel
Nvidia
Since there are no VFX added it may be of limited use.
I would rather think that the peaks you are seeing is GPU load from using OpenCL/GL since you changed frame rate and made an overlap. It doesn’t mean that NVDEC was used.
@bitman Just checked, as signature, no change.
mmm, I finally got some Vegas timeline decoding % using the intel (in task manager for video decoding, mind you, only for 4k, and not for Hvec). I however had to disable my nvidea, connect HDMI to intel (and deselect display port connected to nvidea).
Not sure I want to go further with this, as there is also some discussion on the new intel DCH Drivers breaking QSV if the application (= Vegas) is not recompiled to match the new "intel speech". Checkout other posts on this on the net or here.
Other NLE (Resolve to mention one) is using NVDEC to decode AVC and HEVC files. It works beautifully. So Vegas team should be able to implement it...
^This correlates with my findings. +1. Timeline playback in VP is choppy and not very well using available hardware.
@AVsupport no crashes so far, but if it crashes in games or any other application including Vegas, first thing I will do is disable the iGPU as I do not see any use for it except maybe as a backup for video output if my videocard would be broken. Quality wise rendering via NVENC is supposed to be better as QSV anyway especially so on an RTX (if you believe the promo talk). Maybe another reason to disable iGPU (apart of avoiding conflicts with your main card) is heat. Disabling all not used silicon helps with "saving the planet" by reducing power consumption and thereby heat, which in case of the iGPU is helpful as the CPU will run cooler with all benefits associated with having a cooler CPU (= frequency will throttle down less, fan will make less noise).
Just checked latest DaVinvi Resolve 16, and whilst 1080 timeline playback of 4K XAVCS clips is fast, I cannot see Nvidia Decode activity in Taskmanager, only 3D, ~12%. That said, I believe Resolve utilizes CUDA as part of their HW acceleration...
Just checked latest DaVinvi Resolve 16, and whilst 1080 timeline playback of 4K XAVCS clips is fast, I cannot see Nvidia Decode activity in Taskmanager, only 3D, ~12%. That said, I believe Resolve utilizes CUDA as part of their HW acceleration...
In DR16, with a UHD timeline and UHD DnXHD 29.97, I get full speed playback, CPU runs about 42% and GPU about 5%, AMD R9 390 (OpenCL).
Just checked latest DaVinvi Resolve 16, and whilst 1080 timeline playback of 4K XAVCS clips is fast, I cannot see Nvidia Decode activity in Taskmanager, only 3D, ~12%. That said, I believe Resolve utilizes CUDA as part of their HW acceleration...
Resolve16 is public beta, prob bugs or currently incompatible. With 15 I get 18-20% 'video decode' on timeline playback of 4k30p files
Just checked latest DaVinvi Resolve 16, and whilst 1080 timeline playback of 4K XAVCS clips is fast, I cannot see Nvidia Decode activity in Taskmanager, only 3D, ~12%. That said, I believe Resolve utilizes CUDA as part of their HW acceleration...
Resolve16 is public beta, prob bugs or currently incompatible. With 15 I get 18-20% 'video decode' on timeline playback of 4k30p files
Yes @Former user I thought there was! (You're using XAVC-S as well?) Hence I was so surprised not seeing this after I downloaded..! Interesting..
I just tested with 4K50P XAVC-S and you are right, there is no hardware decode. CPU 82% just for playback. Media Player Classic is able to use hardware decode - 34% 'video decode'. Although a lot of cpu, playback is perfectly smooth, compare to Vegas15 where I get 1fps, and it's not usable.
Converted to HEVC & CPU reduces to 32% due to HW decode on timeline (resolve)