Re: Re: [mpeg2-dev] Exposing flags to libvo.

[Billy B. <ve...@du...>]

Arpi (ar...@th...):

> > > and most of our work (including postprocess, libvo) are common
> > > code, used for many codecs. postprocessing control is outside the
> > > scope of libmpeg2.  libmpeg2 (and other codecs too) needs only a
> > > few lines code to export qscale which is a requred input data for
> > > postprocessing code.
> > 
> > Ok sorry, I was just talking about exporting the qscale stuff then.
> > You're correct that the actual processing code should not be inside
> > libmpeg2.
>
> ok
> but it's something used only by me. it increases cpu usage a few percent and
> has no use for other projects...

  Huh?  If you have a working deblocking filter, I'd really like to get
that in my player too.

> > But please scream real loud if there is something you need exported
> > from libmpeg2 that is not in the base release.
>
> i sent a few patch long time ago - all rejected.  i found it's simple
> to have own version and apply changes immediately.  and now is too
> late to collect them and merge back to main trunk...  at least it's a
> big work and need someone with cvs access and many free time.

  Well, that's a really disappointing attitude.  Personally, I'm pretty
ticked off with walken then for just blatantly rejecting useful patches.
Of course I know the feeling, I sent my patch to walken in July and am
still waiting for some result.  movietime has been waiting for a release
now for at least that long. :(

  So, walken, what do you have to say?  I want to see this issue
resolved in such a way that we get a common, featureful libmpeg2 as
quick as possible.

-- 
Billy Biggs
ve...@du...