[MPlayer-dev-eng] [PATCH] making xvid options lavc compatible
michaelni at gmx.at
Tue Sep 28 12:04:20 CEST 2004
On Tuesday 28 September 2004 10:08, Loren Merritt wrote:
> On Tue, 28 Sep 2004, The Wanderer wrote:
> > Moritz Bunkus wrote:
> >>> Why don't you rename lavc encoding parameters then? For some
> >>> strange reason a lot of them begins with "v", there is no point in
> >>> that. In ffmpeg & xvid they are called more consistently.
> >> Because libavcodec can encode audio, too, so you need both a _v_ideo
> >> bitrate and an _a_udio bitrate.
> > Yes, but does the same reasoning apply for things like "vpass" (since
> > there's no "apass", nor I think any potential for one) and
> > "vmax_b_frames" (since AFAIK there's no such thing as B frames in audio)
> > and so forth?
> Just becasue we haven't implemented 2-pass audio encoding or most
> of the other rate-control options, doesn't mean it doesn't make sense.
> I could even imagine an audio codec with inter-frames, though AFAIK none
> exists now.
> But good examples for renaming are vme, v4mv, vlelim, vcelim.
as long as the old names are still supported for compatibility, such a name
change will probably be accepted
"I do not agree with what you have to say, but I'll defend to the death your
right to say it." -- Voltaire
More information about the MPlayer-dev-eng