8x8 InterBlockSize on DM8147

Has there been any progress in this issue?

Adam,

The settings look fine and proper. We will carry out couple of experiments with the settings you have provided. Meanwhile is it possible for you to get the encoder status using XDM_GETSTATUS through a control call, may be just before the process call ?

Thank you for your response! It is a really big struct, what part of that interesting in this case? Must I print out the whole struct ​​manually?

If possible, yes. 

In spite of what is being set, this will let us know the parameter values which is actually used by the encoder. 

The result is ready. The XDM_GETSTATUS function was called immediately before the H264ENC_encodeFrame.1323.h264EncStatus.txt

Adam,

What is the value set for encodingPreset? It has to be  XDM_USER_DEFINED.

Sorry, I forgot the IVIDENC2_Status section.2110.h264EncExtended.txt

Adam,

All the settings are proper and codec is also taking the values properly. Is it possible for you to share a stream in which you faced the issue (the one generated using the shared settings) ?

The video you have requested is available here: https://drive.google.com/file/d/0B_ifdoHoaEpkQlV2cHhoMXZiNEk

I don't know how behave the encoder, but I see that the block count of received H264 analytic info does not match with imageWidth * imageHeight / ( 8 * 8 ), but same as imageWidth * imageHeight / ( 16 * 16 ).

Oh, I get it. But the analytic info (MV and SAD) contains the motion information with 16x16 block size every case. Is that correct?

Adam, 

The analytic info is returned for every macroblock (16x16). For information regarding analytic info, please refer Appendix D : Motion Vector and SAD Access API of User Guide.