It's vegas it'self that doesn't like the HEVC 422. You can turn of GPU processing and decode and will still crash if you force it to load. Needs to be updated.

I know Nvidia hardware does not support 4:2:2 decoding and does not appear to have any such plans (see: Nvidia codec sdk) I don't think AMD does either. But Intel is reported to have it on it's new Tiger Lake architecture. Coming soon. At least according to this Intel readme. And reported to be fully functional on the coming new Intel Xe pcie gpu board which was supposed to be out by now but doesn't seem to be coming till next year sometime.

Yes I've been having these discussions and I thought that supporting the 4:4:4 10 tier would implement all the other codec variants, including 4:2:2.

However looking at this SDK it paints a bleak picture: "** 4:2:2 is not natively supported on HW".

With H.264 4:2:2 decode is possibly never going to happen but H.265 4:2:2, the ipad pro can apparently hardware decode as well as those new mobile intel gpu's. This raises the possibility that the new Nvidia cards may also do 4:2:2 decode

With H.264 4:2:2 decode is possibly never going to happen

we are talking about 265, HEVC. 264 is pretty common and sup[ported now, I don't see that as an issue

quote from fb

Mazze Aderhold Peter - the decode support matrix only shows supported flavors. If supporting 4:4:4 means that all lower sampled flavor work as well, why would they still explicitly list 4:2:0 😉 ? That being said - I‘ve worked on the implementation of the NVDEC/NVENC SDK - and I can assure you, it is clearly documented that 4:2:2 is not supported. I‘m afraid it‘s just that.

With H.264 4:2:2 decode is possibly never going to happen

we are talking about 265, HEVC. 264 is pretty common and sup[ported now, I don't see that as an issue

:

No consumer GPU's decode H.264 4:2:2 that I"m aware of. Commercial versions exist but are extremely expensive. Apple has the afterburner, and for PC there's various Matrox cards. The expense doesn't come down to the hardware used and it's for that reason it's unlikely to come to a consumer GPU, though i'd love to be wrong

I am wondering if a color space upconversion to 4:4:4 und thus hardware compliant decoding would yield better results than just relying on CPU to crunch those numbers. the bitrate overhead is fairly negligible it seems

I am wondering if a color space upconversion to 4:4:4 und thus hardware compliant decoding would yield better results than just relying on CPU to crunch those numbers. the bitrate overhead is fairly negligible it seems

 

Or, we could hope that a future with 4:4:4 color integrated into smaller and accessible product line comes sooner then later.

Demand & Supply is king.

this from the nvidia developer forum (mind you, this response is from 2017) suggests a 4:4:4 workaround should be possible

If you're transcoding your camera footage why would you convert HEVC 4:2:2 to HEVC 4:4:4 an extremely porocessor heavy and slow action(you're not going to be using Nvenc for encode) so that your computer still has to struggle with HEVC when editing, wouldn't you just transcode to an editor/cpu friendly 4:2:2 intermediate?

If the new Nvidia cards have HEVC 4:2:2 decode the benefit is clear, if you didn't want to transcode you likely don't need to (depending on cpu) but I don't see the benefit in your proposal unless I don't understand the color upconvert process and it doesn't require transcoding

I would hope that transforming 4:2:2 into a 4:4:4 color space can be done without major recompression, like displaying a 1080 picture on a 4K screen, maybe just changing a few flags? If this could be done rather simply when VP handballs the stream to NVDEC which then use the full HW acceleration to decode the stream.

But as you say, maybe this is just naive wishful thinking. Hopefully the Devs could shine a light on this

I don't know the pro's or con's of that, but if there is no advancement in 4:2:2 color decode on GPU with upcoming Nvidia gpu's they'll be forced to do something like that (if that's realistic - not a technical person) as 4K and 8K 422 HEVC become more standardised

I was looking for Nvidia Ampere RTX3000 leaks and noticed this from back in May, it's about the new data center Ampere GPU. It compares the old Pascal version to the new Ampere one. Disturbingly nothing was upgraded with h.264/h.265 decode between Ampere and Turing. Can only hope it's a gtx1650 type situation where for some reason they're using the new chip but use old Nvenc/NvDec

The funny part is, as I read through the HEVC white papers, it seems that: if you support a tier -say MAIN 4:4:4: / 10bit, then all the other subordinates (4:2:0 and 4:2:2, and 8 Bit variants) must be supported. If nVidia isn't doing that then they're strictly speaking non-conformant, for whatever its worth. One way to find out what the graphics chip can do is query colour space abilities with their downloadable SDK tools (would be nice if someone could do that). Not sure what an outcome this will deliver, or if not, if a simple GFX driver / FW update can fix this, or if this is indeed a hardware restriction.

They may not support Main 4:4:4 10 or Main 4:4:4 12. Have you read anything that says they do?

I've asked in the past for people with turing (other than 1650) to try and attempt playback of HEVC 422 in a media player, and report if any GPU decode, nobody bothered to try. During google searches, I've only seen complaints about HEVC 422 not using GPU decode, never positive comments about HEVC 422 using gpu decode

I don't believe Nvidia can decode it. Intel may have stumbled upon a niche set of users who will come back to intel cpu if only for HEVC 422 decode if AMD and Nvidia gpu's don't deliver, though they need to put those iGPU's into desktop cpu's not just mobile

turing chipset will do HEVC 4:4:4: 8/10/12bit yes https://developer.nvidia.com/video-encode-decode-gpu-support-matrix

but that doesn't really mean anything for 4:2:2 sadly, as you pointed out @Former user . HEVC being harsh on CPU already is not gonna help for editing.

Is there anyone on this forum with a touring RTX of sorts to check this out?

As there is nothing to say it conforms to a Main Profile, it's reasonable to assume it doesn't and only decodes what is specifically says, which seems odd, but when oddness is related to AVC/HEVC hardware it's probably a licencing/patent issue then a technological one.

HEVC decoders that conform to the Main 4:4:4 12 profile must be capable of decoding bitstreams made with the following profiles: Monochrome, Main, Main 10, Main 12, Main 4:2:2 10, Main 4:2:2 12, Main 4:4:4, Main 4:4:4 10, Main 4:4:4 12, and Monochrome 12.

With H.264 4:2:2 decode is possibly never going to happen but H.265 4:2:2, the ipad pro can apparently hardware decode as well as those new mobile intel gpu's.

The new Ipad Air also does 4:2:2 HEVC GPU decode. It is cheaper than Ipad Pro, but quite a lot more than standard ipad

Received a response from the Sony team informing the new A7Siii will also have some HEVC 10-Bit 4:2:0 options, this could well alleviate the problem at the cost of a little bit of colour:

It sounds like they're fixing a bug where vegas can't open 10bit 4:2:0 HEVC files with PCM audio. I call it a bug because it will open A7Siii 10bit 4:2:0 HEVC if you strip the pcm audio and replace with AAC Audio track. As far as upgraded support for a codec, that's quite minimal, but still good