Re: Error handling if source does not support non-audible playback

Thanks Paul

Apparently, I've temporarily forgotten how to read ... I can't find the
specified behavior of a cross-origin conflict in the spec either. Could you
point me in the right direction?

--hans


On Wed, Jan 15, 2014 at 2:09 PM, Paul Adenot <padenot@mozilla.com> wrote:

> This has not been considered, I believe.
>
> I think it could work in the same way as a cross-origin resource that
> should not have its content inspected: output silence. A warning could then
> be written in the Javascript console.
>
> Paul.
>
> ----- Original Message -----
> > From: "Hans Schmucker" <hansschmucker@gmail.com>
> > To: public-audio@w3.org
> > Sent: Wednesday, January 15, 2014 2:03:07 PM
> > Subject: Error handling if source does not support non-audible playback
> >
> > This has come up on the EME List:
> >
> > What is the expected behavior of MediaElementAudioSourceNode and other
> > source nodes if the source does not support silent playback or
> redirection
> > to a buffer?
> > In the case of EME, a ContentDecryptionModule may refuse to output sound
> > any other way but directly to the audio hardware.
> >
> > I imagine it may throw an error or treat it like a silent source, but I
> > can't find anything definite in the Web Audio API spec about error
> handling
> > in this case.
> >
> > --hans
> >
>