SPU decode is now going to be done in the input plugin.
There are two types of overlays.
1) Subtitle overlays, where SHOW and HIDE PTS values are known and fixed.
The video_out could keep handle these as it does now.
2) Menu button highlighting, where SHOW and HIDE PTS values depend on user
key presses and mouse movements.
These are not currently supported in the video_out.
I suggest we have 2 APIs: -
1) for subtitles
2) for overlay messages (menu buttons, OSD etc.)
Also, we need a method for reducing the delay between demux and display.
Alternatively, we need to give the input plugin access to the metronom.
> -----Original Message-----
> From: xine-devel-admin@...
> [mailto:xine-devel-admin@... Behalf Of Guenter
> Sent: 21 July 2001 15:00
> To: Rich Wareham
> Cc: xine-dev
> Subject: [xine-devel] Re: SPU modifications
> Hi Rich,
> On Fri, 20 Jul 2001, Rich Wareham wrote:
> > On a slight implementation note, I may need to change the input API so
> > that an input plugin can get the xine_t being used at the moment (So it
> > can send/receive events).
> hum, I'm not sure if this is the best way to send events - if you contact
> the xine engine directly your events will arrive to early because the
> stream packets are still buffered in fifos.
> Perhaps input->read(...) could simply return a flag indicating that
> additional message information is available. More important,
> input->read_block could simply return that information in some additional
> fields in the buf_element_t* it returns
> time is a funny concept
> xine-devel mailing list