• Resolved

DM6467 H264 High profile decoder questions

Hi,

    In TI's H.264 decoder for DM6467, how many reference frames are supported?

    We are using TI's H.264 decoder version 01.10.04.00. So far we have been using it to decode the Main Profile video with 1 reference frame.

   However, for the next generation of the s/w we are planning to add the support of decoding the high profile video with upto 8 reference frames.

   I have gone through the documentation and the only mention of the reference frames is not clear. The user guide says' Supports multiple slices and multiple reference frames'. Does this mean the TI decoder can support decoding of H.264 High profile video with maximum (16) reference frames?

  Also I read that h264 decoder "Supports up to 16 MV per MB". Does this mean that some video clips using 32 MVs per MB (in case of B frames), will not be successfully decoded by this decoder?

Thanks,

Santosh Madanwad

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

 

  • Hello Santosh,

    HP is already supported in the TI H264 decoder. Also 720p with 8 reference frames is also not an issue since it will already be supported in the decoder.

    Best Regards

    Feroz

     

  • In reply to K Md Feroz Irfan:

    Hi Feroz,

       Thanks for the response.

       We have now tried the high profile decoding with some standalone sample applications and we have verified that the 8 reference frames is supported.

       I have tried the 720P decoding with 8 reference frames as well as QCIF decoding with 16 reference frames.

       However, we would like to know what are the specific limitations of TI's decoder wrt high profile feature set that we will be required to address.

    Thanks,

    Santosh

  • In reply to Santosh M:

    Santosh,

    The TI decoder supports all features of HP except Monochrome content decoding.

    It also does not support ASO/FMO, but this is a Baseline profile feature.

    Is there any particular feature you are looking for?

    Regards

    Kapil

  • In reply to Kapil Ahuja:

    Hi Kapil,

       Thanks for the response.

       Basically we were looking for the information in terms of the missing features. Specifically the features that if missing will add an application overhead. Your response has answered that concern.

    Thanks,

    Santosh