OSD scroller; too much resources

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use a low power frontend
2. with an assistive graphics technology such as XvMC or VDPAU
3. send a OSD message to the screen of scroller type.

expected:
smooth tv playback and a scoller of the message sent

actual experience:
As I understand it XvMC and VDPAU only currently work while the OSD is not
being displayed/transitioned. Therefore on a low power system running
scroller means the CPU has to attempt to complete more work than it is able
to and playback stutters and the scroller is slow.

I would prefer to be able to select the OSD template (with preset
text-replacement); Alert, CID or Scroller.

This is a fantastic little feature though; esp. for incoming calls.

thanks

Rich

Original issue reported on code.google.com by richard....@gmail.com on 5 Jan 2010 at 11:15

[GoogleCodeExporter]

AFAIK this shouldn't be a problem with VPDAU - the compositing is done on GPU 
and
VDPAU (the video decoder, etc) does work while the OSD is visible. However, I do
recall that compositing the OSD bitmap causes problems for XvMC, so I guess 
you're
using XvMC? 

A setting allowing one to choose the OSD template for SMS display wouldn't be a 
bad
thing anyway so I'll accept a patch / implement it soon.

Original comment by foobum on 6 Jan 2010 at 12:59

[GoogleCodeExporter]

This issue was closed by revision r81.

Original comment by foobum on 7 Mar 2010 at 2:46

• Changed state: Fixed