HTML5 Audio is a subject of the HTML5 specification, investigating audio input, playback, synthesis, as well as speech to text in the browser - wikipedia ![]()
http://cdn.media.ccc.de/congress/2013/mp3/30c3-5437-en-Plants_Machines_mp3.mp3
This is an example of using the audio plugin to display an mp3 file from cdn.media.ccc.de ![]()
YOUTUBE 1GfmSp6HrYc Rhode Lavelier mic
# HTML5 audio tag
There are a number of interesting options that can be used with the audio tag - developer.mozilla.org ![]()
<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>
# Buffering
You can't control the buffering of an audio tag. The buffering and delay is dependent on implementation, and is more complicated than a single setting as there are buffers along every step of the chain - stackoverflow ![]()
If latency matters for your application, I suggest implementing a WebRTC client which is built for low-latency.
If you need even more control, you can receive audio data over web sockets and playback with the Web Audio API, but this requires you to manage the buffering yourself and makes codecs tricky, for likely no improvement over WebRTC.
# Adoption
The adoption of HTML5 audio, as with HTML5 video, has become polarized between proponents of free and patented 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.
http://cdn.media.ccc.de/congress/2013/webm/30c3-5437-en-Plants_Machines_webm.webm Plants_Machines_webm.webm
But it looks like the HTML plugin does not support the HTML5 audio tag:
Your user agent does not support the HTML5 Audio element.