On Tue, Jul 19, 2016 at 12:59 PM, Sean Bright <[email protected]> wrote: > On 7/19/2016 10:35 AM, Matt Fredrickson wrote: >> >> Response below. >> >> On Mon, Jul 18, 2016 at 7:18 AM, Dennis Guse >> <[email protected]> wrote: >>> >>> Technical Details (at the moment the modifications are based upon >>> 13.6.0): >>> * Enabled OPUS (with incoming stereo and outgoing stereo [interleaved]) >>> * Extended softmix for stereo support (downmixing) >>> * Extended the default confbridge (basically added a convolution engine) > > > If Opus is a required part of the implementation - and from reading the > description of the work being done it appears to be - wouldn't that make > this ineligible for inclusion?
My hope is that there is a large amount of core Asterisk work which does not explicitly require Opus for it to be merged. I'm hoping that our current Opus legal impasses will not go on forever, but until things clear up with regards to it, this is the best response I can give. -- Matthew Fredrickson Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
