On 10/18/12 10:47 PM, Nathan Caldwell wrote:
and strict_std_compliance is not FF_COMPLIANCE_EXPERIMENTAL.

This moves the check from avconv to avcodec_open2().
---
I am not sure of the correct wording of the error message. Telling the user
to set '-strict experimental' doesn't make much sense for a library user, but
telling the user to set 'strict_std_compliance == FF_COMPLIANCE_EXPERIMENTAL'
makes even less sense for avconv users.

  avconv.c           |   19 -------------------
  libavcodec/utils.c |   23 +++++++++++++++++++++++
  2 files changed, 23 insertions(+), 19 deletions(-)

A simpler solution could be adding AVERROR_EXPERIMENTAL and have avconv manage it normally.

Sounds good to you?

lu

_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to