Re: getUserMedia use cases

I'd like to one up what Tom just said, but also share a bit of thoughts on
the matter... As useful as it is to enumerate the MIDI devices, and get I/O
access to them, another really useful aspect of MIDI are virtual devices.
For example, if I make a virtual keyboard or a sequencer for the browser,
to stream to most of the DAWs, I need a virtual device that will act as an
output for my app, and an input for the DAW. In the same way, if I have
native sequencer application, and I would like to stream it's output to my
in-browser-DAW, I need a virtual device that will act as the input for my
DAW and output for the sequencer.

I'm not sure how this would be achieved, but I think it applies to concepts
such as webcams as well, would be pretty cool to create a virtual webcam,
that streams the contents of a canvas for example, then use existing
applications such as Skype to harness it. This would allow great
interaction with existing applications out there. Of course, you must not
forget the security aspects that come along with this, as such proxy
devices would also allow some malicious transfer.

Jussi Kalliokoski
Official.fm labs

On Wed, Feb 1, 2012 at 2:25 AM, Tom White (MMA) <lists@midi.org> wrote:

> **
> Chris Rogers said
>
>  it would be good to have an introspection API to enumerate the available
> audio devices for both audio input and output.  A built-in microphone would
> be one such device.  Also commonly available is the line-in analog audio
> input on a laptop or desktop computer.  And, of course, any externally
> connected multi-channel USB or Firewire audio devices.  Some of these can
> present eight (or more) simultaneous audio input and output channels
> simultaneously.
>  It's important to not consider audio input in isolation, but also audio
> output capabilities when enumerating the devices.
>
> I can't help but point out that MItDI devices (software and hardware
> ports) are commonly used for audible* input/output and thus would also be a
> candidate for enumeration...
>
> Tom White
> www.midi.org
>
> *I say "audible" instead of "audio" so there is no confusion between MIDI
> and audio <g>
>