[FFmpeg-devel] feature proposal: custom size for OGG pages (original) (raw)

Måns Rullgård mans
Mon Jan 24 16:03:15 CET 2011

Andres Gonzalez writes:

On 20/01/11 18:58, Ronald S. Bultje wrote:

Hi,

2011/1/20 Andres Gonzalez: [...]

The question is: Is it okay to add an arbitrary feature-specific parameter? Or, do you have any other suggestion to achieve this? Yes, but not in the generic API. Please look into muxer-specific AVOptions, some muxers already use it. Could you put an example of this, please? Let's say: option, muxer and some of the files involved. I'm not sure to understand you when you mention the "generic API". For example, I've seen the array "AVOption options[] = {" in libavformat/options.c; if I'm not mistaking, adding an option here would imply adding a member of AVFormatContext. Is this true? and, is this the right way?

For an example, see the recently added flag to select id3v2 tag version: http://git.ffmpeg.org/?p=ffmpeg.git;a=commitdiff;h=22272f6

-- M?ns Rullg?rd mans at mansr.com

More information about the ffmpeg-devel mailing list