On 07 Mar 2014, at 01:16, Hendrik Leppkes <[email protected]> wrote:
> On Fri, Mar 7, 2014 at 12:43 AM, Reinhard Tartler <[email protected]> wrote: >> On Thu, Mar 6, 2014 at 4:12 PM, Luca Barbato <[email protected]> wrote: >>> On 06/03/14 22:08, James Almer wrote: >>>> On 06/03/14 5:47 PM, Luca Barbato wrote: >>>>> On 06/03/14 21:34, Reinhard Tartler wrote: >>>>>> Do we want this in release/10? >>>>> >>>>> Yes. >>>> >>>> The current stable version (x265 0.8) has X265_BUILD == 7. This change >>>> would make libav 10 only support the development branch, and most users >>>> and even distros usually prefer compiling using stable versions of >>>> every library. >>> >>> I'm not sure, given the current level of development at least in Gentoo >>> I'd track it as it comes. >> >> So libx265 is an even worse API bumping nightmare than libx264? > > Its still very new and very much under development. > What do you expect? :) +1 Just because they happen to have releases doesn't mean they have a mature codebase. I'd say, if we keep the wrapper in the release, we should check for a specific API (==). Doesn't really matter if the wrapper's API is ahead of what's in 0.8, there were like 2 weeks between 0.7 and 0.8, the next one can't be more than 3 months away. In any event, we shouldn't ship a release with support for X265_BUILD == 7, 10-bit encoding apparently only works properly with API 9 and later: https://bitbucket.org/multicoreware/x265/commits/eadec14 Tim _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
