• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 100 subscribers
  • Views 496 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.

OpenMAX: "OMX_TI_IndexConfigAlgEnable"

_Ralph_
Guru 10685 points

What does the "OMX_TI_IndexConfigAlgEnable" parameter do? I can't find any documentation or even source code on it.

Thanks,
Ralph

  • 0
    Guru 10685 points

    Also, what does "OMX_TI_IndexConfigVFCCFrameSkip" do?

    Edit: others:

    "OMX_Video_Enc_Med_Speed_High_Quality"

     

  • 0
    TI__Mastermind 25055 points

    Ralph,

    Which device family is this for?  I will move it to that device's forum so that it gets addressed.

    Regards,
    Marc

  • 0 in reply to MarcPyne
    Guru 10685 points

    Hi Marc,

    It's for the DM8168. I thought I had the right forum but maybe not!

    Thanks,
    Ralph

  • 0 in reply to _Ralph_
    TI__Mastermind 25055 points

    Hi Ralph,

    I'm going to move it into the DM816x Forum, and ask the OMX guys to look at it.

    Regards,
    Marc

  • 0 in reply to MarcPyne
    TI__Intellectual 1085 points

    Hi Ralph,

    OMX_TI_IndexConfigAlgEnable - is used for switching off the algorithm. For example, bypassing say Deinterlacer (VFPCDEI) for progressive content but still to have the dual scaler operations - In this case one can configure VFPC to bypass the dei part of the h/w ip.

    OMX_TI_IndexConfigVFCCFrameSkip - is used to get say 30FPS from 1080p60 source. Other scenarios that one may require this configaration is to temporarily reduce the DDR b/w requirements.

    thanks and regards

    Tarakesh.

  • 0 in reply to MarcPyne
    TI__Expert 6535 points

    Ralph,

    OMX_TI_IndexConfigAlgEnable is for enabling algorithm in VFPC. e.g. DEI will not do de-interlacing if algorithm is bypassed. Capture_encode example uses this index.

    OMX_TI_IndexConfigVFCCFrameSkipis for dropping frames in capture, as per skip mask (30bit).

    Regards

    Vimal

  • 0 in reply to Vimal Jain
    Guru 10685 points

    Thanks for the replies; some further questions:

    1. OMX_TI_IndexConfigAlgEnable- why would you go to the effort of setting up an OpenMAX chain of components only to then effectively bypass one of them by unsetting this parameter?
    2. OMX_TI_IndexConfigVFCCFrameSkip - how does the frame skip mask work?
    3. OMX_Video_Enc_Med_Speed_High_Quality - what is this?

    Ralph


  • 0 in reply to _Ralph_
    TI__Expert 6535 points

    1. OMX DEI component has one input and two output and each of this can be independently scaled, so if you have progressive input and just want two o/p (420 & 422) with scaling , alg would be disabled but pipeline remains same. Capture_encode example is using bypass of DEI.

    2. Frame mask is binary 30 bit value, so 0x2aaaaaaa is (0x101010..)dropiing alternate frames.

    3. This is one of the codec parameters for setting encode_preset in h264  for quality. We plan to provide all codec supported parameters configurability in next release.

    Regards

    Vimal