W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

WebRTC Web APIs for On-board Multimedia Devices Handling and Control

From: Venkateswar Reddy Melachervu <vmelachervu@gmail.com>
Date: Mon, 8 Jul 2013 07:56:02 +0530
Message-ID: <CAFbMEWVzWWOp-GtUF9-Z7SCtCF5cDFzkzpqigjjrZ7kf1rJ_=Q@mail.gmail.com>
To: public-webrtc@w3.org
Cc: Venkateswar Reddy Melachervu <vmelachervu@gmail.com>
Team WebRTC,
First of all let me congratulate you for the awesome work you have done and
are doing to liberate the multimedia control from the clutches of native
OS' walled garden while as you read this mail many civil societies wage war
against the walled freedom across the globe.

I am just beginning to get into the innards of the WebRTC and request your
patience for what may seem like novice queries.

The over-arching query I've is related the framework for web APIs for the
control/handling of multimedia devices for audio, video and screen share
sessions from within a browser-side web app (HTML, Javascript). More
specifically :
 - Getting list of available devices and selecting a device for audio,
video - mic, speaker, camera - session from the OS available devices
 - Getting and setting device properties like device name, device id,
sampling rate, echo cancellation etc for audio, video etc. - mic, speaker,
camera etc.
 - Getting and setting OS default device for speaker, mic, camera
 - Muting/un-muting a device/stream
 - Getting events for:
      - When a device - mic, speaker, camera becomes
disabled/unavailable/plugged out
      - When a device - mic, speaker, camera becomes
      - When a device property like sampling rate etc. change - mic,
speaker, camera
      - When a default device selection changes - mic, speaker, camera

My question is : are there web APIs (IETF) for WebRTC for the above
purposes in defined/available today for a web app developer like us who is
developing a web app (html, javascript only) that cuts across audio, video
and screen shares - in browsers (desktop and android)? My initial searching
and google searching did not yield the answer I was looking for either
across the IETF drafts or web.

These are non-negotiable controls a multimedia web app needs to have to
offer a seamless, acceptable, WORAB - write once, run on any browser,
multimedia experience to the end users and for the success of web - more so
for the success of WebRTC itself, in my view. If not-addressed by IETF,
browser makers will eventually be forced to introduce proprietary APIs -
nullifying the global goal of making the web work for all.

Let's liberate the multimedia control from the clutches of OS walled garden
for the success of web on this very month a great nation attained freedom
and set an example to the world of freedom and free and open markets.

Venkateswar Reddy Melachervu
"...dare to dream, care to win..."
Received on Monday, 8 July 2013 05:13:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:34 UTC