Roman Huts

The issue has now been fixed and will be publicly available in an upcoming driver release.

According to the H264 and H265/HEVC syntax, chroma location fields are optional and their presence is controlled by a Boolean flag (`chroma_loc_info_present_flag`). The AMF encoder sets this flag to 0,...

Yes, you are right. We will add an AMF property for applications to properly code the chroma location syntaxes inside the VUI parameters.

### Issue 1 - **AV1** produces different bitstreams with the provided settings so the original reported issue cannot be reproduced. - For **HEVC**, the difference between CBR and VBR lies...

The latest public driver 23.7.1 has been tested on our side to have QVBR support. As confirmed by our internal testing, 23.5.2 did not have QVBR support for the 4500U...

Closing. Please open a separate issue if there are any additional bugs.

The bitrates were not set for comparison for each case. The bitrates vary and this would explain the corresponding quality differences. For example, in the two AMD/Intel HEVC cases, you...

There is a bug and it will be fixed in an upcoming release. In the meantime, here is a workaround to allow you to proceed with your development. Since it...

> I am a little bit worried about these defaults. This is primarily because it enables Pre-Analysis (PA). PA eats a decent chunk of traditional GPU compute, and this can...

> > PAEngineType=11(DX12) and PAEngineType=10(Vulkan). > > Where are you getting those values from? [The docs](https://github.com/GPUOpen-LibrariesAndSDKs/AMF/blob/master/amf/public/include/components/PreAnalysis.h#L95) don't say anything about DX12 support > > [Nevermind found it](https://github.com/GPUOpen-LibrariesAndSDKs/AMF/issues/439#issuecomment-1917886326) @rhutsAMD could you...