codec library

If the .xem3 build successfully you don't have to change anything in VIDEO_M3_CODE_SIZE,VIDEO_M3_DATA_SIZE.

The algorithm memory requirement also doesn't changes from Decoder version to version so there should be no need to increase Memory.defaultHeapSize 

hello badri,

thanks for your reply.

I found the size of .xem3 in each rdk version is a little samller than the value of VIDEO_M3_CODE_SIZE.

And after using the latest codec library, the size of .xem3 is over the value of VIDEO_M3_CODE_SIZE too much.

Will it have any side effect?

hello Badri,

Would you mind to explain the meaning of following?? thanks

 VIDEO_M3_CODE_SIZE.

 VIDEO_M3_DATA_SIZE

I think the VIDEO_M3_CODE_SIZE defines the memory size for codes and VIDEO_M3_DATA_SIZE for data

Hi Bing

    thanks.

Hi Badri,

    By testing, it looks like this mis-match size of *.xem3 and VIDEO_M3_CODE_SIZE will cause hang in either A8 or M3.  Because we update all codec libraries such as h264, mjpg, mpeg4(which are newer than these in rdk4.1) to fix other bugs. Would you mind to help to clarify if something need to be changed under dvr_rdk/mcfw/src_bios6/cfg/ as we just change codec libraries. Thanks...

There is no change required in any cfg gile to migrate codec version. Make sure you are cleaning and building.