Category Archives: HTML 5 Audio Video

WebGL 3D Asteroid Game with HTML 5 audio

WebGL 3D Asteroid Game with HTML 5 audio

a small webgl 3d asteroid game with HTML 5 audio, done with CopperLicht, CopperCube and WebsitePainter. Demo here: (run only if you have a webgl enabled browser) More about CopperLicht:


Cursos De WordPress: Creando Mi Web Y Woptimizar – Carolina Renteria

Cursos De WordPress: Creando Mi Web Y Woptimizar – Carolina Renteria
Gana El 50% Por Cada Venta – WordPress Es Un Sistema Gestor De Contenidos Mundialmente Conocido, Este Curso Muestra Como Usar WordPress Para Hacer Negocios En Internet O Simplemente Para Crear Un Sitio Web Propio.
Cursos De WordPress: Creando Mi Web Y Woptimizar – Carolina Renteria

Flash Audio Wizard (v4) – Web Audio Software.
Top Selling Streaming Audio Button Creator With Built-in Background Music. Audio Editor Software And Video Training Bonuses. Full Affiliate Tool Kit With Links, Banners, Ezine Ads And More. Affiliates Earn .58 Per Sale.
Flash Audio Wizard (v4) – Web Audio Software.


Native Audio with HTML5

Emily P. Lewis | October 12, 2011

Once upon a time, audio on the web lived primarily in the world of third-party browser plug-ins like Flash, QuickTime and Silverlight. This was not a bad world, but it had its issues.

For one, most plug-ins require the user to install them, but not all users are willing (or able) to install them. Also, many players built with these plug-ins are inaccessible, making it difficult for folks who use assistive technologies to access the audio or alternative content.

Then there are the front-end design hassles like trying to get a dropdown menu to display on top of a plug-in-based player. And let’s not forget that to build a custom player with these plug-ins requires knowledge and expertise in that SDK.

Enter HTML5

Today, we have another option: HTML5 <audio>. This new element allows you to deliver audio files directly through the browser, without the need for any plug-ins. It works much like the tried-and-true <img> element, embedding the audio file into a web page via the src attribute:

  1. <audio src=”audio.mp3″></audio>

Not only does native audio deliver independence from plug-ins, it can be targeted with CSS and JavaScript. This means that creating a custom player is simply a matter of writing HTML, CSS and JS. It also means more front-end control for responsive, dynamic designs and potentially better accessibility.

As far as browser support goes, <audio> enjoys support by all of today’s latest browsers, including mobile browsers for iOS 4+, Android 2.3+ and Opera Mobile 11+.

Sound good? Then let’s get started adding embedded audio in our web pages!

A Basic Audio Player

To add a simple audio player to your web page, all you need is a single line of markup:

  1. <audio src=”audio.mp3″ controls></audio>

This includes the src attribute I already discussed, which embeds the specified audio file into the page. It also includes the controls attribute, which tells the browser to use its default control interface for audio.

As you can see in Figure 2, each browser has a different default for player controls but all include the basics: play/pause toggle, timeline progress bar and volume control.

More Attributes

Beyond src and controls, <audio> has several other attributes you can utilize to further modify how your audio file will load and play.


  1. <audio src=”audio.mp3″ controls autoplay></audio>

The Boolean autoplay attribute is one that I don’t recommend using because it specifies that the audio begin playing as soon as the page loads. This is a usability no-no for most scenarios, so exercise restraint in using this attribute.

If you do decide to utilize autoplay, please be sure to include the controls attribute (or roll your own custom controls) so that your users can stop the audio or reduce volume.


  1. <audio src=”audio.mp3″ controls crossorigin=”anonymous”></audio>

crossorigin is used to indicate if an audio file is being served from a different domain. This is a very new attribute introduced for all media elements (<video> and <img> too) to address playback issues with Cross-Origin Resource Sharing (CORS).

Depending on the scenario, crossorigin can be declared with an empty string or with CORS settings attribute keywords: user-credentials or anonymous.


  1. <audio src=”audio.mp3″ controls loop></audio>

Another Boolean attribute, loop, tells the browser to loop the audio when playing. Like autoplay, I’m not a particular fan of this attribute because it takes control away from the user. But if you must use it, I recommend including the controls attribute alongside loop.


  1. <audio src=”audio.mp3″ controls mediagroup=”AnyName”></audio>

mediagroup is another relatively new attribute that is used to tie together multiple media files for synchronized playback. Each media element with the same keyword value for mediagroup is, essentially, linked and can be manipulated for playback via the DOM.

This attribute is valid for all media elements, so it is possible to link audio to audio, as well as audio to video and video to video.


  1. <audio src=”audio.mp3″ controls muted></audio>

The Boolean attribute muted does just what it says: mutes the audio file upon initial play. The user can then override this if volume controls are provided.


  1. <audio src=”audio.mp3″ controls preload></audio>

The preload attribute suggests how the browser should buffer the audio, according to the specified value:

  • preload="auto" (same as the Boolean preload in the example) leaves it up to the browser to decide whether to begin downloading.
  • preload="metadata" tells the browser to download information like tracks and duration, but to wait to buffer the audio until the user selects play.
  • preload="none" tells the browser that no audio information should be downloaded until the user activates the controls.

Make note that not all browsers support all of these attributes and that the specification itself is still changing. That means you have to experiment, test and stay up-to-date on the spec.

Fallback Content

As I already mentioned, <audio> is well supported by modern browsers. But what about users who aren’t on modern browsers? Depending on your audience, there could be a fair percentage of your users who can’t access your audio content. For those users, <audio> offers fallback content, which is contained within the opening and closing <audio> tags:

  1. <audio src=”audio.mp3″ controls>
  2. <p>Your browser does not support native audio, but you can <a href=”audio.mp3″>download this MP3</a> to listen on your device.</p>
  3. </audio>

For browsers that don’t support <audio>, this fallback content is what displays to the user, while browsers that do support native audio ignore the fallback and display the player.

In this example, I chose to include some explanatory text and a link to download the audio file for my fallback content. But you can pretty much include any content you want to serve to those users, including HTML.

Not a Perfect World

HTML5 <audio> makes it (arguably) easier for an average front-end developer like me to add audio to web pages. And it opens up a world of possibilities for better media accessibility as the specification evolves.

Unfortunately, like the world of plug-ins, native audio has its issues too.

No Single Codec

To keep audio content for the web at reasonable sizes for streaming and download, audio data is compressed/decompressed using codecs. Different codecs transform the audio into different formats that offer good quality with minimum bitrates.

So far, there is no single standard for audio codecs in the HTML5 specification. This means that some browsers support some formats, while other browsers support others:

Multiple Audio Files

Fortunately, <audio> is set up to handle multiple file formats:

  1. <audio controls>
  2. <source src=”audio.ogg”>
  3. <source src=”audio.mp3″>
  4. </audio>

As you can see in this example, to declare multiple audio files, you first drop the src attribute from <audio>. Next, you nest child <source> elements inside <audio>, each of which specifies a different file format via the src attribute.

A browser will read the first-listed <source> and, if it supports the specified file format, the audio player will render on the page. If the browser doesn’t, it moves on to the next <source> element.

In the event the browser doesn’t find a <source> file format it can support, it will fail and playback won’t be possible:

But this is where you can take advantage of fallback content, which must be nested within <audio> and after all <source> elements:

  1. <audio controls>
  2. <source src=”audio.ogg”>
  3. <source src=”audio.mp3″>
  4. <p>Your browser does not support native audio, but you can <a href=”audio.mp3″>download this MP3</a> to listen on your device.</p>
  5. </audio>

In this example, a browser will first check if it supports <audio>. If it doesn’t, it goes straight to the fallback content.

If it does support <audio>, it next checks for support of file formats, starting with the first <source> and proceeding until it reaches a supported format. In the event no listed formats are supported, the fallback content displays.

Files & Order

In terms of which file formats to include, it isn’t necessary to have all formats listed in Figure 3. Including just MP3 and OGG will cover all your bases for modern browsers supporting HTML5 <audio>.

Regarding source order, it technically doesn’t matter which audio file format is listed first. That said, I usually include my OGG <source> first. It is the higher-quality file, compared to MP3, and I want browsers that support both to get the OGG first. Also, there was a bug in older versions of Firefox where if the first <source> format was MP3 it failed, so listing OGG first can avoid triggering this bug.

MIME Types

In addition to specifying multiple audio formats, it is also good practice to specify MIME types for each audio file:

  1. <audio controls>
  2. <source src=”audio.ogg” type=”audio/ogg”>
  3. <source src=”audio.mp3″ type=”audio/mp3″>
  4. <p>Your browser does not support native audio, but you can <a href=”audio.mp3″>download this MP3</a> to listen on your device.</p>
  5. </audio>

By specifying a MIME type for each audio format, it helps the browser know what type of content it will be dealing with. This can speed up <audio> rendering because the browser won’t have to download the files to determine content type.

Also, some browsers won’t play audio without the correct MIME type. For example, Safari 5.1 (at least as of this writing) will fail to play any audio if the first-listed <source> is an unsupported format like OGG without a specified MIME type.

Server Support

During my experiments with <audio> I encountered one of the more frustrating aspects of delivering native media: server support for MIME types. Though you can specify the MIME type for each audio format directly in your markup as seen in the example above, this doesn’t guarantee that your web server supports those MIME types.

And if your server doesn’t support a given format, you won’t have playback … something I discovered (not quickly enough) when an <audio> implementation that worked on my local system failed on the live web server.

I’m am the furthest thing from a expert on server configurations, but I have found success circumventing these MIME type issues by updating my sites’ .htaccess files to reference the correct file types. And the HTML5 Boilerplate.htaccess file is a fantastic template to start with.

Making the Transition

HTML5 is still new to so many developers. So maybe you aren’t quite ready to take the leap headfirst into <audio>? Or perhaps you have concerns about your users on browsers without <audio> support?

I completely understand wanting the best possible experience for all your users, regardless of their browsers. Fortunately, you can ease into HTML5 <audio> and gracefully degrade the experience for users on older browsers.

Flash Fallback

As I mentioned, <audio> fallback content can include HTML. And that means it can include a Flash <object> for browsers that don’t support <audio>:

  1. <audio controls>
  2. <source src=”audio.ogg” type=”audio/ogg”>
  3. <source src=”audio.mp3″ type=”audio/mp3″>
  4. <object data=”mediaplayer.swf?audio=audio.mp3″>
  5. <param name=”movie” value=”mediaplayer.swf?audio=audio.mp3″>
  6. </object>
  7. </audio>

In this example, the browser will first check if it supports <audio>. If it doesn’t, it will fallback to the Flash audio player (provided the plug-in is installed).

If the browser does support <audio>, it will proceed through the <source> elements until it finds a supported format. In the event no supported format is listed, the browser will fallback to the Flash player (again, if the plug-in is installed).

Fallback for the Fallback

Now, what if Flash isn’t supported? That’s when you use the fallback’s fallback:

  1. <audio controls>
  2. <source src=”audio.ogg” type=”audio/ogg”>
  3. <source src=”audio.mp3″ type=”audio/mp3″>
  4. <object data=”mediaplayer.swf?audio=audio.mp3″>
  5. <param name=”movie” value=”mediaplayer.swf?audio=audio.mp3″>
  6. <p>Your browser does not support native audio or Flash, but you can <a href=”audio.mp3″>download this MP3</a> to listen on your device.</p>
  7. </object>
  8. </audio>

Simply nest your Flash fallback content within the <object> and after all <param>s. Browsers that don’t support HTML5 audio or Flash will fallback to this content, in this case some explanatory text and a link to download the audio.

Pre-Built Players

Another way you can transition to HTML5 audio is to use a pre-built player. Many players today give you options to choose different skins for the player and even skin on your own via CSS. Additionally, several HTML5 media players are already built with Flash fallback content. Here are a few to check out:

Further Reading

To say this is the tip of the iceberg when it comes to native audio is an understatement. This article focuses on the core markup and syntax for embedding audio into your web pages. But the true power of native audio is the ability to target it using JS and CSS.

You can make your own custom player. You can visualize audio. You can generate audio on the fly. And these are just some of the early experiments.

As you experiment further with <audio>, please check out these resources:

P.S. You’ve got the foundation for <video> now!

Much of what this article discusses for HTML5 <audio> applies equally to <video>. As media elements, they share many of the same attributes and follow a similar syntax. <video> is also subject to many of the same issues as <audio> — specifically multiple file formats and MIME types — and benefits from the same solutions.


HTML Video Tutorial For Beginners

HTML Video Tutorial For Beginners
Keep 50% of sales on this high selling, high conversion rate product. It has an excellent sales page and it is an excellent product for beginners that want to learn Html.
HTML Video Tutorial For Beginners


SEO, Information Architecture and Interface Design

SEO, Information Architecture and Interface Design

Keywords, I swear, that’s all I hear from my colleagues, that and the assumption that keywords are the most important part of SEO. Well, I disagree. I don’t believe keywords are the most important building block of SEO. Keyword phrases mean nothing unless they’re used in a specific, contextual environment.

Think about it. Many search engine spammers use software spiders to “borrow” content from competitor sites to generate doorway-page content. Do spam doorway pages generate high-quality search engine traffic and conversions? Not likely, especially if you’ve ever viewed some of these poorly designed and unusable pages. The contextual environment is substandard; therefore, the keyword phrases have little meaning.

The most important building block of SEO is the information architecture. If you want your HTML/XHTML, audio, video, and image files to generate qualified search engine traffic, the key ingredient to making these files appear relevant are the information architecture and the interface that communicates this architecture.

Information Architecture versus Interface

Many SEOs utilize the terms “information architecture” and “site architecture” without truly understanding their meaning. Information architecture refers to the organization of site content into groups. Navigation is part of the user interface. Unfortunately, too many SEOs confuse a site’s actual information architecture with the interface.

How is your site’s information grouped? Are all video files (if used) placed in a directory labeled “videos” (or some other relevant label), and do you give search engines easy access to those files? When you use videos on Web pages, are they used as eye candy or to highlight relevant concepts on key pages?

The Meaning of Search

Interestingly, as the search industry has evolved, it seems the word “search” has come to mean only the querying process. In other words, type in two to three keywords into Google and get results — that’s search.

Search behavior doesn’t only encompass the querying process. Scanning is also a search process. When people view search results, they scan the page for information. When people click a search result to get to a Web page, they scan the Web page to determine whether or not the page’s content matches their search query.

Many SEOs and their clients need to take their blinders off. There’s a plethora of search behavior outside of rankings. I find the obsession with ranking to be rather narrow-minded and annoying, especially from people who should know better.


We are a SEO Services and Internet Marketing provider SEO India Company .for any query regard SEO you may content us.

More HTML 5 Audio Video Articles

Which spy pen is the best choice to buy?

Which spy pen is the best choice to buy?

Question by mark.deguia: Which spy pen is the best choice to buy?

Can someone please give me a good opinion on which is best because I’m very ignorant on technical stuff like this. I dont really know much about this. I want to be able to take good quality video in secret.

They all have the same format whih is AVI so i dont need to worry about that.

They all use the same video encoding so I dont need to worry about that.

The 2nd & 3rd seem to have a higher video resolution and FPS so I’m assuming that the video quality on them is better than the first one.

Someone needs to tell me which is better for image ratio. I want to be able to watch this on my computer or LED HD TV. Mostly the computer but thats good if its also great on a widescreen tv. The first one is 16:9 and the 2nd & 3rd ones are 4:3. I think 4:3 is letter box so it has those black lines at the sides. And 16:9 doesnt which is better. I think the 1st one is better for image ratio. But i’m just making an educated guess on what I know which isnt a lot.

The audio format I have little interest in because I am only focused on video quality.

What the heck is interface supposed to mean? It says that they are all USB. But the 2nd one is Mini 5 pin USB.

So storage is how much video it can hold. I think the 2nd one is best for storage. The 2nd one uses a micro SD card and it can hold up to 16 gb which sounds good. The 1st and 3rd both use 4gb Nand Flash which to me translates to “it can hold 4gb worth of video”. I dont really think thats really important because I can save video from the pen into the computer cant I?

They all use the same battery type.

I’m guessing that they all have the same working time which is about 90 min. I dont know what working time is. Does that mean how long it will stay on before running out of power?

Time/date stamp sounds like it can record the time and date when it is recording video. I think only the 1st one can do that.

I use a PC and they all support it.

So um after I record my video with any of these pens how would I view it on my computer? Would it have a USB connector or something that I use to connect the pen to the computer then watch the video?

After reviewing the technical info my 1st choice would be the 1st pen because even though its video resolution is lower than the other 2 its not by that much and its still HD quality. And after looking at 2 youtube videos comparing the 2 spy pens I couldnt really tell a difference between the quality of the videos from the 2 different pens. It has I think a better Image ratio then the other 2. I want to be able to watch it on TV but mostly on my computer and be ahppy with what I’m seeing( I dont want black lines). Again the video resolution between the cameras is 1280 by 720 and the others 1280 by 960. So only a difference of 240 um…. pixels. They are called pixels right?

So anyway thats my question my comparison and my initial first choice of the 3 pens. My 1st choice is the 1st pen. 2nd choice is the 2nd pen. and 3rd choice is the 3rd pen. I’m open to people’s ideas though on which I should get because I’m no technology expert. Please tell me which you would recommend and why. I will be interested in reading all of your answers comments and ideas. the person with the best answer will get 10 points.

Oh and the 2 youtube videos I watched were here
this one is the first pen.

this one is the 2nd pen

Best answer:

Answer by remo r
I think you should go with 8GB USB video camera spy pen

8GB Memory
Video and Camera Mode
One of the smallest digital Video Recorders built into a fully functional ball point pen
Records in Avi format High Res 640×480 avi Video Format
Ideal for secret recordings, Monitoring, emergency video recordings, accidents, etc.

Add your own answer in the comments!


HTML 5 Features and Uses

HTML 5 Features and Uses

HTML5 is a next version of HTML.There is lot of new features not yet implemented in this HTML 5.There is bunch of new features that will make it easier for developers to provide accessible and inaccessible content.

It is huge concept. HTML 5 has Semantic elements like etc

It is already implemented in Opera 9.5+

HTML 5 has New Structure and Semantics. New multimedia options like Native video support in browsers.

It will reduce dependence upon Flash completely.

HTML5 is best suitable for search engines, screen readers, information architects.

By using the advanced features of HTML5 user can expect fast, full-featured advanced web applications.

HTML5 API also includes

• Offline storage

• Geo-Location

• Drag & Drop

• Canvas

HTML 5 has Web Forms 2.0:

• Form Controls

• Repetition Model

• Client Side Validation

• DOM APIs for Forms

HTML 5 has the following

• New Structures

• New Semantics

• New Controls

• Client-Side Form Validation



Video Implementations is already done by some of the top sites like

• Opera (Experimental, Ogg Theora)

• Safari 3.1 (All QuickTime formats)

• Firefox 3.1 alpha 2 (Ogg Theora)

Canvas: There is special tag called Canvas in HTML 5 which can dynamically draw graphics and text around the browser and it has Graphics-oriented DOM APIs.

Canvas Implementations is already done in Opera, Firefox, and Safari.

HTML 5 Futures:

• It can assemble pages into large perceivable regions

• User can navigate of pages in a few keystrokes

• Supported by AT (JAWS, NVDA, ORCA)

• Compatible with HTML 4, 5 & XHTML

Some of the Special HTML5 Form controls

• Slider

• Combobox

• Date picker

• Spin box HTML 5 Audio & Video

• It has tags like

• Native accessible controls

• Captioning and annotations

• It has special tag called HTML5 Canvas element

Written by

Internet Marketing Company | Internet Marketing :

Marketing Agency :

Find More HTML 5 Audio Video Articles

12 visitors online now
4 guests, 8 bots, 0 members
Max visitors today: 16 at 01:56 am UTC
This month: 74 at 04-21-2017 07:18 pm UTC
This year: 74 at 04-21-2017 07:18 pm UTC
All time: 513 at 06-01-2016 02:24 pm UTC
Get Adobe Flash player