[MPlayer-dev-eng] [RFC] EOSD improvements
Grigori Goronzy
greg at chown.ath.cx
Mon Aug 2 21:35:20 CEST 2010
On 08/02/2010 12:34 PM, Reimar Döffinger wrote:
> I am suggesting to build the foundation (passing the image data through
> the filter chain via EOSD etc.) and then build the extensions to it
> (RGBA support) instead of first building the extensions and then see
> if we can shove the foundations below it.
>
What I am thinking of actually isn't that far off IMO, maybe we're
simply misunderstanding each other? :)
a) pull all libass specifics/dependencies out of the EOSD, vo and vf_ass
code and extract an indedependently usable interface while not breaking
any current functionality.
b) extend EOSD with RGBA bitmap support and possibly more; what exactly
depends on the possible use cases we can think of and what hardware is
capable of.
d) Modify spudec (and old-style OSD) to use the EOSD interface. IMHO
spudec is a good fit to be a generic higher-level subpicture interface
that deals with timing, caching, bitmap conversion, scaling, etc.
> I just think that we now have two OSD things. And I simply can't shake
> the suspicion that if everyone starts at the most unrelated part and at
> the end figures out that it all just doesn't fit together we will end up
> with 4 or more when we finally have full coloured subs and none of the will
> work properly.
If we get as far as having a versatile low-level OSD rendering
interface, I doubt it'll happen.
Grigori
More information about the MPlayer-dev-eng
mailing list