• State Answer Suggested
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 154 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.

OSD window addr[0][0] set

billy david
Genius 3900 points

hi all.  i want to know that whether i do like following will have some  wrong result

i create one OSD buffer once,and set the window parameter like following,not like the demo once alloc all window buffer,then use the bufOffset.if i want to modify the osd ,i free the window buffer ,then create again

chWinPrm->winPrm[winId].addr[0][0] = bufInfo.physAddr;


tks

  • 0
    TI__Guru 59700 points

    If you free and alloc OSD buffer when OSD is active it will result in some artifacts on the display

  • 0 in reply to Badri Narayanan
    Genius 3900 points

    yes Badri.when i free and create the osd again that will have something flash across,then the osd display normally.

    but when i just do the test for disable or enable the osd,or change the startX/startY of the osd ,it also has the  appearance.i found the operator just do that

    System_linkControl(
    SYSTEM_LINK_ID_ALG_0,
    ALG_LINK_OSD_CMD_SET_CHANNEL_WIN_PRM,
    &g_osdChParam[0],
    sizeof(AlgLink_OsdChWinParams),
    TRUE
    );

    whethe some way can fix this problem?

    tks