Hi again,
On 28 October 2015 at 23:08, Arun Raghavan wrote:
> Hi folks,
> I'm looking at updating the webrtc-audio-processing code, and will
> probably look at doing a new release that breaks API. I've written a
> little bit about the rationale here:
>
> http://arunraghavan.net/2015/10/psa-breaki
On Wed, 2015-10-28 at 18:52 +0100, Peter Meerwald wrote:
> Hello,
>
> > I'm looking at updating the webrtc-audio-processing code, and will
> > probably look at doing a new release that breaks API. I've written
> > a
> > little bit about the rationale here:
>
> I've built a somewhat recent webrtc-
On 28-Oct-2015 11:43 pm, "Felipe Sateler" wrote:
>
> On 28 October 2015 at 14:38, Arun Raghavan wrote:
> > Hi folks,
> > I'm looking at updating the webrtc-audio-processing code, and will
> > probably look at doing a new release that breaks API.
>
> Would it be possible to write code that compile
On 28 October 2015 at 14:38, Arun Raghavan wrote:
> Hi folks,
> I'm looking at updating the webrtc-audio-processing code, and will
> probably look at doing a new release that breaks API.
Would it be possible to write code that compiles (not run, ABI would
be incompatible) against both versions of
Hello,
> I'm looking at updating the webrtc-audio-processing code, and will
> probably look at doing a new release that breaks API. I've written a
> little bit about the rationale here:
I've built a somewhat recent webrtc-audio-processing library a few month
ago in a hackish way
I had to redo t
