[MPlayer-dev-eng] [PATCH] making xvid options lavc compatible

[Loren Merritt]

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.

--Loren Merritt