OSD on blank window in Swms can not be flushed

Ri-Ping YU

Hi , everybody!

I'm using RDK4.0, 8168.

There is one OSD on Swms full screen layer, not individual window in SwmsLINK, to display real time, which should be flushed per second.

If the OSD covers on window which show active image, it work properly; but if it covers on blank window, it cannot be flushed per second, its display will be overlapped, depicted below

This issue can be fixed according to the method metioned in url:

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/230739/974806.aspx#974806

But, if do so in RDK 4.0, it'll be run-time error

[m3vpss ] 16450: Assertion @ Line: 3176 in links_m3vpss/swMs/swMsLink_drv.c: pInFrame->appData != NULL : failed !!!

How can I fix this issue?

Appreciate for any suggestion!

over 11 years ago

0 Badri Narayanan over 11 years ago

TI__Guru 59700 points

No this workaround mentioned in the post is not valid for RDK 4.0. If you have OSD after swms you should set swmsPrm.outputBufModified = TRUE in swms createPrms. Don't make any other modifications to swms

0 Ri-Ping YU over 11 years ago in reply to Badri Narayanan

Expert 1460 points

Thanks for your reply!

one more question, the layout mode of swms is depicted below, the part screen area where OSD displayed on is not allocated to any window, in this situation, OSD can not be flushed.

how can I fix this issue?

expexte your further suggestion!

0 Badri Narayanan over 11 years ago in reply to Ri-Ping YU

TI__Guru 59700 points

This is an issue because swms will update only the window portion of the buffer and the remaining background is never modified. The only workaround I can think of is to have a blank swms window below your OSD coordinates.THis way the older OSD content will get cleared on every frame.

Processors

Processors forum

OSD on blank window in Swms can not be flushed