On 02/03/14 20:02, Hendrik Leppkes wrote:
> On Sun, Mar 2, 2014 at 7:34 PM, Luca Barbato <[email protected]> wrote:
>> Provide f_strict for avconv usage.
>> ---
>>
>> Spun off the nut patch.
>>
>>  libavformat/avformat.h      | 6 ++++++
>>  libavformat/options_table.h | 5 +++++
>>  libavformat/version.h       | 2 +-
>>  3 files changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/libavformat/avformat.h b/libavformat/avformat.h
>> index ec9c262..215476e 100644
>> --- a/libavformat/avformat.h
>> +++ b/libavformat/avformat.h
>> @@ -1166,6 +1166,12 @@ typedef struct AVFormatContext {
>>       * Must not be accessed in any way by callers.
>>       */
>>      AVFormatInternal *internal;
>> +
>> +    /**
>> +     * Allow non-standard and experimental extension
>> +     * @see AVCodecContext.strict_std_compliance
>> +     */
>> +    int strict_std_compliance;
>>  } AVFormatContext;
>>
>>  typedef struct AVPacketList {
>> diff --git a/libavformat/options_table.h b/libavformat/options_table.h
>> index cc84e1c..61f9bd5 100644
>> --- a/libavformat/options_table.h
>> +++ b/libavformat/options_table.h
>> @@ -59,6 +59,11 @@ static const AVOption avformat_options[] = {
>>  {"buffer", "detect improper bitstream length", 0, AV_OPT_TYPE_CONST, {.i64 
>> = AV_EF_BUFFER }, INT_MIN, INT_MAX, D, "err_detect"},
>>  {"explode", "abort decoding on minor error detection", 0, 
>> AV_OPT_TYPE_CONST, {.i64 = AV_EF_EXPLODE }, INT_MIN, INT_MAX, D, 
>> "err_detect"},
>>  {"max_interleave_delta", "maximum buffering duration for interleaving", 
>> OFFSET(max_interleave_delta), AV_OPT_TYPE_INT64, { .i64 = 10000000 }, 0, 
>> INT64_MAX, E },
>> +{"f_strict", "how strictly to follow the standards (deprecated; use strict, 
>> save via avconv)", OFFSET(strict_std_compliance), AV_OPT_TYPE_INT, {.i64 = 
>> DEFAULT }, INT_MIN, INT_MAX, D|E, "strict"},
> 
> Adding a flag which is already deprecated in its inception seems like
> you should come up with another idea.
> 

When the patch was written avconv had issues with same-named keys. Maybe
it got fixed. I'll check soon.


Thanks for spotting.
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to