HEVC requires a lot of power to decode, so if you have a slower computer, you won't be able to do it without making a proxy file.

VEGAS 17 does support hardware decoding of HEVC files on GPUs that support it, so if you can give us your hardware specs, that will let us know whether or not your system will be able to decode HEVC smoothly or not. Also give us the project seThank you


Thank you for your answer fr0sty. Here you can see the hardware specs. of my computer. It`s a very expensive PC, just bought specially for video editing. The video card is Nvidia GeForce RTX 2080 Super.

 

That's a powerhouse system. You might want to give a little more info on the source and format of the hvec you're trying to work with. If it's a supported format, the problem is likely with the video drivers and/or the Vegas video config.

We need some other info about the way you work and the decoding option you use.
Which buildnumber of the program ?
Can you show a screenpicture of your project properties and the interface when using those hevc files?
And what is the specific driverversion for the Nvidia GPU and what is your setting at Options/Preferences/File I/O

We need some other info about the way you work and the decoding option you use.
Which buildnumber of the program ?
Can you show a screenpicture of your project properties and the interface when using those hevc files?
And what is the specific driverversion for the Nvidia GPU and what is your setting at Options/Preferences/File I/O

Hi!.
The answers of your questions are in the following attachements.

and:
[Display]
Operating System:    Windows 10 Pro, 64-bit
DirectX version:    12.0 
GPU processor:        GeForce RTX 2080 SUPER
Driver version:        446.14
Driver Type:        DCH
Direct3D API version:    12
Direct3D feature level:    12_1
CUDA Cores:        3072 
Core clock:        1815 MHz 
Memory data rate:    15.50 Gbps
Memory interface:    256-bit 
Memory bandwidth:    496.06 GB/s
Total available graphics memory:    40917 MB
Dedicated video memory:    8192 MB GDDR6
System video memory:    0 MB
Shared system memory:    32725 MB
Video BIOS version:    90.04.7A.80.69
IRQ:            Not used
Bus:            PCI Express x16 Gen3
Part Number:        G180 0042

That's a powerhouse system. You might want to give a little more info on the source and format of the hvec you're trying to work with. If it's a supported format, the problem is likely with the video drivers and/or the Vegas video config.

Here are more info about the file:
 

General
Format                      : MPEG-4
Format profile              : Base Media
Codec ID                    : isom (isom/iso2/mp41)
File size                   : 655 MiB
Duration                    : 55 s 22 ms
Overall bit rate            : 99.9 Mb/s
Encoded date                : UTC 2020-06-01 08:32:48
Tagged date                 : UTC 2020-06-01 08:32:48
Writing application         : Lavf56.15.102

Video
ID                          : 1
Format                      : HEVC
Format/Info                 : High Efficiency Video Coding
Format profile              : Main 10@L5@Main
Codec ID                    : hvc1
Codec ID/Info               : High Efficiency Video Coding
Duration                    : 55 s 22 ms
Bit rate                    : 99.9 Mb/s
Width                       : 3 840 pixels
Height                      : 2 160 pixels
Display aspect ratio        : 16:9
Frame rate mode             : Constant
Frame rate                  : 29.970 (30000/1001) FPS
Color space                 : YUV
Chroma subsampling          : 4:2:0
Bit depth                   : 10 bits
Bits/(Pixel*Frame)          : 0.402
Stream size                 : 655 MiB (100%)
Encoded date                : UTC 2020-06-01 08:32:48
Tagged date                 : UTC 2020-06-01 08:32:48
Color range                 : Limited
Color primaries             : BT.2020
Transfer characteristics    : HLG
Matrix coefficients         : BT.2020 non-constant
Codec configuration box     : hvcC
 

On my 9900K with VEGA 64 LQ I can have (4) tracks of 4K HEVC files, each with track motion resizing them to 1/4th of the screen, all playing at once and I get full FPS in both Preview & Best/Full.

CPU usage during 4 track playback is minimal, at around 12% whereas GPU usage is at 50%. Add crossfades to just one track & my GPU usage jumps to 95% and playback slows to a crawl..

Also, with (4) tracks of 4K, drive speed matters. If the source footage is on one of my (2) 2TB M.2 RAID0 drives, it only takes a fraction of a second for the preview to display FULL fps.... If the source footage is on a SATA drive, it can take more than a second to get full FPS...

This is my old tried & true method of choosing which camera I want to switch to when editing a multi-camera event..  I arm the audio to record my voice on a new track & set markers at each camera switch while calling out what camera I think is best.  Then, the 2nd time through I drag the chosen track to the top full-size track.  After that I might tweak the exact cut point but it saves me a ton of time & the reason I prefer Vegas vs. other NLEs... 

It's worth noting this is a 10 bit, Rec2020 hybrid-log-gamma (HLG) file, I'm not sure if hardware decoding support works for those files in VEGAS or not... care to chime in, team? If not, it's even harder to decode than a standard 8bit HEVC file if the load is being forced onto your CPU. You may have better luck using proxies for those files if they cannot be hardware decoded.

I do know the 10 bit H264 files from my Panasonic S1's can't be decoded on GPUs, because it is 4:2:2 and GPUs only support 4:2:0 chroma sub-sampling for hardware decode.

It's worth noting this is a 10 bit, Rec2020 hybrid-log-gamma (HLG) file, I'm not sure if hardware decoding support works for those files in VEGAS or not... care to chime in, team? If not, it's even harder to decode than a standard 8bit HEVC file if the load is being forced onto your CPU.

I notice something unusual with vp17. and this format of video. First up, plays fine with media players and davinci resolve. uses gpu decode on my Nvidia. but in VP17 there is no GPU decode, and oddly is GPU accelerated (no gpu decoded) on my intel processor which should not even be used by vp17. "enable legacy HEVC decoding via intel quicksync" is not turned on. GPU acceleration is turned on and set to my Nvidia card.

This seems to be a bug. with media player and Davinci Resolve I get little cpu activity and smooth playback, with vp17, very poor unusable playback and about 65% cpu. If you want to test on your vp17 this is the file. https://drive.google.com/file/d/0B58KOvm3krLlTGpzQ3pBQVlWcDQ/view

@Former user
I see nothing strange with that file loaded on VPro 17 b 452 on my laptop exept a very bad coloured picture. Look how the file plays at Preview Full and what the loads are

@Former user
I see nothing strange with that file loaded on VPro 17 b 452 on my laptop exept a very bad coloured picture. Look how the file plays at Preview Full and what the loads are

How do you get the same info about the project and the preview?

How do you get the same info about the project and the preview?

That will be done by your preview settings

@Paolo-Bruno afaik, your rog strikx motherboard has an Intel igpu onboard and your performance should benefit by using it for decoding. You might want to make sure you have the latest drivers for that igpu obtained from the asus support site for your motherboard (not from Intel). I find with my own asus motherboard that I get the best overall Vegas performance using the Intel igpu for decoding and even better performance if I uncheck the Intel legacy option on the File I/O screen. That frees up my video board for everything else.

@Howard-Vigorita
I don't see you have also the GeForce RTX 2080 SUPER with the right drivers that @Paolo-Bruno has.
How do you know that your Intel igpu performs better?
Is there some statement from the developpers I did not see?

@Former user
I see nothing strange with that file loaded on VPro 17 b 452 on my laptop exept a very bad coloured picture. Look how the file plays at Preview Full and what the loads are

Your decode is working just fine. I don't have decode. I put the settings at the end of video

@j-v Can you see if you can make vp17 use your Nvidia gpu video decoder for that file?

@Howard-Vigorita
I don't see you have also the GeForce RTX 2080 SUPER with the right drivers that @Paolo-Bruno has.
How do you know that your Intel igpu performs better?
Is there some statement from the developpers I did not see?

@j-v I have a different brand gpu but almost the same motherboard and cpu. And have benchmarked it every which way in this thread... complete with video capture of me doing it. In all the testing I've done on various gpus and systems, dividing the load always seems to improve performance. Indeed, as soon as Intel releases its rumored Xe pcie board, I'm gonna grab a couple for my systems that do not have an onboard igpu. And naturally, report the results here.

@j-v Can you see if you can make vp17 use your Nvidia gpu video decoder for that file?

No, these are my settings you showed.

But also if all options are unchequed in File/I/O, it makes for that file no difference.
It does when I use my GOPro 4K HEVC files.

using your settings I can't replicate video decode on intel gpu, which would be good enough. Well i'm out of ideas, maybe a nice computer restart will help

And maybe using the right GPU drivers for that task.
But nowhere I see you mentioned the type of Nvidia and Intel GPU so I cannot give you advice for suitable drivers.

Here's a little tidbit I noticed in the latest Intel driver release... no indication of if or when an Xe pcie board might happen but look at that decoder list! May or may not be what gamers are hoping for but it'll change everything for video editing.

says 12 bit but no mention on 10bit 4:2:2.. that's the current issue as I see it (awaiting my A7Siii arrival..); like current situation whereas HW support for 4:4:4 and 4:2:0 is there but not for 4:2:2.. the devil could well be in the detail..