[Bug 691617] avenc_aac: errors out with "encoder not initialized"

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=691617
  GStreamer | gst-libav | unspecified

--- Comment #8 from Greg Rutz <greg at gsr-tek.com> 2013-05-03 18:01:16 UTC ---
More specifially, the "-strict" argument specifies how you would like the codec
to behave with respect to its associated specification.  The strictness levels
are described in avcodec.h:

    /**
     * strictly follow the standard (MPEG4, ...).
     * - encoding: Set by user.
     * - decoding: Set by user.
     * Setting this to STRICT or higher means the encoder and decoder will
     * generally do stupid things, whereas setting it to unofficial or lower
     * will mean the encoder might produce output that is not supported by all
     * spec-compliant decoders. Decoders don't differentiate between normal,
     * unofficial and experimental (that is, they always try to decode things
     * when they can) unless they are explicitly asked to behave stupidly
     * (=strictly conform to the specs)
     */
    int strict_std_compliance;
#define FF_COMPLIANCE_VERY_STRICT   2 ///< Strictly conform to an older more
strict version of the spec or reference software.
#define FF_COMPLIANCE_STRICT        1 ///< Strictly conform to all the things
in the spec no matter what consequences.
#define FF_COMPLIANCE_NORMAL        0
#define FF_COMPLIANCE_UNOFFICIAL   -1 ///< Allow unofficial extensions
#define FF_COMPLIANCE_EXPERIMENTAL -2 ///< Allow nonstandardized experimental
things.

After discussing with Tim, I will propose a real fix to this problem.  We will
add a new enum property to all libav encoders (just encoders for now) that
allows you to specify the strictness level for the AVCodecContext.  This will
allow GStreamer users to 1) control the spec-adherence of their encoders and 2)
more specific to this bug, allow the use of encoders marked as "experimental"

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.