[vdr] How's the 24 bit OSD VDR coming?
Klaus.Schmidinger at tvdr.de
Wed Mar 9 22:49:11 CET 2011
On 09.03.2011 12:54, Petri Hintukainen wrote:
> Klaus Schmidinger wrote:
>> On 08.03.2011 22:31, Udo Richter wrote:
>>> Am 08.03.2011 22:09, schrieb Klaus Schmidinger:
>>>> Don't get too excited about the TrueColor OSD, though.
>>>> What comes with VDR is only the basic OSD platform that
>>>> allows plugins to use full screen 32 bit ARGB color,
>>>> with alpha blendable pixmaps and such.
>>> Do you have any numbers on OSD speed for, lets say, some prototype
>>> output device you may have at hand?
>>> An old-style 720x576x8 display has just 400k size, HD RGB32 however has
>>> 6Mb. This could limit display update speed notably for animations or
>>> video overlays using OSD. Would be nice to know how much is possible.
>> Sending the full screen OSD with 32 bit ARGB to the TT-S2 6400 takes
>> roughly 500ms. Most of the time, though, only small portions of the
>> screen are modified and need to be transferred to the hardware (or
>> whatever device actually displays the OSD).
> What kind of interface is provided to output device plugins ? It would
> be nice if output devices could hook to the drawing primitives instead
> of plain ARGB OSD plane.
> When the output device is behind network, transferring just the
> primitives would give huge speed gain (drawing background using filled
> rectangle, drawing text using cached pixmaps etc.). Using derived
> cBitmap class would allow preloading pixmaps so that those could be
> transferred to the device memory in advance.
It's exactly that way.
The new cPixmap class can be reimplemented by the OSD device to
make all the actual processing happen in a device specific way.
The default implementation works on a local array of 32 bit
More information about the vdr