• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 290 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How to query HDVICP usage information in TI's h264dec codec on DM6467

_Ralph_
Guru 10685 points

Hi,


if I create an instance of an H264 decoder, how can I check which HDVICP it is running on? Just to know which HDVICPs were currently in use would in fact be enough information for me.

As this is for TI's closed binary H264 codec I'm not quite sure where I should be writing code to do this as the IRES and RMAN Framework Components for C64x+ PDF (spraai15) suggests writing this information into the source code of the algorithm which I don't have access to.

There is an enumerated type called "IRES_HDVICP_RequestType" which is used to request which HDVICP an algorithm should use in an algorithm's source code but obviously this is no use to me.

Thanks,

Ralph

  • 0
    TI__Intellectual 1915 points

    Ralph,

    There is no IRES API that can be used to query the codec for HDVICP usage. However, you can find out which HDVICP the codec is using when the Decoder's Process API calls HDVICP_configure (call back function). The prototype of this function is as follows -

    void HDVICP_configure(IALG_Handle handle,
                          void *hdvicpHandle,
                          void (*ISRfunctionptr)(IALG_Handle handle));

    The 2nd argument here can be used to find out the the HDVICP used by the instance (handle) of the decoder

    Eg. hdvicpId = ((IRES_HDVICP_Handle)hdvicpHandle)->id;

    Regards,

    Anirban

     

  • 0 in reply to Anirban Sengupta
    Guru 10685 points

    Okay, thanks for that. So it is as I thought.

    One more thing; is there some sort of debug or verbose mode in which TI's H264 codec can be created? If not maybe it's something that your users would have use for given the necessary closed nature of the codec; at present the best information the user can get from any binary codec is limited to IVIDDEC2_OutArgs which although useful (vital) for using the codec it would be nice to have some more information about what was going on internally to the codec.

  • 0 in reply to _Ralph_
    TI__Intellectual 1915 points

    Ralph,

    I am afraid there is no debug or verbose mode for DM6467 codecs. We are definitely considering adding such features on future platforms.

    Regards,

    Anirban