Try updating your QSV drivers.

Help->Check for driver updates.

Na, everything is freshly updated on Windows 11. I wish it were as simple as a non updated driver.

Unless testing on a system with a 11th generation+ Intel CPU with Intel GPU, you aren't testing the QSV hardware decoder with HEVC 10-bit 4:2:2.

Handy chart that refers to Premiere but should be the same for Vegas:
https://www.pugetsystems.com/labs/articles/What-H-264-and-H-265-Hardware-Decoding-is-Supported-in-Premiere-Pro-2120/

Mark, I wouldn't waste more time trying to figure it out- pretty clearly a decoding issue from the type of error seen with QSV. Either file a support request of wait to see if Vegas staff replies to this thread. Not many users are using Vegas with these most recent CPUs with such files or we'd see more complaints. Though if any are reading this far it would be good to get them to validate it fails on their 11th or 12th generation Intel CPUs, too.

One other idea for a workaround is choosing a 10-bit AVC format in camera for now, assuming your camera has one with the other settings (resolution, framerate, etc.) you need. Vegas has supported those for longer and I remember trying a few out when the R5 and R6 came out.

One other idea for a workaround is choosing a 10-bit AVC format in camera for now, assuming your camera has one with the other settings (resolution, framerate, etc.) you need. Vegas has supported those for longer and I remember trying a few out when the R5 and R6 came out.

Yes good point

One other idea for a workaround is choosing a 10-bit AVC format in camera for now, assuming your camera has one with the other settings (resolution, framerate, etc.) you need. Vegas has supported those for longer and I remember trying a few out when the R5 and R6 came out.

Yes good point

I dont' think your camera does AVC 10 bit, that's why it was so controversial on release. Nothing could edit it.

It looks like you're using HEVC IPB Full Format, 4K HQ, you could try the ALL I version which will playback easier without using GPU decoder and so avoid the decoding bug. The bitrates are much higher, 470MB/s for HQ, 350MB/s for standard quality

T'was a good idea but ALL I barely makes a difference. I only create wedding films. I suppose for the time being I can just work with the CLOG3 in an 8bit project despite not maximizing its potential. I don't do any ultra high end work

Confirmed, The ALL-I format actually uses more CPU, and is less playable than IPB. It seems to be a completely pointless codec, compared to ALL-I 422 AVC as created by other cameras which is much easier to edit and shuttle through

I didn't use Vegas for the comparison as it would be pointless, Both clips use a tiny amount of CPU, and behave like slideshows

@MarkAnthony121Been shooting clog3 a bit myself lately but not 4:2:2 as the performance is lower in Vegas than 4:2:0. But I didn't get messed up green tint when I tried it on an 11900k which decoded it OK. Just not as smoothly as you describe with your 11200k. I'd suggest going with the latest Intel graphics drivers using the Intel Driver & Support Assistant being that your igpu is fairly new. This seems to be the latest as of this minute: 30.0.101.1340.

Btw, I've been working with my clog3 footage by setting Vegas to 8-bit limited during edit with legacy hevc un-checked but switching to 32-bit limited with legacy hevc enabled for final render. And for some reason I've been getting nicer range distribution putting the LUT into the Look-side on the far right of the Color Grading Panel rather than the Camera-side on the far left... the upper end on the distribution looks less crushed to me in the scopes that way.

Thanks I'll try that method!

@MarkAnthony121Been shooting clog3 a bit myself lately but not 4:2:2 as the performance is lower in Vegas than 4:2:0. But I didn't get messed up green tint when I tried it on an 11900k which decoded it OK. Just not as smoothly as you describe with your 11200k.

@Howard-Vigorita could you try this file 422 1080P60, Interested if you can play at 60fps in BEST/FULL with your Intel decoder, and report cpu use?

https://www.dropbox.com/s/jrif74cmeqpla3f/R5T_9417_Video_Cut.MP4?dl=0

@MarkAnthony121Been shooting clog3 a bit myself lately but not 4:2:2 as the performance is lower in Vegas than 4:2:0. But I didn't get messed up green tint when I tried it on an 11900k which decoded it OK. Just not as smoothly as you describe with your 11200k.

@Howard-Vigorita could you try this file 422 1080P60, Interested if you can play at 60fps in BEST/FULL with your Intel decoder?

https://www.dropbox.com/s/jrif74cmeqpla3f/R5T_9417_Video_Cut.MP4?dl=0

 

Same exact situation as with my footage. Buttery smooth, imports correctly. Once I change project to 32bit the clip displays distorted. Then when I turn off QSV the clip displays correctly but is choppy

I'm trying to work out if the new Intel IGPU's some how fix the HEVC problem where Vegas is limited to only using a small amount of CPU , around 20% on my CPU, then dumps frames because it gets overloaded. That video plays terribly on my computer but I don't have the GPU decoding that you guys have which potentially reduces the cpu use for decoding below the point it overloads... but maybe it is able to use more cpu and 12th gen CPU's are the answer to this problem, almost , just the 32bit bug

@MarkAnthony121 One last question, can you playback 60fps 4K 422 IPB at 60fps in 8bit project?

If it's slide showing do the play/pause/play thing at the beginning to see if that helps

If you haven't tried this is a sample https://www.dropbox.com/s/p3ru2ko05u0bvei/R6_T3402_Cut.MP4?dl=0

@MarkAnthony121 One last question, can you playback 60fps 4K 422 IPB at 60fps in 8bit project?

The clip you provided plays back very poorly and start/stopping doesn't help much. I recorded a 60fps clip on my R5 at 60fps 4K CLOG3 IPB which should be 422 and that footage plays through once buttery smooth, THEN starts getting choppy. However the R5 footage reclicking or start/stopping does get it going smoother though. Both tests were done in 8bit full range mode with legacy HEVC/AVC checked, then again with them unchecked and QSV selected. Same results. Vegas makes me sad when you're using a 12900K processor and footage is still clunky. Like come on

. Both tests were done in 8bit full range mode with legacy HEVC/AVC checked, then again with them unchecked and QSV selected. Same results. Vegas makes me sad when you're using a 12900K processor and footage is still clunky. Like come on

My guess is that your 12900K with 422 GPU decoding via QSV helps to hide the HEVC decode problem, rather then fix it. Your CPU is still limited to using a small percentage when decoding HEVC, and if you were to conform that 60fps test file to 30fps or 24fps to play on a project timeline of the same frame rate it would work fine. At 24fps the GPU decoding is doing such a good job the cpu decode is kept very low, but at 60fps it overloads the limited amount of CPU cores HEVC decoding has access to.

Maybe VP20 will be the one

. Both tests were done in 8bit full range mode with legacy HEVC/AVC checked, then again with them unchecked and QSV selected. Same results. Vegas makes me sad when you're using a 12900K processor and footage is still clunky. Like come on

My guess is that your 12900K with 422 GPU decoding via QSV helps to hide the HEVC decode problem, rather then fix it. Your CPU is still limited to using a small percentage when decoding HEVC, and if you were to conform that 60fps test file to 30fps or 24fps to play on a project timeline of the same frame rate it would work fine. At 24fps the GPU decoding is doing such a good job the cpu decode is kept very low, but at 60fps it overloads the limited amount of CPU cores HEVC decoding has access to.

Maybe VP20 will be the one

I'm glad you brought this up because I only tested 24 FPS. Then I would have filmed an entire wedding and filmed many portions in 60 FPS wondering what was going on.

Let's focus on the image distortion. 
I'm happy that there's no problem occured by AMD Hardware for any pixelformat in VEGAS. 
As your hardware @MarkAnthony121 are from new generation, the problem can only be
1, the current Intelgraphic driver or 
2, its compatibility/conjunction with Nvidia. 

As for timeline performance of such source materials, codec with deep compressing + high resolution with max framerate and/or 10bit+422, not only VEGAS but also the other NLEs all have a long way to go. 
Here's my test project in 32bitfloating point (No ACES) fullragne environment, the preview is after dynamicRAM cached. 

Let's focus on the image distortion. 
I'm happy that there's no problem occured by AMD Hardware for any pixelformat in VEGAS. 
As your hardware @MarkAnthony121 are from new generation, the problem can only be
1, the current Intelgraphic driver or 
2, its compatibility/conjunction with Nvidia. 

As for timeline performance of such source materials, codec with deep compressing + high resolution with max framerate and/or 10bit+422, not only VEGAS but also the other NLEs all have a long way to go. 
Here's my test project in 32bitfloating point (No ACES) fullragne environment, the preview is after dynamicRAM cached. 

Yes maybe I will play with the DynamicRAM a little

could you try this file 422 1080P60, Interested if you can play at 60fps in BEST/FULL with your Intel decoder, and report cpu use?

https://www.dropbox.com/s/jrif74cmeqpla3f/R5T_9417_Video_Cut.MP4?dl=0

@Former user was able to play it with the laptop I have with me in VP19... specs with driver versions are: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 {.8935} & Nvidia GTX-1050Ti {511.65}), Win10.

Very jumpy trying to play 4:2:2 HD hevc 60 fps and absolutely no decoding happening. Plays at approx 2.5 fps.

But if I transcode it with ffmpeg nvenc encoder to 4:2:0 keeping all else the same, it plays best-full at almost 60 fps throughout with Intel hd630 utilization around 96% and cpu about 70%. I saw a slight bit of frame rate jitter, dropping to about 59.5 fps at moments, but the preview screen looks smooth as glass. File size dropped to 427 meg (216 mbps) even though I specified cbr 230 mbps bitrate. Script I used is:

ffmpeg -i "R5T_9417_Video_Cut.mp4" -c:v hevc_nvenc -pix_fmt yuv420p10le -profile:v main10 -rc cbr -b:v 230M -minrate 230M -maxrate 230M -bufsize 4096k -an -y out_420.mp4

Note that I also tried the libx265 codec. The output file was slightly smaller (412 meg/209 mbps) but takes about 5x longer to generate and plays not quite as well in Vegas, probably because my Intel igpu decoder doesn't like it as much. And this isn't a particularly powerful laptop. With libx265 it plays in Vegas 60fps most of the time but drops as low as 14 fps for instants.

 

Very jumpy trying to play 4:2:2 HD hevc 60 fps and absolutely no decoding happening. Plays at approx 2.5 fps.

But if I transcode it with ffmpeg nvenc encoder to 4:2:0 keeping all else the same, it plays best-full at almost 60 fps throughout with Intel hd630 utilization around 96% and cpu about 70%. I saw a slight bit of frame rate jitter, dropping to about 59.5 fps at moments, but the preview screen looks smooth as glass. File size dropped to 427 meg (216 mbps) even though I specified cbr 230 mbps bitrate. Script I used is:

ffmpeg -i "R5T_9417_Video_Cut.mp4" -c:v hevc_nvenc -pix_fmt yuv420p10le -profile:v main10 -rc cbr -b:v 230M -minrate 230M -maxrate 230M -bufsize 4096k -an -y out_420.mp4

@Howard-Vigorita Thanks for trying that. I"m also interested in NVENC transcodes and problems with Vegas, I tried 2 transcodes, 1 x265, 1 NVENC HEVC. Result in this case is very similar, Both very smooth full frame rate, and recover quite well after edit points, but I also saw the slight frame jitter you describe, but mainly an NVENC thing.

This lead me to believe the NVENC encode was barely holding on to 60fps, so I changed project to 120fps, and conformed the transcodes (2x playback). Both transcodes played back smoothly 120fps, both frame rates showing slight jitter, how ever the frequency was much higher, with NVENC the frequency much higher than x265. Nvenc took longer to recover after edit points.

Pleasantly surprised by high frame rate 420 HEVC NVENC at 1080P

@Former user Just tried my laptop's onboard Intel igpu to encode the 420 transcode with ffmpeg (-c:v hevc_qsv) and that worked just as well as the Nvidia. Am a little puzzled by my seeing better performance playing nvenc than you. Maybe because I was set to use the Intel igpu for decoding. Just switched it to use the Nvidia and got spotty playback with both qsv and nvenc encodes until a replay. But much better from x265 more like before. Beats me why that is.

Also ran timers on the transcodes and the ffmpeg Nvenc codec was actually 16x faster than x265. Qsv was only 13x faster... same ratio on both my laptop and quicker Nuc8 although gpu and cpu utilization was lower and run-times were quicker for qsv and x265. Btw, playback on the Nuc8 looked the same as my laptop if I used the hd630 igpu for decoding on both. But if I used the Amd Vega-M igpu to decode on the Nuc, no jitter at all on the playback rate... it was rock solid 60p. Wouldn't recommend that in practice however, if there were any fx, multi track, or transitions to deal with. Amd encoders cannot do 10-bit so I cannot compare that.