[MPlayer-dev-eng] [PATCH] making xvid options lavc compatible
D Richard Felker III
dalias at aerifal.cx
Tue Sep 28 16:20:31 CEST 2004
On Tue, Sep 28, 2004 at 03:59:35AM -0400, 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?
huh? of course there's a potential for 2pass audio encoding. think of
a vq based audio codec that uses a default set of vectors during the
first pass, but can optionally search for more optimal ones at the
same time, and then encode a second pass. or, more simple examples...
same thing with huffman tables, or just bitrate distribution for a
desired average bitrate.
now, i don't see lavc getting any of these anytime soon, but it does
More information about the MPlayer-dev-eng