Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability

Randell Jesup <randell-ietf@jesup.org> Mon, 06 August 2012 21:23 UTC

Message-ID: <50203564.8070509@jesup.org>
Date: Mon, 06 Aug 2012 17:21:40 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <53223349-A31F-4381-899F-82E29B0A0B6C@cisco.com> <CACHLvecT1AgJRo=xM5AH-fGZn+iYrtHqWk7Eym8QJn9U7YGcsg@mail.gmail.com> <CAPk5xQv_ZNqo66LfApshWtRrvXuBMscnp3+kY_GMiibgD1BCqw@mail.gmail.com> <AEF5DA45-0307-4170-A8B4-BAE6B25248C8@cisco.com> <CAOJ7v-093zyfumK_z5dGhr8msNatfBABk6wD=g80GH2LG4055Q@mail.gmail.com> <CAPk5xQsxfNQhdVQUnhfXY2US-tsixsv0h+A6y-26UK7px4PpKw@mail.gmail.com>
In-Reply-To: <CAPk5xQsxfNQhdVQUnhfXY2US-tsixsv0h+A6y-26UK7px4PpKw@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] Microsoft tells W3C and IETF what we are doing no signs of offering real world interoperability
Precedence: list

On 8/6/2012 4:49 PM, Rohit Puri wrote:
> If from the media pipeline perspective, it were possible to have an
> architecture like for example, gstreamer, wherein there is a concept of
> a processing chain for media and it is possible for the client developer
> to provide proprietary processing blocks that suit the use case for
> their application better than the default implementation, that would be
> great.

See the MediaStream Processing API proposal:
https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing.html

Note that this was partly an alternative to the Web Audio API, which has 
been adopted, and they plan to integrate some aspects of MediaStream 
Processing into Web Audio, but MediaStream Processing is still relevant, 
especially for video (and will be more so once JS workers can access WebGL).

-- 
Randell Jesup
randell-ietf@jesup.org

[rtcweb] Microsoft tells W3C and IETF what we are… Cullen Jennings (fluffy)
Re: [rtcweb] Microsoft tells W3C and IETF what we… Luca De Cicco
Re: [rtcweb] Microsoft tells W3C and IETF what we… Rohit Puri
Re: [rtcweb] Microsoft tells W3C and IETF what we… Harald Alvestrand
Re: [rtcweb] Microsoft tells W3C and IETF what we… Cullen Jennings (fluffy)
Re: [rtcweb] Microsoft tells W3C and IETF what we… Justin Uberti
Re: [rtcweb] Microsoft tells W3C and IETF what we… Rohit Puri
Re: [rtcweb] Microsoft tells W3C and IETF what we… Kevin P. Fleming
Re: [rtcweb] Microsoft tells W3C and IETF what we… Jim Barnett
Re: [rtcweb] Microsoft tells W3C and IETF what we… Kevin P. Fleming
Re: [rtcweb] Microsoft tells W3C and IETF what we… Randell Jesup
Re: [rtcweb] Microsoft tells W3C and IETF what we… Randell Jesup
Re: [rtcweb] Microsoft tells W3C and IETF what we… Matthew Kaufman
Re: [rtcweb] Microsoft tells W3C and IETF what we… Justin Uberti
Re: [rtcweb] Microsoft tells W3C and IETF what we… Martin J. Dürst
Re: [rtcweb] Microsoft tells W3C and IETF what we… Randell Jesup
Re: [rtcweb] Microsoft tells W3C and IETF what we… Alexey Aylarov
Re: [rtcweb] Microsoft tells W3C and IETF what we… Tim Panton
Re: [rtcweb] Microsoft tells W3C and IETF what we… Lorenzo Miniero
Re: [rtcweb] Microsoft tells W3C and IETF what we… Jim Barnett
Re: [rtcweb] Microsoft tells W3C and IETF what we… Anant Narayanan
Re: [rtcweb] Microsoft tells W3C and IETF what we… Harald Alvestrand
Re: [rtcweb] Microsoft tells W3C and IETF what we… Tim Panton
Re: [rtcweb] Microsoft tells W3C and IETF what we… Tim Panton