Re: [xine-devel] closed caption spu decoder event type removal

[<bar...@t-...>]

hallo miguel,

> > as you might know i'm currently cleaning up xine's event mechanism. this
> > means i have to understand the event types and how they're used - i just
> > came across the close_caption event
> > 
> > i think it can be removed since it is only used to call the cc spu
> > decoder from libmpeg2, but it is not necessary to (ab)use the event
> > mechanism for this, i think libspucc can just be turned into a libmpeg2
> > subdir and called directly.
> 
> Just to make sure we are not limiting possibilities here: what if a new
> input/demux plugin (eg: v4l like) can separate cc data from tv signal
> (line 21 i guess) and send it as BUF_SPU_CC?
> 
> Perhaps now that we have the new plugin loader mechanism it might get
> fixed by letting libmpeg2 to register both mpeg2 and cc decoders.

anyway, see my follow-up posting i noted that more modules are using the
"old", synced event mechanism for cross-module interaction. i don't think
this is the best way of handling thing, but don't want to get into this
too deeply and focus on the public api for now (in fact i had first
forgotten events completely and then when daniel reminded me of this i
had simply copied all event stuff blindly to the public xine header - so
it's definitely time to think this through and find a clean solution.
i've just posted a first proposal of a cleaner interface on this mailing
list, maybe you'd like to have a look?)

cheers,

   guenter

--
"Cutting the space budget really restores my faith in humanity.  It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation."
                -- Johnny Hart