Udo Richter wrote:
On 18.04.2009 15:36, Luca Olivetti wrote:
On Sat, 18 Apr 2009 13:28:24 +0200
Udo Richterudo_rich...@gmx.de wrote:
This is mostly what the VDR skin interface already provides: A
semantically structured description of the interface. Most skins
translate this into
On 14.04.2009 01:42, Torgeir Veimo wrote:
This would of course require information from vdr in a slightly
different form; ie. semantically instead of pixels. I'd suggest trying
to get the OSD information as HTML from VDR, then allowing the frontend
to render it in any way it deems suitable,
On Sat, 18 Apr 2009 13:28:24 +0200
Udo Richter udo_rich...@gmx.de wrote:
This is mostly what the VDR skin interface already provides: A
semantically structured description of the interface. Most skins
translate this into a bitmapped OSD view, but they don't have to. The
skincurses plugin
On 18.04.2009 15:36, Luca Olivetti wrote:
On Sat, 18 Apr 2009 13:28:24 +0200
Udo Richterudo_rich...@gmx.de wrote:
This is mostly what the VDR skin interface already provides: A
semantically structured description of the interface. Most skins
translate this into a bitmapped OSD view, but
On Sat, Apr 18, 2009 at 10:37 AM, Udo Richter udo_rich...@gmx.de wrote:
This is mostly what the VDR skin interface already provides: A
semantically structured description of the interface. Most skins
translate this into a bitmapped OSD view, but they don't have to. The
skincurses plugin for
Quoting Torgeir Veimo torg...@pobox.com:
Why not go all the way and implement an opengl rendered OSD with vdpau?
This would of course require information from vdr in a slightly different
form; ie. semantically instead of pixels. I'd suggest trying to get the OSD
information as HTML from VDR,
Hi,
Klaus Schmidinger wrote:
On 13.04.2009 20:11, VDR User wrote:
There's been recent talk in #xine-vdpau about expanding VDR to allow
for a high color osd. Does anyone happen to know any bad implications
of changing tIndex from uint8_t to a uint16_t for allowing access to
more of a color
Gerald Dachs wrote:
Quoting Torgeir Veimo torg...@pobox.com:
Why not go all the way and implement an opengl rendered OSD with vdpau?
This would of course require information from vdr in a slightly different
form; ie. semantically instead of pixels. I'd suggest trying to get the OSD
There's been recent talk in #xine-vdpau about expanding VDR to allow
for a high color osd. Does anyone happen to know any bad implications
of changing tIndex from uint8_t to a uint16_t for allowing access to
more of a color palette?
___
vdr mailing
On 13.04.2009 20:11, VDR User wrote:
There's been recent talk in #xine-vdpau about expanding VDR to allow
for a high color osd. Does anyone happen to know any bad implications
of changing tIndex from uint8_t to a uint16_t for allowing access to
more of a color palette?
I believe the right
Am Mon, 13 Apr 2009 20:17:50 +0200
schrieb Klaus Schmidinger klaus.schmidin...@cadsoft.de:
On 13.04.2009 20:11, VDR User wrote:
There's been recent talk in #xine-vdpau about expanding VDR to allow
for a high color osd. Does anyone happen to know any bad
implications of changing tIndex
On Mon, Apr 13, 2009 at 11:31 AM, Udo Richter udo_rich...@gmx.de wrote:
This will hopefully be a true-color OSD with transparency and the
ability to scale to the needs of the output device? Like having a HD OSD
even on SD playback? And (even if these times are almost history) the
ability to
12 matches
Mail list logo
