Re: [xine-devel] clarifications regarding OSD

[Miguel F. <mi...@ce...>]

hi,

On Tue, 2003-06-24 at 20:18, Bastien Nocera wrote:
> Heya,
> 
> Yet another mail from me. I've got a bit of trouble understanding how
> the OSD system works:
> 
> xine_osd_show (osd, vpts);
> xine_osd_hide (osd, vpts);
> 
> How do I get the current vpts? As I understand it, a vpts value of zero
> means "now". I'd like to hide the OSD after 5 seconds (that's 5 seconds
> into the song in that case). Is that possible using the existing API, or
> do I have to implement my own timeout to hide it?


you are right: public API has no way of returning current vpts. we
should add that, otherwise this parameter makes very little sense.

what about:

int64_t xine_get_current_vpts(xine_stream_t *stream) ?

i know clock/vpts is not currently a per stream resource, but maybe we
can change that sometime.

> The default font that's being used (sans) doesn't look that well
> anti-aliased. There's mention of using freetype to draw the text, does
> that mean we could ship TTF fonts with xine-lib, would that help having
> text that looks more anti-aliased?


i would guess that most of problems with ugliness of fonts are caused by
the overlay blending code, not the font itself. we do blending at 4:2:0
or 4:2:2 image formats and current code is pretty stupid about handling
the chroma subsampling correctly. that is the cause color leaking
effect, for example.

regards,

miguel