DM368 PlatinumCodec 2.10.00.06 ROI Enabling Confusion

Sujith,

Looking at the stream, it does not seem that ROI was triggered.

regards

Yashwant

Yashwant,

the same is working fine with 2.00.00.09 platinum codec release package.

so is there any other setting parameters required in 2.10.00.06 platinum codec library ?

Following are the encoder setting parameters.

------------------------------------------------------------------------------------

------ STATIC PARAMETERS -----------
 videncParams.encodingPreset =2
 videncParams.rateControlPreset =1
 videncParams.maxHeight =1536
 videncParams.maxHeight =2048
 videncParams).maxFrameRate =20000
 videncParams.maxBitRate =10485760
 videncParams.inputChromaFormat =9
 videncParams.reconChromaFormat =9
 videncParams.dataEndianness =1
 videncParams.maxInterFrameInterval =0
 videncParams.inputContentType =0
 meAlgo  =0
 enableVUIparams =0
 enableVUIparams =0
 levelIdc =40
 entropyMode =0
 transform8x8FlagIntraFrame =1
 transform8x8FlagInterFrame =1
 seqScalingFlag  =1
 encQuality =2
 enableARM926Tcm =0
 outputDataMode =1
 sliceFormat =1
 enableDDRbuff =0
 sliceMode  =3

------ DYANAMIC PARAMETERS -----------
 sizeof(IH264VENC_DynamicParams) =212
 videncDynamicParams.inputHeight =1536
 videncDynamicParams.inputWidth =2048
 videncDynamicParams.targetBitRate =10485760
 videncDynamicParams.intraFrameInterval =15
 videncDynamicParams.generateHeader =0
 videncDynamicParams.captureWidth =2048
 videncDynamicParams.captureWidth =20000
 videncDynamicParams.refFrameRate =20000
 videncDynamicParams.forceFrame =-1
 videncDynamicParams.mbDataFlag =0
 videncDynamicParams.interFrameInterval =0
 maxBitrateCVBR =0
 rcAlgo =0
 sliceSize =96
 airRate =0
 interPFrameQP =8
 interPFrameQP =8
 initQ =-1
 rcQMax =51
 rcQMin =8
 rcQMaxI =51
 rcQMinI =8
 enableROI =1
 aspectRatioX =1
 aspectRatioY =1
 mvSADoutFlag =1
 metaDataGenerateConsume =0
 maxDelay =2000
 lfDisableIdc =0
 enableBufSEI =0
 enablePicTimSEI =0
 perceptualRC =1
 resetHDVICPeveryFrame =1

--------------------------------------------------------------------

Hi,

it's very urgent issue. ROI is not getting triggered with the recent version of H264 codec 2.10.00.06

earlier similar problem was there with H263 2.00.00.09 but Mr. Anshuman has looked in to the this and we finally found the problem was

(m_pInArgs->videncInArgs).size = sizeof(VIDENC1_InArgs);

and we had modified to

(m_pInArgs->videncInArgs).size = sizeof(IH264VENC_InArgs)

Now i don't understand where is the problem, even rcAlgo not set to FIXED_QP.

where can be the problem ? 

Hi Sujit,

There seems to be some issue with ROI in 2.10.00.06 release. We are looking into this.

Will update you ASAP.

Rgds, mahant

Thanks Mahant,

i will be waiting for this, its very urgent as we are in to final production stage this month. 

Sujit,

I have already got a note about this from our regional TI office located at your place of work. We are working in it, will update the schedule in few hours. Since the release may take some time to get uploaded on web, I will work on a way so that it can be given directly to you through our regional TI office.

regards

Yashwant

Thanks Yashwant,Mahant

ohh yes, my boss had discussed it with TI concerned person at our place.

as our deadline for production to start up is 11th Jan, i am little worried.

Hi yashwant,

can you please update me at what time we will me receiving the new release ?

we are waiting for that as you know already today 11th Jan is the our final relese for production.

Sujit,

We will be able to make release by today eve, India time.

regards

Yashwant

Thanks for the information Yashwant,

our local TI contact has informed the same now. we will plan accordingly.

Hi Yashwant,

we have received the release version 2.10.00.07.

i have attched 2 recorded files one in chain mode and another in oneshot mode with 2.10.00.07 version ROI enabled ( 800x600 resolution, 20 fps, 512 kbps).

can you please check wether ROI is triggered in the video stream or not and conform, as i am not able to find out a visible difference in the ROI area.

Sujit,

ROI is getting triggered in the area. I can see QP difference within the frame.

The reason for not finding visible difference could be the following

- I and IDR frame come back to back. You may like to set IntraFrameInterval =0 and IDRFrameInetrval=<userdefined>. Or at least have both of them same value. Currently it looks like it is 20 and 21. This will eat up bits and nothing much will be left for P frames.

- You can put the ROI region to text, so that it is easily noticiable.

- You can play with ROI priority, Value 4 will give most prominent difference.

regards

Yashwant

Yashwant,

 my earlier recorded stream both IntraFrameInterval = 15 and IDRFrameInetrval=15 and ROI priority 4.

i tried with IntraFrameInterval = 0 and IDRFrameInetrval=15 also some different combinations.

but there is no visible difference like 2.00.00.09 version.

please suggest some setting to make a visible difference like the aerlier 2.00.00.09, otherwise our QA team will not pass ROI feature.

Can you send the stream whcih you generated with 2.00.00.09 with the similar setting and similar i/p content ? We want to compare it with 2.10.00.07

regards

Yashwant

ok,

give me 30 mins time. i will be sending.

Yashwant,

please find the attched 2 avi files in 2.00.00.09 and 2.10.00.ersion of h264 platinum codec release.

Sujit,

- It looks like 2.10.00.07 stream does not have ROI. It was there in the last zip which you sent using 2.10.00.07. What is the priority which you used. We have found that ROI  priority 1 and 3 does not working fine. I am sorry for this. But ROI priority 2 and 4 works fine and the o/p is similar to 2.00.00.09. So we suggets you to ti use ROI priority 2 and 4 only in your app.

- We also see that the IDR and I frame period is not OK. Why they are coming with just 1 frame diff. They should overlap. So my suggestion is to make intraFrameInterval = 0 in your app, for ever unless you specifially need them to be diff.

- The setiings for both the streams also does not seems to be same, They seems to have used diff RC and diff bitrate.

regards

Yashwant

Hi Yashwant,

 with quality level 2 and 4 it is working absolutely fine, even roi area quality is much better than the 2.00.00.09 version.

Thank you very much.

But as you said with level 1 and 3 it is not working.

so when can we expect the modified version of the same ?

Thanks Yashwant,

thanks to your team also.

i think with same version number 2.10.00.07, which will be updated on the web by next 1-2 weeks will have this issue fixed .

The build id will be different, i.e. the last digit set will be greater than 07. But the version tree(2.10.00) is same, so no API change and hence release will be a drop and replace for you.

regards

Yashwant