My customer is seeing green artifact on (top) when running the CCS based test application example that ships with H.264 encoder v1.14.03. This is using the default encoder configuration that comes with the encoder package. Attached is copy of reference clip. Is this issue pertains to incorrect configuration - UMV enabling/disabling, luma/chroma swapping? Would appreciate any pointers.
Thanks,
Prateek
PS: Please mark this post as verified if you think it answers your question
To supply further information, here is the testvecs.cfg file I used
0 /* X: Value "1" does Test Compliance and Value "0" dumps the Output */..\..\Test\TestVecs\Config\Testparams.cfg /* Test Parameters File */..\..\Test\TestVecs\Input\test.yuv /* Input File */..\..\Test\TestVecs\Reference\reference.264 /* Output File */
And the Testparams.cfg file I used:
# Input File Format is as follows# <ParameterName> = <ParameterValue> # Comment############################################################################################ Parameters##########################################################################################ImageWidth = 704 # Image width in PelsImageHeight = 480 # Image height in PelsFrameRate = 30000 # Frame Rate per second*1000 (1-100)Bitrate = 3000000 # Bitrate(bps)ChromaFormat = 1 # 1 => XMI_YUV_420P, 4 => XMI_YUV_422ILEIntraPeriod = 30 # Period of I-FramesFramesToEncode = 5 # Number of frames to be coded
I also attached the cmd file I used here.
By the way, I have tried to use BIOS 5.31 and 5.41, Code Generation Tools V6.08, all have the artifacts.
Thanks for help!
Taiwu
Hi Taiwu,
I tried to use the same library (h264venc_ti.l64P) and .cmd file sent by you to Prateek. But still I am not seeing any issue as such.
I am suspecting data cache settings. Did you modify Application file? If yes can you please send to me?
Thank you and Best Regards,
bhushan