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.

About OSD setting

Hi,

There are two ways to perform the alpha blending for OSDWIN0MD.

1.OSDWIN0MD.TE0 and (TRANSPVALL, TRANSPVALU, TRANSPBMPIDX)

2.Enabled attribute window (OSDATRMD.OASW)

I will use both of them simultaneously in my scenario.

However, OSDWIN0MD.TE0 will don't work, if I enabled the attribute window.

Could I make it work? (I need the color index works even if the area is in the overlap of bitmap0 and attribute window.)

  • I doubt these two approaches can work simultaneously.If they do, for the pixels that will get blended, the machine won't be able to figure out which blending factor is to be used (BLND0 value or attribute window value).

    Could you please explain why you will need both activated again? I can talk to our designer and see you can approach this.

  • Dear Paul,

    The main reason is I use the UI toolkit (nano-x) that is based on framebuffer to do low level drawing.

    I found it use transparent color index to perform color key, so a color is transparent.

    The toolkit will create a main (top) window to cover all of the screen, and to make it is transparent.

    But, we still need the product UI is 50% transparent in some areas (show time, status...).

    I could use only attribute window to approach this, but I need to find which is color is transparent and to setup attribute for each pixels when drawing.

    Could you advise this issue?

    time and status bar are 50% transparent area.

    menu window has background color which is color key.

  • Actually one correction to my previous post. Attribute window has higher priority (over the region that OSD0 and OSD1 overlaps). According to Figure 36 of the PRG.

    I am still not sure what exactly is being done here. Could you please tell me, which is VID0, VID1, and OSD0, OSD1? some more detail on the size and location?

    You want the time bar and status bar 50% blended, menu window transparency enabled, and the rest of the places showing background?

    I am assuming VID0 is the background ?

  • Paul.Yin said:

    Actually one correction to my previous post. Attribute window has higher priority (over the region that OSD0 and OSD1 overlaps). According to Figure 36 of the PRG.

    Yes, It is current status.

    Paul.Yin said:

    I am still not sure what exactly is being done here. Could you please tell me, which is VID0, VID1, and OSD0, OSD1? some more detail on the size and location?

    You want the time bar and status bar 50% blended, menu window transparency enabled, and the rest of the places showing background?

    I am assuming VID0 is the background ?

    Yes, I replenish some as following.

    VID0 is for live view (background).

    OSD0 is for overlay menu. It covers the full-screen, so it has the transparent color.

    OSD1 is for attribute window.

     

     

     

  • Person,

    thank you for getting back to us. However, we still need clarification on VID1 and OSD0.

    You have 3 small windows (statu, timer, and menu). If OSD0 contains all three, OSD0 will need to be as large as VID0. Is it what is happening right now?

    In the menu sub-window portion of OSD0, you want that transparency function, in the timer an status sub-window portion of OSD0, you want 50% blending, and in the rest of OSD0, you want 0% blending, correct?

  • Paul.Yin said:

    You have 3 small windows (statu, timer, and menu). If OSD0 contains all three, OSD0 will need to be as large as VID0. Is it what is happening right now?

    Yes, It is.

    Paul.Yin said:

    In the menu sub-window portion of OSD0, you want that transparency function, in the timer an status sub-window portion of OSD0, you want 50% blending, and in the rest of OSD0, you want 0% blending, correct?

    Yes, it is one of usecases. I think that the better solution is priority of transparency function higher than attribute window.

    However it maybe not be changed according your previous post, rihgt?

    How could I do for this usecase by HW OSD?

  • Hi, Just checked with the designer, transparency is disabled when attribute window is used.

    I would also try to keep transparency enabled and see what I can do with the rest, but this varies case by case.

  • Dear Paul,

    I am very grateful for your help!

    Waiting your good news!

     

  • Person,

    Sorry about the confusion... I wasn't planning to do anything on my side. I meant I agree with you that YOU should keep transparency enabled and see how you can do the rest. Do you have an FAE or TSR in your region? If so, could you please ask him to contact me?