W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: CodecNode

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 16 May 2012 11:11:16 +1200
Message-ID: <CAOp6jLacT9-0XwGoPiTL-u-0px6+bnvbR6er2aRrDVP6rOVCRA@mail.gmail.com>
To: "Young, Milan" <Milan.Young@nuance.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>
On Wed, May 16, 2012 at 10:45 AM, Young, Milan <Milan.Young@nuance.com>wrote:

>  The recording use case I had in mind was quasi-realtime.  Similar to
> WebRTC except that I’d like the application layer to have control over the
> transport.  In this model, the “recorder” portion of the
> MediaStreamRecorder is just a way to get at an encoded version of the audio
> data.  If the Audio API could provide an encoded version of the stream,
> recording would not be necessary.

Someone will pretty soon want to exactly what you're doing, except with
video and audio. So this needs to be a MediaStream API or we're going to
have major duplication.

“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]
Received on Tuesday, 15 May 2012 23:11:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:04 UTC