[MPlayer-dev-eng] [PATCH] synch to new x264 revision
Guillaume POIRIER
guillaume.poirier at ifsic.univ-rennes1.fr
Sat Sep 25 19:25:04 CEST 2004
Hi,
Le sam 25/09/2004 à 15:17, Jan Knutar a écrit :
> On Saturday 25 September 2004 15:18, Diego Biurrun wrote:
>
> > > > > All codecs are by default fast, even if their maintainers dislike it.
> > > > > For example, I know that XviD devs would prefer some "basic" quality
> > > > > optimization on per default.
> > > >
> > > > I haven't seen that rule written in stone anywhere, I doubt patches
> > > > for it would be rejected.
> > >
> > > Glad to hear that... So, should I ask what XviD devs would prefer on by
> > > default, You think there's a chance to have those patches included?
> >
> > Sure, why not.
>
> IIRC, the issue was that there were options such as trellis:chroma_opt:chrome_me,
> and what not, but if they were on by default there was no way to turn them off.
Then I guess it makes sense to have "flag" options stay (off) that way
and have "gradual" options set to whichever the users prefers.
That looks like a pretty simple way to have "not so stupid" defaults.
> Which
> seems a bit silly to me, since atleast once upon a time the first page of mplayer(1)
> said that every flag has a noflag counterpart. Actually, it says so still, but it's obviously
> not true for many things, however, I see no reason why xvid couldn't have no* options
> for turning off CPU intensive options.
I currently don't know if it would be simple to do that. Does lavc
support that?
Regards,
Guillaume
--
Le capitalisme, c'est l'exploitation de l'homme par l'homme. Le
communisme, c'est le contraire. -+- Coluche -+-
More information about the MPlayer-dev-eng
mailing list