Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cele domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/hughmcguire/hughmcguire.net/wp-includes/functions.php on line 6121

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/hughmcguire/hughmcguire.net/wp-includes/functions.php:6121) in /home/hughmcguire/hughmcguire.net/wp-includes/rest-api/class-wp-rest-server.php on line 1896
{"id":976,"date":"2010-08-13T13:50:30","date_gmt":"2010-08-13T18:50:30","guid":{"rendered":"https:\/\/hughmcguire.net\/2010\/08\/13\/html5-audio-tag-mess\/"},"modified":"2010-08-13T16:04:02","modified_gmt":"2010-08-13T21:04:02","slug":"html5-audio-tag-mess","status":"publish","type":"post","link":"https:\/\/hughmcguire.net\/2010\/08\/13\/html5-audio-tag-mess\/","title":{"rendered":"HTML5 Audio Tag Mess"},"content":{"rendered":"

Good news: in the new HTML5 spec, you don’t need Flash or another plugin to play audio files from standards compliant browsers. Instead, you can put your audio link between <audio><\/code> tags, and all should be well.<\/p>\n

New releases of Safari, Chrome, Firefox, and Opera all support the audio tag.<\/p>\n

Bad news: Safari, Chrome, Firefox and Opera all support the tag, but they don’t all support the same codecs – or kinds of audio files. Here, from HTM5 Doctor<\/a>, is a list of current support:<\/p>\n

\"HTML5<\/p>\n

Man.<\/p>\n

You can solve the problem by offering all the codecs between the tags, so:<\/p>\n


\n<audio>
\n<source src=\"librivox.ogg\" \/>
\n<source src=\"librivox.mp3\" \/>
\n<source src=\"librivox.wav\" \/>
\n<\/audio><\/code><\/p>\n

Anyone have a better explanation for such a jumble?<\/p>\n","protected":false},"excerpt":{"rendered":"

Good news: in the new HTML5 spec, you don’t need Flash or another plugin to play audio files from standards compliant browsers. Instead, you can…<\/p>\n