Mikhail_AMD

I follow your conversation in FFmpeg mail list and appreciate your efforts. Currently in AMF encoder there is no clear indication by return code if more input is needed before...

This needs to be supported by HW. AMF provides access to what is available. We started Wiki with HW information: https://github.com/GPUOpen-LibrariesAndSDKs/AMF/wiki/GPU%20and%20APU%20HW%20Features%20and%20Support

"All codecs are 4:2:0"

Sorry for the delay. Few things need to be discussed: 1. Flush is not needed to be called after Drain + QueryOutput loop. Flush means that the caller is not...

4:4:4 and 4:2:2 codecs are currently not supported by hardware.

Could you please describe your call sequence, in particular, did call Drain() and QueryOutput() in a loop till AMF_EOF to get last few frames?

According to Vega analyzer the video stream in the file is seriously corrupted. 

In these streams timestamps on video and audio streams are far away from each other. You can add the tracing line below at the end of AMFFileDemuxerFFMPEGImpl::AMFOutputDemuxerImpl::QueryOutput() method in FileDemuxerFFMPEGImpl.cpp:...

I extracted elementary streams from the TS files with this CMD: **ffmpeg.exe -i %1 -vcodec copy -bsf h264_mp4toannexb -an %1.h264** FFmeg complained about corruption and I believe skipped some frames....

This common issue and is timing problem. In a single-thread implementation pulling all outputs is triggered by submission of input. Consider scenario that the app may experience: inputs submitted faster...