HTML5 Audio

"Audio tag" redirects here. For metadata describing digital audio, see Metadata § Digital music.

HTML5 Audio is a subject of the HTML5 specification, investigating audio input, playback, synthesis, as well as speech to text in the browser.

<audio> element

The <audio> element represents a sound, or an audio stream.[1] It is commonly used to play back a single audio file within a web page, showing a GUI widget with play/pause/volume controls.

The <audio> element has these attributes:

Example:[2]

<audio controls>
  <source src="http://media.w3.org/2010/07/bunny/04-Death_Becomes_Fur.mp4" type='audio/mp4' />
  <source src="http://media.w3.org/2010/07/bunny/04-Death_Becomes_Fur.oga" type='audio/ogg; codecs=vorbis' />
  <p>Your user agent does not support the HTML5 Audio element.</p>
</audio>

Supported browsers

Supported audio coding formats

The adoption of HTML5 audio, as with HTML5 video, has become polarized between proponents of free and patent-encumbered formats. In 2007, the recommendation to use Vorbis was retracted from the specification by the W3C together with that to use Ogg Theora, citing the lack of a format accepted by all the major browser vendors.

Apple and Microsoft support the ISO/IEC-defined formats AAC and the older MP3. Mozilla and Opera support the free and open, royalty-free Vorbis format in Ogg and WebM containers, and criticize the patent-encumbered nature of MP3 and AAC, which are guaranteed to be “non-free”. Google has so far provided support for all common formats.

Most AAC files (finite-length media) are wrapped in an MP4 container, which is supported natively in Internet Explorer, Safari, and Chrome, and supported by the OS in Firefox and Opera.[4] Most AAC live streams (infinite-length media) are wrapped in an ADTS container, which is currently only supported by Chrome and Safari.[5]

Many browsers also support uncompressed PCM audio in a WAVE container.[6]

In 2012, the free and open royalty-free Opus format was released and standardized by IETF. It is supported by Mozilla, Google, and Opera.[7][8][9]

Supported browsers

This table documents the current support for audio coding formats by the <audio> element.

Browser Operating system Formats supported by different web browsers
WAV PCM MP3 MP4 AAC ADTS AAC Ogg Vorbis WebM Vorbis Ogg Opus WebM Opus
Google Chrome All supported Yes Yes Yes Yes 9 Yes 25
(since v31 in Windows)
Yes
Internet Explorer Windows No 9 9 No No No No No
Microsoft Edge Windows Yes Yes Yes No No No[10] No No[11]
Mozilla Firefox All supported 3.5 OS-dependent[lower-alpha 1] OS-dependent[lower-alpha 1] No 3.5 4.0 15.0 28.0[13]
Opera All supported 11.00 OS-dependent[lower-alpha 2] OS-dependent[lower-alpha 2] No 10.50 10.60 14 Yes
Safari OS X 3.1 3.1 Yes Yes Manual install No No No

Web Audio API and MediaStream Processing API

The Web Audio API specification developed by W3C describes a high-level JavaScript API for processing and synthesizing audio in web applications. The primary paradigm is of an audio routing graph, where a number of AudioNode objects are connected together to define the overall audio rendering. The actual processing will primarily take place in the underlying implementation (typically optimized Assembly / C / C++ code), but direct JavaScript processing and synthesis is also supported.[15]

Mozilla's Firefox browser implements a similar Audio Data API extension since version 4, implemented in 2010 [16] and released in 2011, but Mozilla warns it is non-standard and deprecated, and recommends the Web Audio API instead.[17] Some JavaScript audio processing and synthesis libraries such as Audiolet support both APIs.

The W3C Audio Working Group is also considering the MediaStream Processing API specification developed by Mozilla.[18] In addition to audio mixing and processing, it covers more general media streaming, including synchronization with HTML elements, capture of audio and video streams, and peer-to-peer routing of such media streams.[19]

Supported browsers

Web Speech API

The Web Speech API aims to provide an alternative input method for web applications (without using a keyboard). With this API, developers can give web apps the ability to transcribe voice to text, from the computer's microphone. The recorded audio is sent to speech servers for transcription, after which the text is typed out for the user. The API itself is agnostic of the underlying speech recognition implementation and can support both server based as well as embedded recognizers.[22] The HTML Speech Incubator group has proposed the implementation of audio-speech technology in browsers in the form of uniform, cross-platform APIs. The API contains both:[23]

Google integrated this feature into Google Chrome on March 2011.[24] Letting its users search the web with their voice with code like:

<script type="application/javascript">
    function startSearch(event) {
        event.target.form.submit();
    }
</script>
<form action="http://www.google.com/search">
  <input type="search" name="q" speech required onspeechchange="startSearch">
</form>

Supported Browsers

See also

Notes

  1. 1 2 Firefox does not have native support for MPEG codecs due to licensing reasons. MP3/AAC support for Firefox is present in the following operating systems: Windows Vista (v21.0), OS X (v26.0), Linux (v24.0, needs a gstreamer codec)[12]
  2. 1 2 Opera does not have native support for MPEG codecs due to licensing reasons. Decoding of audio files requires the host OS to provide a compatible library. MP3/AAC support is present in Windows 8 (v25) and OS X 10.9 (v26)[14]

References

  1. HTML5 audio element - W3C
  2. https://www.w3.org/wiki/HTML/Elements/audio
  3. 1 2 About HTML5 Audio and Video - Safari HTML5 Audio and Video Guide
  4. Is it possible to play this stream using HTML5/javascript?
  5. MP4 container · Issue #95 · karlheyes/icecast-kh · GitHub
  6. https://developer.mozilla.org/en-US/docs/Media_formats_supported_by_the_audio_and_video_elements
  7. https://developer.mozilla.org/en-US/docs/Media_formats_supported_by_the_audio_and_video_elements#Ogg_Opus
  8. https://www.xiph.org/press/2012/rfc-6716/
  9. https://hacks.mozilla.org/2012/09/its-opus-it-rocks-and-now-its-an-audio-codec-standard/
  10. https://dev.modern.ie/platform/status/vorbisaudiocodec/
  11. https://dev.modern.ie/platform/status/opusaudiocodec/
  12. http://html5hub.com/so-do-we-have-a-cross-browser-audio-format-yet/
  13. http://www.mozilla.org/en-US/firefox/28.0/releasenotes/
  14. http://stackoverflow.com/questions/28237510/does-opera-support-audio-mp3-files
  15. Chris Rogers (2012-03-15). "Web Audio API". W3C. Archived from the original on 2012-03-15. Retrieved 2012-07-04.
  16. "Audio Data API".
  17. "Introducing the Audio API extension". Mozilla Developer Network. Mozilla. 2012-03-05. Archived from the original on 2014-01-16. Retrieved 2012-07-04.
  18. "Audio Processing API". W3C. 2011-12-15. Archived from the original on 2011-12-15. Retrieved 2012-07-04.
  19. Robert O'Callahan (2012-05-31). "MediaStream Processing API". W3C. Retrieved 2012-07-04.
  20. Web Audio API is now available in Chrome
  21. Scott Gilbertson (2011-09-19). "Chrome 14 Adds Better Audio, ‘Native Client’ Support". Webmonkey. Wired. Retrieved 2012-07-04.
  22. "API draft". Retrieved January 28, 2012.
  23. "HTML5 Speech API". Retrieved January 28, 2012.
  24. "Talking to your computer". Retrieved January 28, 2012.

External links

This article is issued from Wikipedia - version of the Monday, December 14, 2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.